Re: Re: mbstring: Japanese conversion not working for me

Привет! Jean-Christian Imbeault wrote:

I tried EUC-JP and ISO-2022-JPand neither worked. Ah well ... so much for a nice idea quick hack to displaying multiple charsets at once.

They should. I checked out w3c.org at that and it definitely should. No exception for japanese mentioned anywhere. The two parameters actually open a local exception from the <meta http-equiv="Content-Language" content="{LANCODE}"> <meta http-equiv="Content-Type" content="text/html; charset={CHARSET}"> headers. And SPAN sections can be nested. At least, so the standard goes. Besides, while checking the docs I stepped onto something really funny (to say the very least). I quote from http://www.htmlcompendium.org/attributes-list/attributes-notes/lang.htm ------------------- The argument to the "lang=" attribute is made up of two parts; a primary code and an optional subcode (separated by a "-" hyphen). The primary code is a two character language code. i.e.<tag lang="en"> The subcode is "understood to be a (ISO 3166) country code". However, W3C also gives several examples: <tag lang="en-US"> <tag lang="en-cockney"> <tag lang="i-cherokee"> They also propose a method of handling such "artificial languages" as Elfish and Klingon. For such languages they propose the primary code of "x" --------------------- Now I hope I shall never manage a porting to a Klingon repository LOLOL Anyway, if you do not need it for your application but just for a debugging procedure you can just forget about it :) пока Альберто Киев @-_=}{=_-@-_=}{=_-@-_=}{=_-@-_=}{=_-@-_=}{=_-@-_=}{=_-@-_=}{=_-@ LoRd, CaN yOu HeAr Me, LiKe I'm HeArInG yOu? lOrD i'M sHiNiNg... YoU kNoW I AlMoSt LoSt My MiNd, BuT nOw I'm HoMe AnD fReE tHe TeSt, YeS iT iS ThE tEsT, yEs It Is tHe TeSt, YeS iT iS ThE tEsT, yEs It Is.......