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

Re: [mobileOK] i18n comment: Specifying script info

From: <mike@w3.org>
Date: Thu, 07 Jun 2007 16:11:54 +0000
To: <ishida@w3.org>
Cc: public-bpwg-comments@w3.org
Message-Id: <E1HwKaY-0002da-G0@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/20070321154053.6EC634F0E0@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 6
> At http://www.w3.org/International/reviews/0703-mobileok/
> Editorial/substantive: S
> Owner: FS
> 
> Location in reviewed document:
> 3.3 CHARACTER_ENCODING_SUPPORT and CHARACTER_ENCODING_USE
> 6.3.1 Annotation element
> 
> Comment: 
> A personal comment from Felix Sasaki, not endorsed by the i18n core
> WG.
> 
> 
> [[For each external resource as defined in 2.3.5 Included Resources:
> Request the URI indicated by the href attribute If the HTTP response
> Content-Type header value specifies an Internet media type starting
> with "text/" but does not specify UTF-8 encoding(e.g. "text/css" only
> instead of "text/css;charset=UTF-8"), warn PASS]] 
> 
> 
> Should a @charset rule in an included CSS stylesheet be taken into
> account? I.e., should there also be a warning if such a rule specifies
> an encoding different that UTF-8?


Working Group Resolution:
The DDC offers CSS Level 1 + @media support only

----
Received on Thursday, 7 June 2007 16:11:56 UTC

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