Hi Gene,
You wrote:
the chance to select the "Encoding:" is next below that
True. Windows started using Unicode as of Win2K. I was surprised indeed to find the Unicode option in Win98's Wordpad. I was surprised again today when opening in Unired a file saved as 'Unicode text' with Wordpad. Unired said it was no utf-8, it was utf-16 (Little Endian) instead, so sending it as utf-8 would be incorrect, even if Mozilla seemed not to care that much.
I thought nothing of the fact that I have not seen such a result in IE6 and Mozilla 1.7.
Mozilla 1.7.5 still proudly displays an ugly BOM, IE doesn't.
All of my efforts, so far, are stand-alone and intranet applications, so I don't know what to expect from actually having the file on a true server situation accessed from the Internet.
As long as you have a web server on your intranet it shouldn't do any difference to the browser, it's just documents coming from the network. It's files from your disk that will miss the http headers.
Urk! Fortunately, my files are English-language with a few &#... codes for "proper" typographic punctuation and some characters in names
This works, but after a few characters it just becomes tiring ...
One thing I've just thought of. The final hurdle in letting the world see vietnamese text is hoping that the visitor's browser has a font capable of displaying the text. There is not much you can do if it doesn't, but if it has one you should allow the browser to choose it avoiding to declare a font-family for that part of the page.
djn
begin:vcard fn:Dejan Kozina n:Kozina;Dejan org:Dejan Kozina Web Design Studio adr:;;Dolina 346;Dolina;TS;I-34018;Italy email;internet:[EMAIL PROTECTED] tel;work:+39 348 7355 225 tel;fax:+39 040 228 436 tel;cell:+39 348 7355 225 x-mozilla-html:TRUE url:http://www.kozina.com/ version:2.1 end:vcard
