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

Re: New article for REVIEW: Upgrading from language-specific legacy encoding to Unicode encoding

From: Chris Lilley <chris@w3.org>
Date: Wed, 12 Oct 2005 17:24:35 +0200
Message-ID: <1646037342.20051012172435@w3.org>
To: "Deborah Cawkwell" <deborah.cawkwell@bbc.co.uk>
Cc: "Frank Yung-Fong Tang" <ytang0648@aol.com>, "Richard Ishida" <ishida@w3.org>, <www-international@w3.org>, <member-i18n-geo@w3.org>

On Wednesday, October 12, 2005, 5:10:34 PM, Deborah wrote:

DC> Hi Frank

DC> Could you clarify: we're not sure what problem you refer to.

I suspect it might be
in particular point 4 of the bulleted list for figuring out the charset
of a CSS file:

4. charset of referring stylesheet or document (if any)

Clearly if a.html and b.html are in different encodings, both refer to
c.css which does not have a BOM and does not have an @charset, then
there can be a problem.

DC>  Possibly:

DC> - if you change encoding of your HTML, you should ensure no knock ons with other files
DC> or 
DC> - class defined in another language
DC> or
DC> - something else?

DC> Many thanks

DC> Deborah

DC> -----Original Message-----
DC> From: www-international-request@w3.org on behalf of Frank Yung-Fong Tang
DC> Sent: Tue 8/23/2005 20:02
DC> To: Richard Ishida
DC> Cc: www-international@w3.org
DC> Subject: Re: New article for REVIEW: Upgrading from
DC> language-specific legacy encoding  to Unicode encoding

DC> I think you should mention not only charset with HTML, but also issue 
DC> with CSS and seperate JavaScript file. The issue with \ unicode in CSS 
DC> is quite tricky.

DC> Richard Ishida wrote on 8/23/2005, 1:45 PM:

 >> Title: Upgrading from language-specific legacy encoding to Unicode
 >> encoding
 >> http://www.w3.org/International/questions/qa-utf8-upgrade.html
 >> Comments are being sought on this article prior to final release.
 >> Please send any comments to www-international@w3.org. We expect to
 >> publish a final version in one to three weeks.
 >> This article provides an answer to the question: What should I
 >> consider when upgrading my web pages from legacy encoding to Unicode
 >> encoding?
 >> ============
 >> Richard Ishida
 >> W3C
 >> contact info:
 >> http://www.w3.org/People/Ishida/
 >> W3C Internationalization:
 >> http://www.w3.org/International/
 >> Publication blog:
 >> http://people.w3.org/rishida/blog/

DC> http://www.bbc.co.uk/

DC> This e-mail (and any attachments) is confidential and may contain
DC> personal views which are not the views of the BBC unless specifically
DC> stated.
DC> If you have received it in error, please delete it from your system. 
DC> Do not use, copy or disclose the information in any way nor act in
DC> reliance on it and notify the sender immediately. Please note that the
DC> BBC monitors e-mails sent or received. 
DC> Further communication will signify your consent to this.

 Chris Lilley                    mailto:chris@w3.org
 Chair, W3C SVG Working Group
 W3C Graphics Activity Lead
 Co-Chair, W3C Hypertext CG
Received on Wednesday, 12 October 2005 15:24:49 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:40:51 UTC