![change text encoding browser chinese simplified gb2312 change text encoding browser chinese simplified gb2312](http://www.herongyang.com/PHP-Chinese/Web-Form-Input-Chinese-GB18030.jpg)
Earlier versions of NN3.x and NN4.x were great at automatically switching the page encoding seamlessly when that tag was in the.
![change text encoding browser chinese simplified gb2312 change text encoding browser chinese simplified gb2312](http://pinyin.info/news/news_photos/2015/10/UTF-8_website_use_2001-2010.png)
The last meta tag there is a holdover from the Netscape days for me. It's when you paste from MS Office documents directly into a WYSIWYG editor that you get all this unwanted formatting or gibberish. All you need is to have the proper IME in place and you're good to go. I can type Japanese into FP's WYSIWYG interface just fine. If you're entering the Chinese from scratch, i.e., typing it in and not copy & pasting it, then FP or DW seem to be fine even on an English OS. I would suggest that you consider using a 3rd party HTML editor on the side for times when you're entering your double byte content.
Change text encoding browser chinese simplified gb2312 windows#
One thing I have noticed is that I haven't had much luck using NotePad as an HTML editor on an English version of Windows for Japanese or Chinese content. I assume that the Chinese content looks OK in the source document, right? I'll bet it's the WYSIWYG that's the culprit here. My solution when using source materials in Word was to copy and paste the material directly into the HTML editor part of FP, and to avoid the WYSIWYG part of the program altogether. I've seen the exact same thing happen with FrontPage using Chinese and Japanese. )Ī2ztranslate has given you some excellent advice. I'm just a mild-mannered WebmasterWorld Mod. word to html editor) use unicode, and then you can change back to specific charset. if you have to work between applications (e.g. as long as translator sets charset at beginning of translation, and works with a true multilingual (or target language) html editor, you should not see these probems.Ģ. get translation done directly in the source code. in a student lab or in an internet cafe frequented by travellers) as the previous computer user may have set the "view" "text encoding" to a different charset.ġ. this will ensure that site displays correctly on computers that are set up for multiple languages (e.g. are you using a Chinese version of dreamweaver?ģ. so some English versions of dreamweaver only handles English characters correctly, no matter what the encoding.
![change text encoding browser chinese simplified gb2312 change text encoding browser chinese simplified gb2312](http://www.alanwood.net/unicode/firefox-osx-encoding-default.png)
some versions of dreamweaver have difficulty using characters other than the language version used. try pasting text into a standard multilingual non-microsoft text editor first, saving as correct encoding, and then moving to html.Ģ. you need to ensure that word has set the encoding correctly in the first place (microsoft products sometimes have issues if you are not using the localised version are you using a chinese version of word?). i think there are several possible causes here:ġ.