- From: Richard Ishida <ishida@w3.org>
- Date: Thu, 25 Aug 2005 12:43:59 +0100
- To: "'Deborah Cawkwell'" <deborah.cawkwell@bbc.co.uk>
- Cc: "'Richard Ishida'" <ishida@w3.org>, "GEO" <public-i18n-geo@w3.org>
Hi Deborah, Please take note of all the comments made in this thread and prepare some proposal for what we should accept and how we should deal with it. Cheers, RI PS: I suspect we should have a section called "Script-specific issues" where we give examples of the type of thing that may need to be considered. Handling Hebrew pages in visual order is clearly one of those examples. ============ 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/ -----Original Message----- From: Frank Yung-Fong Tang [mailto:ytang0648@aol.com] Sent: 23 August 2005 20:02 To: Richard Ishida Cc: www-international@w3.org Subject: Re: New article for REVIEW: Upgrading from language-specific legacy encoding to Unicode encoding I think you should mention not only charset with HTML, but also issue with CSS and seperate JavaScript file. The issue with \ unicode in CSS is quite tricky. 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/ > > >
Received on Thursday, 25 August 2005 11:44:12 UTC