Hi,
On Sat, 25 Feb 2006 11:33:08 +0100, Dominic Mitchell wrote:
...
> It is a hack, but it's a useful one.
...
> You could get into long details about the correct API for transcoding
> automatically into the desired charset from whatever charset the database
> has stored your data in. But it smacks of overengineering, and not making
> the common case simple.
I was checking now that utf-8 looks really complicated enough to not to be
fooled by random data as "false positive". I can report that my engine was
getting MMSE (MMS Encapsulation - mobile phones binary format) data marked
as utf-8 (and therefore failing binary decoding of bytes-oriented MMSE).
Maybe I did there some other mistake or that previously attached patch of mine
is broken (still does not look so to me). Still the hassle around and
unpredictable behavior on possibly random failing service for the clients
prevented me from using it for real.
...
> > In fact I gave up and rather mark it utf-8 by hand from Perl when
> > appropriate.
>
> That's exactly what I *don't* want to be doing. I gave it UTF-8 -- it
> should be able to give me UTF-8 back.
You gave it utf-8 marker when it was really utf-8. It should give back utf-8
marker when it is really utf-8.
Regards,
Lace
