W3C home > Mailing lists > Public > www-international@w3.org > January to March 2013

Re: I18N-ISSUE-246: Clarify character encoding behavior when calculating storage size [ITS-20]

From: Felix Sasaki <fsasaki@w3.org>
Date: Wed, 30 Jan 2013 11:57:17 +0100
Message-ID: <5108FC8D.2040307@w3.org>
To: Stephan Walter <stephan.walter@cocomore.com>
CC: "public-multilingualweb-lt-comments@w3.org" <public-multilingualweb-lt-comments@w3.org>, www-international <www-international@w3.org>
Thanks a lot, Stephan. Just to make sure Norbert sees this, I'm putting 
the www-international list into the loop.

- Felix

Am 29.01.13 13:34, schrieb Stephan Walter:
>
> Dear Norbert,
>
> this concerns issues 106 [1] and 107 [2] which you reported on the 
> draft specification of the ITS 2.0 Tagset Standard.
>
> At our last working group meeting we had a discussion on the topic. We 
> came to the conclusion that the specification need not impose any 
> requirements on implementations regarding supported character 
> encodings, behavior on encoding problems or representation of line breaks.
>
> In the context addressed by your issues this was not intended. The 
> storageEncoding and lineBreakType will enable an implementation to 
> make use of the storageSize information in a sensible way. The details 
> of how this information is used are however up to the implementation. 
>  We agreed to make this clearer by adding  a clarification to the end 
> of the definition of Storage Size (8.21.1) as follows:
>
> ===
>
> The storage size is expressed in bytes and is provided along with the 
> character set encoding used to store the content.
>
> ==>
>
> The storage size is expressed in bytes and is provided along with the 
> character set encoding, and optionally the line break type, that will 
> be used when the content will be stored. In order to check if the 
> translation of the content will fit inside the storage limit given by 
> storageSize, it has to be calculated whether the byte sequence that 
> results from encoding this translation is shorter than the given 
> limit. This byte sequence is to be produced using the specified 
> encoding (and possibly line break type).
>
> ===
>
> Would you agree that this answers the questions raised in your issues 
> in an appropriate way?
>
> Best regards
>
> Stephan Walter
>
> [1] 
> https://www.w3.org/International/multilingualweb/lt/track/issues/106, 
> http://www.w3.org/International/track/issues/246
>
> [2] 
> https://www.w3.org/International/multilingualweb/lt/track/issues/107, 
> http://www.w3.org/International/track/issues/247
>
>
> ________________________________________
> *Dr. Stephan Walter,* Senior IT-Consultant
> Tel.: +49 69 972 69 x Fax: +49 69 972 69 x; E-Mail: 
> stephan.walter@cocomore.com <mailto:stephan.walter@cocomore.com>
> *Cocomore AG,* Gutleutstraße 30, D-60329 Frankfurt
> Internet: http://www.cocomore.de <http://www.cocomore.de/> Facebook: 
> http://www.facebook.com/cocomore Google+: http://plus.cocomore.de 
> <http://plus.cocomore.de/>
> Cocomore ist aktives Mitglied im World Wide Web Consortium (W3C) und 
> im Bundesverband Digitale Wirtschaft (BVDW)
>
> Cocomore is active member of the World Wide Web Consortium (W3C)
> Vorstand: Dr. Hans-Ulrich von Freyberg (Vors.), Dr. Jens Fricke, Marc 
> Kutschera,Vors. des Aufsichtsrates: Martin Velasco, Sitz: 
> Frankfurt/Main, Amtsgericht Frankfurt am Main, HRB 51114
>
Received on Wednesday, 30 January 2013 10:57:42 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 30 January 2013 10:57:42 GMT