From: Boris Z. <bz...@2b...> - 2004-06-25 06:40:09
|
Hi Sean, Am Donnerstag 24 Juni 2004 11:23 schrieb Sean Lee: > Nice, it works!! Tin-q Boris!! > I have tried editing file with editor and save it and it works with all of > 3 languages correctly. (HZ KO JA from internet explorer languages > preferences) > > Now, let me have MySQL setup and testing along with Content .xml and MySQL > data together, if they consistently display characters fine. > > Some questions, > > - Like you said, textarea doesn't display correctly, is there anyway to get > this field to do it correctly? (like for say, if I need to make file editor > on web to modify content.xml files online?) > Textarea should work fine, but at least on the display side. The problem is basicly you send data to the client with some encoding, and the client send it back in another encoding. Unfortunely Mozilla and IE do it different. So you need some action to parse the input. I investigate the textarea thing. Often it is a lost UTF8 flag. > - Is there any way to NOT to use UTF-8 encoding setting on 'browser' and > display language correctly on web with choosing 'Japanese (Auto-detect)'? > Currently I must choose UTF-8, while this will help other charsets (KO,HZ) > to display correctly, but is there way to have browser on 'Japanese > (Auto-detect)' encoding mode and just display Japanese correctly and have > other two (KO,HZ) broken? And vise versa? (While I'm on KO encoding for > Korean, Japanese and Chinese characters break?) I do not understand all this, but what is broken, if you look at the page in UTF8? Then all three languages should be ok. Otherwise the encoding is broken somewhere. And there should be no need to force the browser to use utf8 encoding, the browser should chooce the right encoding if you allow it ( autoencoding ). > > - If I remember it correctly, using these charsets had some weird problems > with fillinform, but I'll find more on this before I ask > > Anyways, Thank you so much Boris! > !!!!! [...] -- Boris |