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

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

State:
CLOSED
Product:
MLW-LT Standard Draft
Raised by:
Felix Sasaki
Opened on:
2013-01-20
Description:
See
http://lists.w3.org/Archives/Public/public-multilingualweb-lt-comments/2013Jan/0120.html
Related Actions Items:
Related emails:
  1. RE: ISSUE-106: I18N-ISSUE-246: Storage Size (from ysavourel@enlaso.com on 2013-04-07)
  2. Re: ISSUE-106: I18N-ISSUE-246: Storage Size (from fsasaki@w3.org on 2013-04-07)
  3. RE: ISSUE-106: I18N-ISSUE-246: Storage Size (from ysavourel@enlaso.com on 2013-04-06)
  4. Re: ISSUE-106: I18N-ISSUE-246: Storage Size (from asmusf@ix.netcom.com on 2013-04-06)
  5. RE: ISSUE-106: I18N-ISSUE-246: Storage Size (from ysavourel@enlaso.com on 2013-04-06)
  6. RE: ISSUE-106: I18N-ISSUE-246: Storage Size (from ysavourel@enlaso.com on 2013-04-04)
  7. AW: ISSUE-106: I18N-ISSUE-246: Storage Size (from stephan.walter@cocomore.com on 2013-04-04)
  8. Re: ISSUE-106: I18N-ISSUE-246: Storage Size (from joerg@bioloom.de on 2013-04-04)
  9. RE: ISSUE-106: I18N-ISSUE-246: Storage Size (from pablo.nieto@linguaserve.com on 2013-04-03)
  10. ISSUE-106: I18N-ISSUE-246: Storage Size (from ysavourel@enlaso.com on 2013-04-03)
  11. [Agenda] DRAFT MLW-LT call 3 April, noon UTC (from fsasaki@w3.org on 2013-04-03)
  12. AW: [ISSUE-106][I18N-ISSUE-246] Storage Size - unit (from stephan.walter@cocomore.com on 2013-04-02)
  13. RE: [ISSUE-106][I18N-ISSUE-246] Storage Size - unit (from pablo.nieto@linguaserve.com on 2013-04-02)
  14. [ISSUE-106][I18N-ISSUE-246] Storage Size - unit (from ysavourel@enlaso.com on 2013-04-01)
  15. Re: [Agenda] MLW-LT call 27 March, 1 p.m. UTC (from olaf@stefanov.at on 2013-03-27)
  16. [Agenda] MLW-LT call 27 March, 1 p.m. UTC (from fsasaki@w3.org on 2013-03-27)
  17. [Minutes] MLW-LT call 2013-03-04 (from fsasaki@w3.org on 2013-03-04)
  18. AW: I18N-ISSUE-246: Clarify character encoding behavior when calculating storage size [ITS-20] (from stephan.walter@cocomore.com on 2013-02-28)
  19. Re: [agenda] MLW-LT WG call 18th Feb 2013 15.00 UTC (from joerg@bioloom.de on 2013-02-18)
  20. RE: [agenda] MLW-LT WG call 18th Feb 2013 15.00 UTC (from ysavourel@enlaso.com on 2013-02-18)
  21. [agenda] MLW-LT WG call 18th Feb 2013 15.00 UTC (from dave.lewis@cs.tcd.ie on 2013-02-18)
  22. Re: I18N-ISSUE-246: Clarify character encoding behavior when calculating storage size [ITS-20] (from w3@norbertlindenberg.com on 2013-02-14)
  23. RE: I18N-ISSUE-246: Clarify character encoding behavior when calculating storage size [ITS-20] (from ysavourel@enlaso.com on 2013-01-30)
  24. Re: I18N-ISSUE-246: Clarify character encoding behavior when calculating storage size [ITS-20] (from fsasaki@w3.org on 2013-01-30)
  25. Re: I18N-ISSUE-246: Clarify character encoding behavior when calculating storage size [ITS-20] (from stephan.walter@cocomore.com on 2013-01-29)
  26. RE: New dial in details to come (Re: [Minutes] Prague f2f (draft) and Monday call) (from sgladkoff@logrus.ru on 2013-01-28)
  27. New dial in details to come (Re: [Minutes] Prague f2f (draft) and Monday call) (from fsasaki@w3.org on 2013-01-28)
  28. Re: [Minutes] Prague f2f (draft) and Monday call (from naoto.nishio@ul.ie on 2013-01-27)
  29. [Minutes] Prague f2f (draft) and Monday call (from fsasaki@w3.org on 2013-01-27)
  30. Re: [Minutes] MLW-LT call 2013-01-21 and "sheperds" ... (from fsasaki@w3.org on 2013-01-21)
  31. mlw-lt-track-ISSUE-106: I18N-ISSUE-246: Clarify character encoding behavior when calculating storage size [ITS-20] [MLW-LT Standard Draft] (from sysbot+tracker@w3.org on 2013-01-20)

Related notes:

Solution proposals from http://lists.w3.org/Archives/Public/public-multilingualweb-lt-comments/2013Jan/0195.html
"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 content will fit inside the storage limit given by storageSize, it has to be calculated whether the byte sequence that results from encoding this content is not longer than the given limit. This byte sequence is to be produced using the specified encoding (and possibly line break type)."

Felix Sasaki, 30 Jan 2013, 12:43:53

Mail to commenter at
http://lists.w3.org/Archives/Public/public-multilingualweb-lt-comments/2013Feb/0025.html

Felix Sasaki, 12 Feb 2013, 08:34:42

DECISION-DETAILS: Editorial ACTION-478 pending on Yves. Clarifications on why bytes are used as the only unit.

David Filip, 3 Apr 2013, 12:55:45

RESOLUTION: rejected

David Filip, 3 Apr 2013, 13:02:46

CHANGE-TYPE: editorial

David Filip, 3 Apr 2013, 13:04:06

[fsasaki]: COMMENTER-RESPONSE: satisfied, see http://www.w3.org/2013/04/04-i18n-minutes.html#action01

8 Apr 2013, 11:44:46

Mail from commenter at
http://lists.w3.org/Archives/Public/public-multilingualweb-lt-comments/2013Apr/0032.html

Felix Sasaki, 29 Apr 2013, 18:57:03

Display change log ATOM feed

Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 106.html,v 1.1 2014-01-21 15:46:09 kahan Exp $