Hello. Steven Wittens:
Actually you will run into some more problems. Drupal is designed to not use mbstring, because it is not available everywhere. We have our own functions for handling basic UTF-8 stuff (string truncation, mime header encode, etc). These functions assume they get direct access to the string's bytes.
Ok, I think I get it. The Drupal's *_utf8 functions use the "classic" (non-multibyte) string manipulation functions as something that manipulates on bytes, not characters, and *depend* on such behaviour, right?
I have no idea how thorough mbstring override is, but you will certainly run into problems. Perhaps the best solution is to make Drupal explicitly check for mbstring and use it if present, otherwise use its own routines.
That seems to make sense. Do all of such Drupal wrapper functions contain utf8 in their names? If not, is there some place that lists all these functions, so I won't miss any? If I come with a patch for this, should I send it here or someplace else? Cheers, -- Shot -- It is a book about a Spanish guy called Manual. You should read it. -- Dilbert ====================== http://shot.pl/hovercraft/ === http://shot.pl/1/125/ ===