From: Ondra K. <ke...@or...> - 2005-03-11 21:03:14
|
But I think that when I have non-utf charset as default in iloha, message is _recode_ to my charset and _then_converted_ to utf html entities. I think that only one of this have to be used. Recode or convert to entities... Maybe I'm wrong, but I test my patch and works correctly. Without it i can't read any utf message correctly. Sun, Mar 06, 2005 ve 10:12:13PM -0600, Ryo Chijiiwa napsal: > Actually, it's the other way around. If you have a character set other > than UTF-8 selected, it won't know how to display raw UTF-8, so it > needs to be converted HTML entities (code in the form "&<decimal > value>;"). If your character set is already set to UTF-8, it'll > display raw UTF-8 without any additional encoding, although it'll still > show Unicode encoded as HTML entities just fine. > > If you could send me a sample message in UTF-8 that fails to show > properly in other character sets, I can take a look into further. > > Ryo > > On 3/4/2005, "Ondra Kudlik" <ke...@or...> wrote: > > >Hi, > > > >my users found a bug in charset conversion. When I am using non utf > >charset for pound and I got utf message, encoding is broken. > > > >Problem is in this condition: > > > >if ($is_unicode) $line = utf8ToUnicodeEntities($line); > > > >Its right if I am using utf charset and reading utf message, but when > >I'm reading non utf (iso-8859-2 in my case) it works bad. So I wrote > >patch which found if used charset is utf and modified the condition: > > > >if ($is_unicode && $my_charset_is_unicode) $line = utf8ToUnicodeEntities($line); > > > >I correct this only on two places in read_message_print.inc so maybe > >this problem is also in other files. > > > >Include this patch please if I'm correct. > > > >Bye -- .''`. Ondra 'Kepi' Kudlik : :' : Debian GNU/Linux User `. `' `- http://www.nosoftwarepatents.com/cz/m/intro/index.html |