Actually I found a way to solve that problem:

 In the <html tag, if we specify the lang="ja" , then the problem
disappear !!



On 3 Aug, 11:14, Jerome Eteve <[EMAIL PROTECTED]> wrote:
> Hi all,
>  we are currently translating our website in japanese. Our system and
> our website is full utf-8 .
>
> Here is a problem we have:
>
>  Under linux/firefox 2.0 , the rendering is different if a webpage is
> encoded in euc-jp or in utf-8.
>
> I did some tests with yahoo.jp home page:
>
> - Have a look at yahoo.jp in firefox . All the characters are nicely
> displayed and antialiased.
>  This page is encoded as euc-jp
>
> - Save the yahoo.jp home page html .
> - Change the encoding from euc-jp to utf-8:
>   iconv -f euc-jp -t utf-8 yahoohome.html > yahoohome_utf8.html
>
> - Now open yahoohome_utf8.html in firefox, set the view -> character
> encoding to utf8 (it's still stated in the file that it's a euc-jp
> page).
>
> If you compare the two versions,
>  - the one with euc-jp encoded character is perfect.
>  - the one with utf-8 encoded characters have got the same characters
> everywhere but about half of them is display very roughly, without any
> antialising.
>
> As far as I understand how character encoding works, the encoding of
> the page should not influence the picked code point of the displayed
> character, but here apparently it's the case.
> The encoding seems to have an effect on which character is picked from
> the character set.
>
> This problem doesn't appear in ie for linux ( 
> fromhttp://www.tatanka.com.br/ies4linux/page/Main_Page) nor in ie or
> firefox for windows
>
> I'm a bit confused.
>
> Thanks for any help !
>
> Jerome


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake 
PHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to