Håvard Hjulstad | 2 Jan 19:37
Picon
Favicon

ISO 639 name change: Romansh / romanche

The ISO 639 Registration Authorities' Joint Advisory Committee has made the following change:
 
Identifiers: rm / roh [no change]
 
English name: changed from Rhaeto-Romance to Romansh [old name deleted]
 
French name: changed from rhéto-roman to romanche [old name deleted]
 
Indigenous name: romontsch [no change]
 
This change has already been implemented on the ISO 639-2 web site, and information about the name change has been circulated in various fora. However, no formal announcement has previously been made.
 
Best regards,
Håvard Hjulstad
(secretary ISO 639 RA-JAC)
 
--------------------
Håvard Hjulstad
  Standard Norge / Standards Norway
  direkte tel / direct tel: (+47) 67838645
--------------------
 
_______________________________________________
Ietf-languages mailing list
Ietf-languages <at> alvestrand.no
http://www.alvestrand.no/mailman/listinfo/ietf-languages
Håvard Hjulstad | 2 Jan 19:47
Picon
Favicon

ISO 639 name change: Mapudungun

The ISO 639 Registration Authorities' Joint Advisory Committee has made the following change:
 
Identifiers: arn [no change]
 
English name: changed from Araucanian to Mapudungun; Mapuche [old name deleted]
 
French name: changed from araucan to mapudungun; mapuche; mapuce [old name deleted]
 
This change has already been implemented on the ISO 639-2 web site, and information about the name change has been circulated in various fora. However, no formal announcement has previously been made.
 
Best regards,
Håvard Hjulstad
(secretary ISO 639 RA-JAC)
 
--------------------
Håvard Hjulstad
  Standard Norge / Standards Norway
  direkte tel / direct tel: (+47) 67838645
--------------------
 
_______________________________________________
Ietf-languages mailing list
Ietf-languages <at> alvestrand.no
http://www.alvestrand.no/mailman/listinfo/ietf-languages
Håvard Hjulstad | 3 Jan 09:33
Picon
Favicon

ISO 639 name change: Asturian

The ISO 639 Registration Authorities' Joint Advisory Committee has made the following change:
 
Identifier: ast [no change]
 
English names: changed from Asturian; Bable to Asturian; Bable; Leonese; Asturleonese
 
French names: changed from asturien; bable to asturien; bable; léonais; asturoléonais
 
Indigenous names: changed from asturianu; bable to asturianu; bable; llionés
 
Best regards,
Håvard Hjulstad
(secretary ISO 639 RA-JAC)
 
--------------------
Håvard Hjulstad
  Standard Norge / Standards Norway
  direkte tel / direct tel: (+47) 67838645
--------------------
 
_______________________________________________
Ietf-languages mailing list
Ietf-languages <at> alvestrand.no
http://www.alvestrand.no/mailman/listinfo/ietf-languages
Doug Ewell | 3 Jan 17:57
Picon

Re: ISO 639 name change: Asturian

Håvard Hjulstad <HHj at standard dot no> wrote:

> The ISO 639 Registration Authorities' Joint Advisory Committee has 
> made the following change:
>
> Identifier: ast [no change]
>
> English names: changed from Asturian; Bable to Asturian; Bable; 
> Leonese; Asturleonese
>
> French names: changed from asturien; bable to asturien; bable; 
> léonais; asturoléonais
>
> Indigenous names: changed from asturianu; bable to asturianu; bable; 
> llionés

I'll send Michael (and cc this list) a registration form to add the two 
new alternative names.  I note in passing that there is no indigenous 
equivalent for the hybrid names "Asturleonese" and "asturoléonais".

I note with a bit more concern that while this announcement precedes any 
changes to the ISO 639-2 Web site, Håvard's other two announcements (for 
Romansh and Mapudungun) come well after those changes were added to the 
Web site, and in fact those changes have already been made in the 
Registry.  Sometimes the Web site is not changed for months after Håvard 
makes an announcement.  Because some people do treat these names as 
normative or official, it can be a problem when announcements are sent 
but the Web site is not changed until much later, or vice versa.

Is there some plan, with the impending publication of ISO 639-3 (which 
has a formal concept of "reference name"), to make the change process 
more predictable and ensure that the two components (e-mail announcement 
and Web site update) occur more or less simultaneously?

