RE: Never too late to fix a problem! (charset-fixes)

This is fine with me, and better than my suggestion.
Michelle, please do it.

         Harald

--On 18. juni 2001 12:16 +0900 Martin Duerst <duerst@w3.org> wrote:

> Hello Michelle, Harald,
>
> Many thanks for your quick answers.
>
> Currently, the entries look like
>
> Name: ISO_8859-6-E                                       [RFC1556,IANA]
> MIBenum: 81
> Source: RFC-1556
> Alias: csISO88596E
>
> I think Harald is proposing to change that to
>
> Name: ISO-8859-6-E                                       [RFC1556,IANA]
> MIBenum: 81
> Source: RFC-1556
> Alias: csISO88596E
>
> i.e. just changing the _ to a - in the Name. Given that these
> entries have been around in the present form for a long time, I would
> prefer to add the correct label as an alias, and keep the current Name,
> as follows:
>
> Name: ISO_8859-6-E                                       [RFC1556,IANA]
> MIBenum: 81
> Source: RFC-1556
> Alias: csISO88596E
> Alias: ISO-8859-6-E (preferred MIME name)
>
> The other three entries then would look as follows:
>
> Name: ISO_8859-6-I                                       [RFC1556,IANA]
> MIBenum: 82
> Source: RFC-1556
> Alias: csISO88596I
> Alias: ISO-8859-6-I (preferred MIME name)
>
> Name: ISO_8859-8-E                                  [RFC1556,Nussbacher]
> MIBenum: 84
> Source: RFC-1556
> Alias: csISO88598E
> Alias: ISO-8859-8-E (preferred MIME name)
>
> Name: ISO_8859-8-I                                  [RFC1556,Nussbacher]
> MIBenum: 85
> Source: RFC-1556
> Alias: csISO88598I
> Alias: ISO-8859-8-I (preferred MIME name)
>
>
> Regards,   Martin.
>
>
> At 00:12 01/06/17 +0200, Harald Tveit Alvestrand wrote:
>
>
>> --On 16. juni 2001 08:02 -0700 IANA <iana@icann.org> wrote:
>>
>>> Dear Martin,
>>>
>>> Apologies that this was never taken care of.  Olle's request came
>>> through before I came on board.
>>>
>>> Harald, is any approval required to make these changes?
>>>
>>> Am I correct in understanding that the charset file should appear as
>>> follows:
>>
>> No - dash in the wrong place.
>>>
>>> Name: ISO_8859-6-E                                       [RFC1556,IANA]
>>
>> The NAME needs to change to ISO-8859-6-E to be consistent with the RFC.
>> The error was done when transcribing the names from RFC 1556 to the IANA
>> registry.
>>
>>> MIBenum: 81
>>> Source: RFC1556
>>> Alias: csISO88596E
>>>
>>> Name: ISO_8859-6-I                                       [RFC1556,IANA]
>>> MIBenum: 82
>>> Source: RFC1556
>>> Alias: csISO88596I
>>>
>>> Name: ISO_8859-8-E                                  [RFC1556,Nussbacher]
>>> MIBenum: 84
>>> Source: RFC1556
>>> Alias: csISO88598E
>>>
>>> Name: ISO_8859-8-I                                  [RFC1556,Nussbacher]
>>> MIBenum: 85
>>> Source: RFC1556
>>> Alias: csISO88598I
>>>
>>>
>>> :    Examples of new character sets for bi-directionality support:
>>> :
>>> :             Content-type: text/plain; charset=ISO_8859-6-e
>>> :             Content-type: text/plain; charset=ISO_8859-6-i
>>> :             Content-type: text/plain; charset=ISO_8859-8-e
>>> :             Content-type: text/plain; charset=ISO_8859-8-i
>>> :
>>> :    The "i" suffix refers to implicit mode and the "e" suffix refers to
>>> :    explicit mode.
>>>
>>> Please confirm that this is correct.
>>>
>>> Thanks,
>>>
>>> Michelle Schipper
>>> IANA
>>>
>>>
>>>
>>> -----Original Message-----
>>> From: Martin Duerst [mailto:duerst@w3.org]
>>> Sent: Saturday, June 16, 2001 2:15 AM
>>> To: ietf-charsets@iana.org
>>> Cc: iana@iana.org; Harald Tveit Alvestrand
>>> Subject: Never too late to fix a problem!
>>>
>>>
>>> Having a look at the charset registry
>>> (http://www.iana.org/assignments/character-sets),
>>> I just rediscovered the following error, already
>>> reported by Olle Jarnefors in 1996!
>>> http://lists.w3.org/Archives/Public/ietf-charsets/1996JulDec/0000.html
>>>
>>> What is the right way to fix such problems once and for all?
>>>
>>> Regards,   Martin.
>>>
>>>
>>> Date: Mon, 08 Jul 1996 18:23:30 +0200
>>> From: Olle Jarnefors <ojarnef@admin.kth.se> Subject: Errors in charset
>>> registrations for Arabic and Hebrew
>>> To: iana@isi.edu
>>> Cc: ietf-charsets@INNOSOFT.COM, ilan-h@taunivm.tau.ac.il,
>>> Message-id: <9607081623.AA19350@mercutio.admin.kth.se>  There are four
>>> small but significant errors in the
>>> registrations of four charset values for Arabic and
>>> Hebrew character sets defined in RFC 1556.
>>> <ftp:ftp.is.edu/in-notes/iana/assignments/character-sets> includes the
>>> registrations:
>>>  > Name: ISO_8859-6-E
>>>  > [RFC1556,IANA] MIBenum: 81
>>>  > Source: RFC-1556
>>>  > Alias: csISO88596E
>>>  > > Name: ISO_8859-6-I
>>> [RFC1556,IANA]  > MIBenum: 82
>>>  > Source: RFC-1556
>>>  > Alias: csISO88596I
>>>  > Name: ISO_8859-8-E
>>> [RFC1556,Nussbacher]  > MIBenum: 84
>>>  > Source: RFC-1556
>>>  > Alias: csISO88598E
>>>  > > Name: ISO_8859-8-I
>>> [RFC1556,Nussbacher]
>>>  > MIBenum: 85
>>>  > Source: RFC-1556
>>>  > Alias: csISO88598I
>>> RFC 1556, however, uses "-", not "_", after "ISO" in the
>>> charset values:
>>> :    Examples of new character sets for bi-directionality support:
>>> :
>>> :             Content-type: text/plain; charset=ISO-8859-6-e
>>> :             Content-type: text/plain; charset=ISO-8859-6-i
>>> :             Content-type: text/plain; charset=ISO-8859-8-e
>>> :             Content-type: text/plain; charset=ISO-8859-8-i
>>> :
>>> :    The "i" suffix refers to implicit mode and the "e" suffix refers to
>>> :    explicit mode.
>>> Best regards
>>> /Olle
>>> --
>>> Olle Jarnefors, Royal Institute of Technology (KTH)
>>> <ojarnef@admin.kth.se>  --Boundary (ID uEbHHWxWEwCKT9wM3evJ5w)
>>>
>>>
>>
>>
>>
>>
>
>
>

Received on Monday, 18 June 2001 23:43:39 UTC