Re: [MWBP 1.0] i18n comment: Bandwith / cost related toscripts

[Sorry for the duplicate]

  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/20060222164357.44D644390@toro.w3.mag.keio.ac.jp
 2. http://www.w3.org/TR/2006/WD-mobile-bp-20060113/


=====

Your comment on 2.3 
Bandwidth and Cost
:
Comment from the i18n review of:

http://www.w3.org/TR/2006/WD-mobile-bp-20060113/



Comment 7

At http://www.w3.org/International/reviews/0602-mwbp10/

Editorial/substantive: E

Owner: FS

Location in reviewed document:

Sec.2.3
[http://www.w3.org/TR/2006/WD-mobile-bp-20060113/#iddiv2102173616]



Comment:

 

In some character encodings like UTF-8, scripts with a similar number of
characters (e.g. latin versus indic scripts) vary in space requirements.
To avoid high bandwidth / cost related to scripts, you might propose for
such cases the use of the 

compression scheme for unicode [http://www.unicode.org/reports/tr6/]

..

Working Group Resolution:
We have not found sufficient support for this encoding scheme in mobile
devices.

----

Received on Wednesday, 12 April 2006 17:13:50 UTC