headers
Doug Ewell | 8 Feb 2012 19:08
Favicon

ISO 639-3 changes

ISO 639-3/RA has released its 2011 series of changes. With this series,
the RA approved 142 changes encompassing roughly 200 code elements. 
Clearly the rate of change has not diminished in the years following the
initial release of 639-3.

In the coming days or weeks, I'll be sending proposed records and
registration forms to keep the Registry in step with this. As in years
past, I'll try to send them out in batches, organized by the type of
639-3 change (retirement, new language, update).

--
Doug Ewell | Thornton, Colorado, USA
http://www.ewellic.org |  <at> DougEwell ­

_______________________________________________
Ietf-languages mailing list
Ietf-languages <at> alvestrand.no
http://www.alvestrand.no/mailman/listinfo/ietf-languages
Permalink | Reply | 3 comments |
headers
John Cowan | 9 Feb 2012 01:00

Re: ISO 639-3 changes

Doug Ewell scripsit:

> 639-3 change (retirement, new language, update).

I'd say the right order is "new language", "update", "retirement".

--

-- 
Business before pleasure, if not too bloomering long before.
        --Nicholas van Rijn
                John Cowan <cowan <at> ccil.org>
                    http://www.ccil.org/~cowan
Permalink | Reply | 1 comment |
headers
Doug Ewell | 9 Feb 2012 02:41
Favicon

Re: ISO 639-3 changes

John Cowan wrote:

> Doug Ewell scripsit:
>
>> 639-3 change (retirement, new language, update).
>
> I'd say the right order is "new language", "update", "retirement".

I hadn't thought they would necessarily be sent in batches to IANA, only 
to this list.  If I remember correctly, in the past I posted 639-3-based 
records and forms to the list in batches, but I sent them to Michael for 
submission to IANA all at once.  I'm not sure whether it's best to have 
IANA do several Registry updates in a case like this, or just one.

Anyway, if they do all go to IANA at the same time, the "right order" to 
post them on the list becomes kind of moot.  The simple cases should 
probably go first, as opposed to changes that cascade over into several 
subtags.

I need to wait a few days anyway for ISO 639-3/RA to fix a couple of 
errors in the data files.

--
Doug Ewell | Thornton, Colorado, USA
http://www.ewellic.org |  <at> DougEwell ­
Permalink | Reply | 0 comments |
headers
Doug Ewell | 13 Feb 2012 23:51
Favicon

Re: ISO 639-3 changes

On Thu Feb 9 02:41:46 CET 2012, I wrote:

> I need to wait a few days anyway for ISO 639-3/RA to fix a couple of
> errors in the data files.

After working through most of the Summary of Outcomes document and the
data files (*.tab), and discovering a significant number of errors and
inconsistencies, I propose that we wait until a revised set of data
files is available from ISO 639-3/RA before making changes to the
Language Subtag Registry.  This may take a few additional weeks,
according to the RA.

The risk in going forward now is that changes will be made to the
Registry that are not reflected in 639-3, and some incorrect changes may
be made that are not reversible.  For instance, we cannot delete a
language subtag that was created in error; we can only deprecate it.

Picking out the non-problematic code elements and applying them to the
Registry, while leaving the problematic ones until the fixes are in
place, would be tricky from a clerical standpoint.  I'd prefer to wait
for a clean and correct data set.

I will finish going through the current batch of data to try to unearth
any additional problems, so they can be corrected in the next release.

Apologies to anyone who has been waiting to use one of the new or
changed subtags.

--
Doug Ewell | Thornton, Colorado, USA
(Continue reading)

Permalink | Reply | 0 comments |
headers
Akira TAGOH | 17 Feb 2012 07:00

language-subtag-registry is broken

Hi,

I'm assuming that language-subtag-registry is encoded by utf-8 though,
it's now broken because of the nulik subtag that has been added
recently.

I hope it will be corrected shortly.

Thanks,
--

-- 
Akira TAGOH
Permalink | Reply | 1 comment |
headers
Doug Ewell | 17 Feb 2012 16:08
Favicon

Re: language-subtag-registry is broken

Akira TAGOH <akira at tagoh dot org> wrote:

> I'm assuming that language-subtag-registry is encoded by utf-8 though,
> it's now broken because of the nulik subtag that has been added
> recently.
>
> I hope it will be corrected shortly.

Both 'nulik' and 'rigik' were apparently encoded in MacRoman instead of
UTF-8. IANA has been notified.  Thanks for spotting this.

--
Doug Ewell | Thornton, Colorado, USA
http://www.ewellic.org |  <at> DougEwell ­

_______________________________________________
Ietf-languages mailing list
Ietf-languages <at> alvestrand.no
http://www.alvestrand.no/mailman/listinfo/ietf-languages
Permalink | Reply | 0 comments |
headers
Martin J. Dürst | 23 Feb 2012 07:10
Picon
Gravatar

Fwd: RFC 6497 on BCP 47 Extension T - Transformed Content

Congratulations!     Martin.

-------- Original Message --------
Subject: RFC 6497 on BCP 47 Extension T - Transformed Content
Date: Wed, 22 Feb 2012 16:56:32 -0800 (PST)
From: rfc-editor <at> rfc-editor.org
To: ietf-announce <at> ietf.org, rfc-dist <at> rfc-editor.org
CC: rfc-editor <at> rfc-editor.org