--
Doug Ewell  *  Fullerton, California, USA  *  RFC 4645  *  UTN #14
http://users.adelphia.net/~dewell/
http://www1.ietf.org/html.charters/ltru-charter.html
http://www.alvestrand.no/mailman/listinfo/ietf-languages
Doug Ewell | 3 Jan 18:09
Picon

NEW-MODIFY LANGUAGE SUBTAG MODIFICATION for "ast"

Type: language
Subtag: ast
Description: Asturian
Description: Bable
Description: Leonese
Description: Asturleonese
Added: 2005-10-16

--
Doug Ewell  *  Fullerton, California, USA  *  RFC 4645  *  UTN #14
http://users.adelphia.net/~dewell/
http://www1.ietf.org/html.charters/ltru-charter.html
http://www.alvestrand.no/mailman/listinfo/ietf-languages
Håvard Hjulstad | 3 Jan 19:54

SV: ISO 639 name change: Asturian


According to the current procedures, the announcement should precede the
implementation. Regretfully there are some changes that haven't been
announced in the proper way, and I will circulate a few more announcements
during the coming days to catch up. I will, however, add the note that the
announcement relates to an item that has already been updated.

As for the future, there will be significant procedural changes. All details
haven't been worked out yet, but these are some of the basics: ISO 639 will
(most likely in the course of 2007) move to a "Standard as database",
utilizing software that is being developed for ISO Central Secretariat. This
software will both support the maintenance process and (more or less)
automate the announcements, which will be generated by the database itself.
The database will be freely available on the web also in the future.

There will be a period between the publication of ISO 639-3 and the
implementation of "ISO 639 as database". The plan is to avoid release of new
items during this period.

Håvard

==================================
Håvard Hjulstad
  mailto:havard <at> hjulstad.com / mailto:hhj <at> standard.no
==================================

-----Opprinnelig melding-----
Fra: ietf-languages-bounces <at> alvestrand.no
[mailto:ietf-languages-bounces <at> alvestrand.no] På vegne av Doug Ewell
Sendt: 3. januar 2007 17:57
Til: ietf-languages <at> iana.org
Emne: Re: ISO 639 name change: Asturian

...

I note with a bit more concern that while this announcement precedes any
changes to the ISO 639-2 Web site, Håvard's other two announcements (for
Romansh and Mapudungun) come well after those changes were added to the Web
site, and in fact those changes have already been made in the Registry.
Sometimes the Web site is not changed for months after Håvard makes an
announcement.  Because some people do treat these names as normative or
official, it can be a problem when announcements are sent but the Web site
is not changed until much later, or vice versa.

Is there some plan, with the impending publication of ISO 639-3 (which has a
formal concept of "reference name"), to make the change process more
predictable and ensure that the two components (e-mail announcement and Web
site update) occur more or less simultaneously?

--
Doug Ewell  *  Fullerton, California, USA  *  RFC 4645  *  UTN #14
http://users.adelphia.net/~dewell/
http://www1.ietf.org/html.charters/ltru-charter.html
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
Picon

Re: Reshat Sabiq's requests for two Tatar orthographic variants


Addison Phillips yazmış:
>> What about ussr1928 or ussr1938? Is it the case that (some of) these
>> orthographies were introduces concurrently?
> 
> Why the 'ussr' at all? There is precedent for using years on their own
> for this purpose (see: -1901, -1996).
> 

