From: Sean L. <se...@ch...> - 2004-06-25 01:23:55
|
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?) - 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?) - 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! !!!!! -----Original Message----- From: pag...@li... [mailto:pag...@li...] On Behalf Of Boris Zentner Sent: Friday, June 25, 2004 8:47 AM To: pag...@li... Subject: Re: [Pagekit-users] RE: PageKit Hi Sean, Am Donnerstag 24 Juni 2004 07:38 schrieb Sean Lee: > Hello All, > > I am wondering if pagekit supports, or if it's not the pagekit, how to make > general system to support CJK charset in Content model. I need to have Just to be sure, by content you mean <PKIT_CONTENT sommething> right? > Content XML file to have Chinese, Korean, Japanese characters and switch I think it should work, but these charsets are unknown to me. Lets try it out. - First I do not know the charsets, how are the names for the three? - Is it possible to express all three in one common charset (UTF8 perhaps?)? my favorite charset is ISO-8859-1 or nowdays ISO-8859-15. > between them with pkit_lang. > a quick test looks good to me. See the attached files: jap.xml jap.tmpl Copy jap.xml into your Content directory. Copy jap.tmpl into View/Default. Then call http://your_site/jap and you get either the japan version if your favorite lang is ja or the default en version. To force a special version set pkit_lang either with pkit_lang in the url ( http://your_site/jap?pkit_lang=ja ) or from your modelcode. Perhaps you need to change default_input_charset and default_output_charset in your Config.xml to UTF8. There are some more pitfalls that you may encount later, while uploading someting to your server via areatext and serialize data to a database or XS ( C ). If you lose the UTF8 flag you need to restore it yourself. But this is another story. Let me know how it works so far. If you have any difficulty, I try to help on the charset issue. > Thank you, > Sean > -- Boris |