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

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

From: Barry Caplan <bcaplan@i18n.com>
Date: Thu, 07 Nov 2002 09:26:03 -0800
Message-Id: <5.1.0.14.2.20021107092404.054b6b00@mail.i18n.com>
To: "Diaz, Michelle (Bolton)" <mdiaz@husky.ca>(by way of Martin Duerst <duerst@w3.org>), www-international@w3.org

What if you just eliminate those meta tags completely? YOu will then be able to play with various combinations in the browser encoding settings to find out what it really is, and then you can consider your options on how to proceed?

You don't need to place the files on a server to do this, BTW, just save the source somewhere and do an "open file" in your browser.

HTH - 

Barry Caplan
www.i18n.com

At 10:52 PM 11/7/2002 +0900, Diaz, Michelle (Bolton) wrote:
>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.
Received on Thursday, 7 November 2002 12:23:11 GMT

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