Re: [Encoding] Rejected: Problems with non-standard implementations of emergent scripts [I18N-ISSUE-386]

Hi Addison,

Fine with resolution. It was expected response.

A.
On 30/08/2014 1:19 AM, "Phillips, Addison" <addison@lab126.com> wrote:

> Hello Andrew,
>
> You commented a while ago [2] on the Encoding spec (and reiterated it a
> few times in the past 24 hours on the "false statement" thread) about the
> problem of non-standard uses of the UTF-8 encoding for emerging or
> otherwise unencoded scripts and languages. The I18N WG is tracking this
> comment separately as issue 386 [1].
>
> The I18N WG discussed this comment and has rejected it as out of scope for
> inclusion in Encoding. Our reasoning is that, while we recognize the
> problem and agree that this is an area of concern, it is out of scope for
> the Encoding specification. Encoding concerns itself with identifying and
> transcoding legacy encodings to/from Unicode code points (as well as
> strongly recommending/requiring the use of UTF-8 in the future). Since the
> problem you identified has to do with pages that are already using/abusing
> the UTF-8 encoding, we don't see this as something Encoding can directly
> address.
>
> Could you please reply to this message indicating if you are satisfied
> with this resolution.
>
> Thanks (for I18N),
>
> Addison
>
> [1] http://www.w3.org/International/track/issues/386
> [2]
> http://lists.w3.org/Archives/Public/www-international/2014AprJun/0285.html
>
> Addison Phillips
> Globalization Architect (Amazon Lab126)
> Chair (W3C I18N WG)
>
> Internationalization is not a feature.
> It is an architecture.
>
>