A new Request for Comments is now available in online RFC libraries.

         RFC 6497

         Title:      BCP 47 Extension T -
                     Transformed Content
         Author:     M. Davis, A. Phillips,
                     Y. Umaoka, C. Falk
         Status:     Informational
         Stream:     IETF
         Date:       February 2012
         Mailbox:    mark <at> macchiato.com,
                     addison <at> lab126.com,
                     yoshito_umaoka <at> us.ibm.com,
                     court <at> infiauto.com
         Pages:      15
         Characters: 32915
         Updates/Obsoletes/SeeAlso:   None

         I-D Tag:    draft-davis-t-langtag-ext-07.txt
(Continue reading)

Permalink | Reply | 1 comment |
headers
Mark Davis ☕ | 23 Feb 2012 20:37

Re: RFC 6497 on BCP 47 Extension T - Transformed Content

Thanks!

— Il meglio è l’inimico del bene —



On Wed, Feb 22, 2012 at 22:10, "Martin J. Dürst" <duerst <at> it.aoyama.ac.jp> wrote:
Congratulations!     Martin.

-------- Original Message --------
Subject: RFC 6497 on BCP 47 Extension T - Transformed Content
Date: Wed, 22 Feb 2012 16:56:32 -0800 (PST)
From: rfc-editor <at> rfc-editor.org
To: ietf-announce <at> ietf.org, rfc-dist <at> rfc-editor.org
CC: rfc-editor <at> rfc-editor.org


A new Request for Comments is now available in online RFC libraries.


       RFC 6497

       Title:      BCP 47 Extension T -
                   Transformed Content
       Author:     M. Davis, A. Phillips,
                   Y. Umaoka, C. Falk
       Status:     Informational
       Stream:     IETF
       Date:       February 2012
       Mailbox:    mark <at> macchiato.com,
                   addison <at> lab126.com,
                   yoshito_umaoka <at> us.ibm.com,
                   court <at> infiauto.com
       Pages:      15
       Characters: 32915
       Updates/Obsoletes/SeeAlso:   None

       I-D Tag:    draft-davis-t-langtag-ext-07.txt

       URL:        http://www.rfc-editor.org/rfc/rfc6497.txt

This document specifies an Extension to BCP 47 that provides subtags
for specifying the source language or script of transformed content,
including content that has been transliterated, transcribed, or
translated, or in some other way influenced by the source.  It also
provides for additional information used for identification.  This
document is not an Internet Standards Track specification; it is
published for informational purposes.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
 http://www.ietf.org/mailman/listinfo/ietf-announce
 http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor <at> rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
IETF-Announce mailing list
IETF-Announce <at> ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

_______________________________________________
Ietf-languages mailing list
Ietf-languages <at> alvestrand.no
http://www.alvestrand.no/mailman/listinfo/ietf-languages

_______________________________________________
Ietf-languages mailing list
Ietf-languages <at> alvestrand.no
http://www.alvestrand.no/mailman/listinfo/ietf-languages
Permalink | Reply | 0 comments |
headers
Doug Ewell | 28 Feb 2012 06:40
Favicon

Update: language-subtag-registry still broken

On Fri Feb 17 16:08:52 CET 2012, I wrote:

> Akira TAGOH <akira at tagoh dot org> wrote:
>
>> I'm assuming that language-subtag-registry is encoded by utf-8
>> though, it's now broken because of the nulik subtag that has been
>> added recently.
>>
>> I hope it will be corrected shortly.
>
> Both 'nulik' and 'rigik' were apparently encoded in MacRoman instead
> of UTF-8. IANA has been notified.  Thanks for spotting this.

IANA "corrected" this by transcoding the entire Registry—not just the
new entries—from MacRoman to UTF-8, so that previously valid fields
like:

Description: Norwegian Bokmål

where the 'm' is followed by U+00E5 (C3, A5 in UTF-8), have been turned
into:

Description: Norwegian Bokmål

where the UTF-8 sequence (C3, A5) was interpreted as MacRoman (U+221A,
U+2022) and converted to (E2, 88, 9A, E2, 80, A2).

*Every* non-ASCII sequence in the Registry has been corrupted in this
way, except the Description fields for the 'nulik' and 'rigik' records,
which were originally encoded in MacRoman and are now fine.

The Registry has been like this for over a week now, and we have been
unable to contact IANA to get it corrected. Until this problem is
resolved, I've posted a corrected version at
http://ewellic.org/language-subtag-registry.txt . Please be aware that
this is not the official Registry, and I'll be taking it down as soon as
IANA makes the necessary corrections.

--
Doug Ewell | Thornton, Colorado, USA
http://www.ewellic.org |  <at> DougEwell ­ 

_______________________________________________
Ietf-languages mailing list
Ietf-languages <at> alvestrand.no
http://www.alvestrand.no/mailman/listinfo/ietf-languages
Permalink | Reply | 2 comments |
headers
John Cowan | 28 Feb 2012 06:49

Re: Update: language-subtag-registry still broken

Doug Ewell scripsit:

> IANA "corrected" this by transcoding the entire Registry—not just the
> new entries—from MacRoman to UTF-8, 

I sat next to the Duchess for tea.
It was just as I feared it would be:
     Her rumblings abdominal
     Were simply phenomenal
And everyone thought it was me.

This is why I preferred the ASCII-plus-Unicode-escapes design of the
previous registry: it couldn't be corrupted this way.

--

-- 
May the hair on your toes never fall out!       John Cowan
        --Thorin Oakenshield (to Bilbo)         cowan <at> ccil.org
_______________________________________________
Ietf-languages mailing list
Ietf-languages <at> alvestrand.no
http://www.alvestrand.no/mailman/listinfo/ietf-languages
Permalink | Reply | 1 comment |

Gmane