W3C home > Mailing lists > Public > public-i18n-core@w3.org > April to June 2006

[Fwd: Re: [MWBP 1.0] i18n comment: No mention of metacharset]

From: Felix Sasaki <fsasaki@w3.org>
Date: Thu, 13 Apr 2006 17:21:22 +0900
Message-ID: <443E0A02.7090203@w3.org>
To: "public-i18n-core@w3.org" <public-i18n-core@w3.org>
FYI

attached mail follows:



 Dear <fsasaki@w3.org>,

The Mobile Web Best Practice Working Group has reviewed the comments you
sent [1] on the Last Call Working Draft [2] of the Mobile Web Best
Practices 1.0 published on 13 January 2006 Thank you for having taken the
time to review the document and to send us comments!

This message holds the disposition of the said comments on which the
Working Group has agreed. This disposition has been implemented in the new
version of the document available at:
http://www.w3.org/TR/2006/WD-mobile-bp-20060412/

Please review it carefully and let us know if you agree with it or not
before 3 May 2006. In case of disagreement, you are requested to provide a
specific solution for or a path to a consensus with the Working Group. If
such a consensus cannot be achieved, you will be given the opportunity to
raise a formal objection which will then be reviewed by the Director
during the transition of this document to the next stage in the W3C
Recommendation Track.

Thanks,

For the Mobile Web Best Practice Working Group,
Philipp Hoschka
Dominique Hazaƫl-Massieux
W3C Staff Contacts

 1. http://www.w3.org/mid/20060222165443.6A738439B@toro.w3.mag.keio.ac.jp
 2. http://www.w3.org/TR/2006/WD-mobile-bp-20060113/


=====

Your comment on [CHARACTER_ENCODING_...:


Comment from the i18n review of:
http://www.w3.org/TR/2006/WD-mobile-bp-20060113/

Comment 18
At http://www.w3.org/International/reviews/0602-mwbp10/
Editorial/substantive: S
Owner: RI
Location in reviewed document:
5.4.12

Comment:
 
The section mentions the use of the XML declaration for declaring
in-document the encoding of XML documents, but makes no mention of the
standard in-document declaration of encoding for HTML documents or XHTML
served as text/html, which uses the Content-Type meta element. This seems
a strange omission. Please add text describing this.


Working Group Resolution:
We have added a link to the I18N tutorial on specifying the encoding and
have added the specific case you mention in the related technique:

http://www.w3.org/2005/MWI/BPWG/techs/SpecifyingCharacterEncoding



(note that the document only focuses on XHTML, not on HTML)

----




Received on Thursday, 13 April 2006 08:21:31 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 1 October 2008 10:18:50 GMT