Netscape 4.x and earlier did not use Unicode.
Netscape (and Mozilla) 6.x do all internal processing in Unicode.
Just to be accurate, the referenced URL,
http://www.hclrss.demon.co.uk/unicode/netscape.html should be
From Character Coding on the View menu, you can see which character
set or code page Navigator 6 is using to display the current page,
From Character Coding on the View menu, you can see which encoder
was used to convert the web page into Unicode and correspondingly
which font preference Netscape Communicator (or Mozilla) 6.x is
using to display the page if the CSS does not specify a font,
Tim Walters wrote:
Markus Kuhn wrote:
Andrew McNaughton wrote on 2001-08-05 10:38 UTC:
You can send Unicode directly to the Web browser. Just make sure you
announce in the HTTP header that the body is encoded in UTF-8.
Sounds nice, but in practice this excludes a lot of users still.
Not really. All M$-Win32 browsers support UTF-8 flawlessly.
I'm glad UTF-8 display is working well for you. Unfortunately, we have run
into a few UTF-8 bugs in Netscape Navigator which were a problem for our
application. I hope it's not too much off-topic to list the two big ones, in
case other readers run into them also:
- There are some non-negligible setup issues (nicely detailed in one of Alan
Wood's Unicode Resource Pages,
http://www.hclrss.demon.co.uk/unicode/netscape.html). Unfortunately, you
have to set up a *single* "unicode" font for dealing with all characters,
whereas most machines just have fonts for specific scripts lying around
(i.e., a font for Japanese, a font for Korean, etc.) If you select a
Japanese font for Unicode display it will work fine for Japanese and other
characters in the font, but won't be able to deal with Korean or other
characters which aren't included. Netscape misbehaved and crashed a lot when
I tried to get it to use the huge Microsoft Unicode font with all of the
- Text input boxes in forms only accept characters in the "ANSI" system code
page. You can't enter or edit Japanese data, even if you can display it.
IE5 does not have these problems and, of course, it's much more stable. If
you (and the browsers viewing your pages) can stick to IE5, UTF-8 shouldn't
be a problem.