W3C home > Mailing lists > Public > public-bpwg-comments@w3.org > April to June 2007

Re: [mobileOK] i18n comment: use of e.g.

From: <mike@w3.org>
Date: Mon, 04 Jun 2007 14:14:03 +0000
To: <ishida@w3.org>
Cc: public-bpwg-comments@w3.org,public-i18n-core@w3.org
Message-Id: <E1HvDJr-0006Lx-QC@wiggum.w3.org>


 Dear <ishida@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 W3C mobileOK Basic
Tests 1.0 published on 30 Jan 2007. Thank you for having taken the time to
review the document and to send us comments!

The Working Group's response to your comment is included below, and has
been implemented in the new version of the document available at:
http://www.w3.org/TR/2007/WD-mobileOK-basic10-tests-20070525/

Please review it carefully and let us know if you agree with it or not
before 22 June 2007. 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,
Michael(tm) Smith
W3C Staff Contact

 1. http://www.w3.org/mid/20070321153932.52DB44F118@homer.w3.org
 2. http://www.w3.org/TR/2007/WD-mobileOK-basic10-tests-20070130/


=====

Your comment on 3.3 CHARACTER_ENCODING_SUPPORT and CHARACTER_ENCODING_USE:
> Comment from the i18n review of:
> http://www.w3.org/TR/2007/WD-mobileOK-basic10-tests-20070130/
> 
> Comment 1
> At http://www.w3.org/International/reviews/0703-mobileok/
> Editorial/substantive: E
> Owner: RI
> 
> Location in reviewed document:
> 3.3 CHARACTER_ENCODING_SUPPORT and CHARACTER_ENCODING_USE
> 
> Comment: 
> [[
> - Content-Type header (e.g. "application/xhtml+xml;charset=UTF-8")
> 
> - XML declaration (e.g. "<?xml encoding="UTF-8"?>")
> 
> - meta element that is the first child of the document's head element,
> and whose http-equiv attribute is "Content-Type", and whose content
> attribute specifies a character encoding as above (e.g.
> "<metahttp-equiv="Content-Type"
> content="application/xhtml+xml;charset=UTF-8"/>)
> ]]
> 
> Since this test is testing for UTF-8 support, it should be made clearer
> that the reason 'e.g.' is used rather than 'i.e.' has to do with the
> other parts of the construct, rather than the encoding declaration
> itself.


Working Group Resolution:
Yes, change to "i.e.", but, also boldface the important parts of the given
strings: "application/xhtml+xml**;charset=UTF-8**"


----
Received on Monday, 4 June 2007 14:14:10 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:01:50 UTC