W3C home > Mailing lists > Public > www-international@w3.org > October to December 2002

RE: Shift_JIS , UTF-16, iso-2022-jp

From: Etienne Kroger <etienne.kroger@welocalize.com>
Date: Thu, 7 Nov 2002 09:19:07 -0500
To: "'Diaz, Michelle \(Bolton\) \(by way of Martin Duerst <duerst@w3.org>\)'" <mdiaz@husky.ca>, <www-international@w3.org>
Message-ID: <000f01c28668$a2ac8050$1564a8c0@frederick.welocalize.com>


a few points you may consider:

- most servers don't support utf-16.

- are you sure that the actual encoding matches what your tag announces?

- in some cases, you may have font tag issues as well, i.e. you may be
forcing the browser to use a font that does not offer japanese glyphs.

etienne

-----Original Message-----
From: www-international-request@w3.org
[mailto:www-international-request@w3.org]On Behalf Of Diaz, Michelle
(Bolton) (by way of Martin Duerst <duerst@w3.org>)
Sent: Thursday, November 07, 2002 8:53 AM
To: www-international@w3.org
Subject: Shift_JIS , UTF-16, iso-2022-jp
Importance: High






Hi there,

I'm hoping someone can help me. We send out html files for Japanese
translation. These files are returned with the encoding:

<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=UTF-16">
<META HTTP-EQUIV="Content-Language" CONTENT="jp">

With this encoding, I cannot view the Japanese fonts, only box characters. I
tried using other encodings: Shift_JIS, and iso-2022-jp. But these all don't
seem to work.

What other things could I pinpoint to know why these fonts are displaying
properly? Could it be the use of text editor versus html editor?  Am I
missing another tag?

Please help me! Thanks in advance.
Michelle
Received on Thursday, 7 November 2002 09:23:36 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 19:16:59 GMT