The way are see it, the main choices can be categorized as follows:
1) separate tag for each language (note that there's no unicode
character for one letter in the original made up alphabets, but ŋ is the
closest apporximation available):
1.1) janalif (Jaŋalif, Qazan Tatar)
http://en.wikipedia.org/wiki/Janalif
1.2) canalip (Çaŋalip, Qazaq)
http://ru.wikipedia.org/wiki/%D0%9A%D0%B0%D0%B7%D0%B0%D1%85%D1%81%D0%BA%D0%B8%D0%B9_%D0%B0%D0%BB%D1%84%D0%B0%D0%B2%D0%B8%D1%82
Note, that Qazaq also has another variant: pinyin.
1.3) Some of these, do not appear to have a cute abbreviation like the
above, so a year or a combination of a year w/ something would probably
be needed, possibly merging 1.3 with 3 below. 1927 as the date of the
conference would be a starting point for most Turkic languages.
2) A common abbreviation for Turkic languages, as used in many sources,
such as NTA (New Turkic Alphabet), NA (New Alphabet), UTLA (Unified New
Turkic Alphabet), etc. I guess most folks didn't like my abbreviations
from the original request, and i can see the point of desirability of
avoiding latn as part of such a variant.
http://www.oxuscom.com/lang-policy.htm
http://www2.unil.ch/slav/ling/textes/GRANDE-34/Grande34.html
http://books.google.com/books?id=Z0-2R51tzi0C&pg=PA347&lpg=PP15&dq=Unified+%22Turkic+alphabet%22+conference+in+Baku+1926&psp=9&sig=IvjWdo9fSY3xmG-6Ru_wGEgxoNw
http://itre.cis.upenn.edu/~myl/languagelog/archives/001499.html
http://www.lmp.ucla.edu/Profile.aspx?LangID=62&menu=004
http://ru.wikipedia.org/wiki/%D0%9A%D1%80%D1%8B%D0%BC%D1%81%D0%BA%D0%BE-%D1%82%D0%B0%D1%82%D0%B0%D1%80%D1%81%D0%BA%D0%B8%D0%B9_%D1%8F%D0%B7%D1%8B%D0%BA
3) A common abbreviation for all languages regardless of origin. Looks
like ussr1928 is the most appealing suggestion in this category, but
maybe there will be some other ideas.
http://www2.unil.ch/slav/ling/textes/GRANDE-34/Grande34.html

One thing i would definitely like to see is a preference for a
wide-spread abbreviation, when it exists, instead of just a year, like
1927. So if the decision goes 1) route, i think Qazaq and Qazan Tatar
should get abbreviations, and not just a year. And as you can see,
canalip, and pinyin also automatically denote country where the reform
was originated, in short, they are more informative than just a year.

P.S. Sorry, some resources are not in English, and sorry if i have to
follow up later w/ more links, as i'm clearly rushing right now.

Thanks,
Reshat.

--
My public GPG key (ID 0x262839AF) is at: http://keyserver.veridis.com:11371
Michael Everson | 4 Jan 10:12
Favicon
Gravatar

Re: Reshat Sabiq's requests for two Tatar orthographic variants

Reshat:

I don't have ANY idea any more what it is you are asking for. How 
many Tatar alphabets are there? Why are you also talking about Qazaq? 
Is Jangalif for Tatar? Which Tatar? Why is Janalif mentioned on the 
Russian Wiki page about Kazakh? Why do you refer to Cangalip when 
that term doesn't appear on the Kazakh page (Jangalip does)? Why do 
you mention Qazan Tatar in association with Jangalif and not Qazaq or 
Crimean Tatar? Why do you keep giving Wikipedia articles as sources? 
The subject line here is "two Tatar orthographic variants". Does this 
mean "two Tatar orthographies"? Are there more? Do you plan to ask 
for a tag for each one? Why are you mentioning Pinyin? Are you also 
requesting a Pinyin tag for Kazakh?

Does the word Jangalif refer to one orthography and one orthography 
only? If so, why is it used for both Qazaq and Qazan Tatar?

What am I supposed to read on http://www.oxuscom.com/lang-policy.htm 
? Or http://www2.unil.ch/slav/ling/textes/GRANDE-34/Grande34.html ? 
Or the rest of those URLs?

This is still too complicated, and all your own posts on the subject 
are rambling and confusing.

I'm rejecting the current application because it is underspecified 
and confusing. Please figure out what you are trying to register, ONE 
THING AT A TIME. Propose a tag for a single orthography, with 
reference to books (dictionaries and grammars) using that 
orthography. Maybe then we can address your needs.

You said "P.S. Sorry, some resources are not in English, and sorry if i have to
follow up later w/ more links, as i'm clearly rushing right now."

Well, stop rushing. Slow down. Don't think by inundating us with URLs 
that you're making a precise case. Please, make the precise case.
--

-- 
Michael Everson * http://www.evertype.com
CE Whitehead | 4 Jan 18:06
Picon

Re: Reshat Sabiq's requests for two Tatar orthographic variants

Hi, all, Happy New Year (it's an important Holiday for me because it means a 
new start and I associate it with the Chinese New Year which emphasizes 
organizing one's house/putting things in order, and prosperity for all; also 
Kalenda Maya is a big holiday and has personal significance--it was Kalenda 
Maya in Japan when I was born though I was born somewhere on the other side 
of that date line)  Back to Reshat Sabiq's request:

