| CARVIEW |
Select Language
HTTP/2 200
date: Wed, 08 Oct 2025 21:47:52 GMT
content-type: text/html
content-encoding: gzip
last-modified: Thu, 13 Jul 2023 18:23:49 GMT
cache-control: max-age=2592000, public
expires: Fri, 07 Nov 2025 21:47:52 GMT
vary: Accept-Encoding
access-control-allow-origin: *
x-request-id: 98b8d6d299878839
strict-transport-security: max-age=15552015; preload
x-frame-options: deny
x-xss-protection: 1; mode=block
cf-cache-status: MISS
set-cookie: __cf_bm=c6ZZSUI0mHjhSXeBaJX_mReBn6UdjSIxfWQ4lfRSJfY-1759960072-1.0.1.1-WiRgjN4yVR0oTLc1fcIiqp0Ip6Dmb7jVFNWfyTmQqrKYW24RF7DRK1wQUyhfaL82TYpJe6ACRtx_.0Cv2IoWfdUtfYrkgV3F94OlSB0Kv1U; path=/; expires=Wed, 08-Oct-25 22:17:52 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98b8d6d299878839-BLR
alt-svc: h3=":443"; ma=86400
I18N-ISSUE-246: Clarify character encoding behavior when calculating storage size [ITS-20] from Internationalization Working Group Issue Tracker on 2013-01-19 (public-multilingualweb-lt-comments@w3.org from January 2013)
I18N-ISSUE-246: Clarify character encoding behavior when calculating storage size [ITS-20]
- From: Internationalization Working Group Issue Tracker <sysbot+tracker@w3.org>
- Date: Sat, 19 Jan 2013 06:07:47 +0000
- To: public-multilingualweb-lt-comments@w3.org,www-international@w3.org
- Message-Id: <E1TwRal-0002xN-47@tibor.w3.org>
I18N-ISSUE-246: Clarify character encoding behavior when calculating storage size [ITS-20] https://www.w3.org/International/track/issues/246 Raised by: Norbert Lindenberg On product: ITS-20 https://www.w3.org/TR/2012/WD-its20-20121206/#storagesize Several aspects of the interpretation of the character encoding given as storageEncoding need to be clarified: - Which character encodings is an implementation required to support? Support for UTF-8 must be mandatory. - What's the required behavior if storageEncoding specifies a character encoding that the implementation doesn't support? - What's the required behavior if the selected nodes contain characters that the specified character encoding cannot represent?
Received on Saturday, 19 January 2013 06:07:50 UTC