Forwarded message 1
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/20060222165722.45B98439B@toro.w3.mag.keio.ac.jp
2. http://www.w3.org/TR/2006/WD-mobile-bp-20060113/
=====
Your comment on the document as a whole:
Comment from the i18n review of:
http://www.w3.org/TR/2006/WD-mobile-bp-20060113/
Comment 21
At http://www.w3.org/International/reviews/0602-mwbp10/
Editorial/substantive: S
Owner: RI
Location in reviewed document:
General
Comment:
We believe the document should encourage all participants in the mobile
value chain to support Unicode. This is extremely helpful in ensuring
international use of this technology and ease of localization of content.
Working Group Resolution:
This document only gives best practices on the content delivery, not to
the whole mobile value chain.
As the default delivery context assumes only UTF-8 support, this means
that by default, content providers should serve content UTF-8 encoded
(unless they know that the targeted device doesn't support it). As such,
we think we already encourage support of Unicode given the scope of the
document. Is there any other way we could/should encourage unicde
support?
We have however, added a note under 'How to do it' of [CHARACTER_ENCODING]
saying that the Default Delivery Context uses UTF-8 and that all
applications should support UTF-8.
----