Re: [apps-discuss] Documenting UTF-1 as Historic

[Mykyta Yevstifeyev <[e-mail]>]

10.06.2011 21:44, Frank Ellermann wrote:
> On 10 June 2011 17:34, Mykyta Yevstifeyev wrote:
>
>> I suppose it could be formally documented
>> in Historic RFC
> In theory.  But the IETF (etc.) never used UTF-1
> for anything.  ISO deprecated UTF-1 years ago,
> and of course they still formally document it:
>
> http://www.itscj.ipsj.or.jp/ISO-IR/178.pdf
>
> Admittedly that page is hard to find, but OTOH
> the en-wikipedia UTF-1 article lists it as its
> one and only external reference (at the moment).
>
>>   Any thoughts on this?
> Unless somebody did it already:  It would be a
> very good thing to deprecate UTF-7 "officially"
> in an RFC, because UTF-7 is at least in theory
> an IETF invention.
Indeed; however if we want to deprecate its use, we should provide 
reasonable justification for it.  Maybe a reason may be "UTF-7 was 
written specially for RFC 822 purposes, which is obsolete", but I am not 
sure if it is appropriate.
> There was an AD willing to sponsor this effort
> in 2007, maybe the new ADs also like the idea.
> The author of the UTF-7 RFC has no objections
> (and should certainly get credits for his stunt
>   to register a "moving target" as IANA charset
>   before UTF-8 existed, and when Unicode was
>   still only registered with a version number).
>
> As far as HTML5 and WhatWG care about standards
> they should also welcome if UTF-7 is "formally"
> dead.  If you volunteer for this effort you can
> also talk about UTF-1 "just for the records" if
> you wish.
I'll then firstly discuss the issue with ADs before taking any action.
> -Frank
>