>Addison Phillips yazmış:
> >> What about ussr1928 or ussr1938? Is it the case that (some of) these
> >> orthographies were introduces concurrently?
> >
> > Why the 'ussr' at all? There is precedent for using years on their own
> > for this purpose (see: -1901, -1996).
> >

I agree, I do not want to use the term ussr though it does have some 
historical significance and I can see why you are choosing it; but if the 
alphabet is in use today while the entity ussr is now sort of defunct and 
replaced  by the Russian Federation I do not think ussr is the right name.  
If the alphabet is in use today, you need a term that is meaningful today.

>The way are see it, the main choices can be categorized as follows:
>1) separate tag for each language (note that there's no unicode
>character for one letter in the original made up alphabets, but ŋ is the
>closest apporximation available):
>1.1) janalif (Jaŋalif, Qazan Tatar)
>http://en.wikipedia.org/wiki/Janalif
>1.2) canalip (Çaŋalip, Qazaq)
>http://ru.wikipedia.org/wiki/%D0%9A%D0%B0%D0%B7%D0%B0%D1%85%D1%81%D0%BA%D0%B8%D0%B9_%D0%B0%D0%BB%D1%84%D0%B0%D0%B2%D0%B8%D1%82
>Note, that Qazaq also has another variant: pinyin.

So how many variants do you want, 2 or 3?   Why that number, are these 
variants significantly different?  If so explain how they differ and why it 
makes sense to tag the alphabets/language variants differently?  Are these 
different languages you are talking about now or just different ways of 
writing the one language?  (I note in the one article I got to look at that 
you said that differences that did not exist or were minimal in the original 
languages really werecreated/augmented with the introduction of different 
ways of representing the vowels; so is that what these variants represent?)

1.3) Some of these, do not appear to have a cute abbreviation like the
>above, so a year or a combination of a year w/ something would probably
>be needed, possibly merging 1.3 with 3 below. 1927 as the date of the
>conference would be a starting point for most Turkic languages.

How many of 'these' are there?

I can see why you chose latn because these are in a latn and not Arabic or 
Cyrillic alphabet/script (or  are these in a Cyrillic script?)

Choose the one that is most meaningful.

Do let me know the number of total variants; you know I am not an expert on 
the Turkic or Tatar languages and on when the variation between two forms is 
significant enough to warrant a unique tag; you are going to have  to tell 
me what cases the variation is significant for and what tag you want!!!

Specify whether these are variants in the script or in the language too; and 
to what degree the script is the one script for that language variant or not 
when it is a language variant!!!

Also I would use dates only when they were relevant and easily available.

Like if it's the date of a well-known dictionary or event, maybe.  Otherwise 
no.

>2) A common abbreviation for Turkic languages, as used in many sources,
>such as NTA (New Turkic Alphabet), NA (New Alphabet), UTLA (Unified New
>Turkic Alphabet), etc. I guess most folks didn't like my abbreviations
>from the original request, and i can see the point of desirability of
>avoiding latn as part of such a variant.

I don't know which one; as I said I had less problems with latin than some; 
choose the best name for the alphabet(s) and let us know how many variants 
there are.

Best wishes, hope you get these through!

--C. E. Whitehead
cewcathar <at> hotmail.com

_________________________________________________________________
Fixing up the home? Live Search can help 
http://imagine-windowslive.com/search/kits/default.aspx?kit=improve&locale=en-US&source=hmemailtaglinenov06&FORM=WLMTAG
Håvard Hjulstad | 5 Jan 11:28
Picon
Favicon

ISO 639 name change: Central Khmer

The ISO 639 Registration Authorities' Joint Advisory Committee has made the following change:
 
Identifiers: km and khm [no change]
 
English names: changed from Khmer; Cambodian to Central Khmer
 
French names: changed from khmer; cambodgien to khmer central
 
This change has already been implemented on the ISO 639-2 and the ISO 639-3 web sites, and information about the name change has been circulated in various fora. However, no formal announcement has previously been made.
 
Best regards,
Håvard Hjulstad
(secretary ISO 639 RA-JAC)
 
--------------------
Håvard Hjulstad
  Standard Norge / Standards Norway
  direkte tel / direct tel: (+47) 67838645
--------------------
 
_______________________________________________
Ietf-languages mailing list
Ietf-languages <at> alvestrand.no
http://www.alvestrand.no/mailman/listinfo/ietf-languages

Gmane