Re: [mobileOK] i18n comment: UTF8 should be explicit

 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/20070321154011.192714F0E0@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 2
> At http://www.w3.org/International/reviews/0703-mobileok/
> Editorial/substantive: S
> Owner: RI
> 
> Location in reviewed document:
> 3.3 CHARACTER_ENCODING_SUPPORT and CHARACTER_ENCODING_USE
> 
> Comment: 
> [[If character encoding is not explicitly specified in at least one of
> these ways, FAIL]]
> 
> 
> Given the goals of this test, shouldn't this say "If the UTF-8
> character encoding is not explicitly specified..." ?


Working Group Resolution:
Change text to simplify and remove other reference to UTF-8 in same
passage.

----

Received on Monday, 4 June 2007 14:14:05 UTC