Marion Gunn | 2 Oct 13:24
Picon

Re: [Ltru] Uniqueness of variant subtags

I'd see this particular block of similar tags as rather an advantage in 
the context, Addison, than any disadvantage (context being tags 
referring to Cornish), as I'd expect actual users to find no difficulty 
at all differentiating between them, especially as linguistic reform is 
currently a very live topic within a community which, although small, 
has had to learn to live with several reforms within a relatively short 
space of time.

I write this wearing my hat as Advisory Editor, English-Cornish 
Dictionary/Gerlyver Sawsnek-Kernowek, Nicholas Williams, Everson Gunn 
Teoranta/Agan Tavas 2000 (NB. First edition, which took two years to 
compile, during which the last but one reform was still in a state of flux).
mg

Phillips, Addison:
> ...
> It's not inconsistent and your position on those subtags is not incoherent. My concern with them was
merely that a tranche of extremely similar subtags might prove confusing and difficult for users to
approach, not that they were not "unique enough". 
>
> Addison
> _______________________________________________
> Ltru mailing list
> Ltru <at> ietf.org
> https://www.ietf.org/mailman/listinfo/ltru
>
>   

--

-- 

(Continue reading)

Lang Gérard | 3 Oct 09:39
Picon
Favicon

RE: Ltru Digest, Vol 44, Issue 15

Dear All,

0-Let me suggest that we should adopt a precise, uniform and recognized terminology when discussing about
transformations between languages and/or scripts.
So, I reproduce thereafter 8 definitions that have been given by the UNGEGN (United Nations Group of
Experts for Geographical Names) inside their Manual M 85, published by the UN Department of Economic and
Social Affairs, Statistical Division, in May 2002, entitled "Glossary of Terms for the Standardization
of Geographic Names".
All definitions are given in the 6 official UN's languages, and I only reproduce the english linguistic version.

1-TRANSFORMATION [, names]: [In toponymy,] general term covering the TRANSLATION, TRANSCRIPTION and
TRANSLITERATION [of toponyms]. The two latter terms constitute CONVERSION.

2-TRANSLATION: (a) The process of expressing meaning, presented in a source LANGUAGE, in the words of a
target LANGUAGE.
                           (b) A result of this process. [In toponymy it is sometimes applied only to the generic element of a name.]

3-CONVERSION: [In toponymy,] the process of transferring the phonological and/or morphological
elements of a particular LANGUAGE to another, or from one SCRIPT to another. Conversion is effected by
either TRANSCRIPTION or TRANSLITERATION.

4-TRANSCRIPTION: (a) A method of phonetic names CONVERSION between different LANGUAGES, in which the
sounds of a source LANGUAGE are recorded in terms of a specific target LANGUAGE and its particular SCRIPT,
normally withou recourse to additional diacritics.
                              (b) A result of this process.
 TRANSCRIPTION is not normally a reversible process. Retranscription (e.g. by computer) might result in a
form differing from the original.
 However, pinyin romanization of Chinese, although being a CONVERSION between SCRIPTS, but phonetic and
non-reversible, is also regarded as TRANSCRIPTION, not as TRANSLITERATION.

(Continue reading)

John Cowan | 3 Oct 16:18

Re: [Ltru] Ltru Digest, Vol 44, Issue 15

Lang Gérard scripsit:

> 0-Let me suggest that we should adopt a precise, uniform and recognized
> terminology when discussing about transformations between languages
> and/or scripts.

As far as I can tell, we are currently using the terms "transcription",
"transliteration", "romanization", "language" (except that we do not
require a language community to be large), and "script" in the same senses
as UNGEGN.  We have not used the broader terms "transformation" (meaning
translation, transcription, or transliteration) and "conversion" (meaning
transcription or transliteration), but they are reasonable additions to
the toolkit.  The term "translation" is not relevant to our work.

We also use a different taxonomy of scripts, dividing them into
alphabets, abjads, abugidas, syllabaries, and logosyllabaries: see
http://www.unicode.org/glossary for terse definitions, or Section 6.1
of the Unicode Standard for detailed explanations (available online at
http://www.unicode.org/versions/Unicode5.0.0/ch06.pdf .

--

-- 
John Cowan    http://ccil.org/~cowan  cowan <at> ccil.org
'Tis the Linux rebellion / Let coders take their place,
The Linux-nationale / Shall Microsoft outpace,
We can write better programs / Our CPUs won't stall,
So raise the penguin banner of / The Linux-nationale.  --Greg Baker
Lang Gérard | 3 Oct 16:41
Picon
Favicon

RE: [Ltru] Ltru Digest, Vol 44, Issue 15

I do not think that all variants of "Sign languages" taken care of inside ISO 639 and IANA's Registry could
enter under the"means of verbal communication" that are described as a condition for a language by UNGEGN.
This question of definition of "languages" is clearly linked with the fact that the english word
"language" has two possible interpretations in french:
-(i) "langue", that is linked whith "tongue" (that has the same translation "langue" in french),
evidently connected with "verbal communication" and oriented on the semantics (this interpretation
clearly excludes all forms of signed or only symbolic languages);
-(ii) "language", that is more extensive and more oriented on syntax, and allows to take care of sign
languages as well as many sorts of artificial and symbolic languages, like informatics, or "chess game
description", ......

The french title of ISO 639 is "Codes pour la representation des noms de LANGUES" that , in principle, does
not include Sign languages (that are not "verbal communication means").

Gérard LANG

-----Message d'origine-----
De : John Cowan [mailto:cowan <at> ccil.org] 
Envoyé : vendredi 3 octobre 2008 16:18
À : Lang Gérard
Cc : ltru <at> ietf.org; ietf-languages <at> iana.org
Objet : Re: [Ltru] Ltru Digest, Vol 44, Issue 15

Lang Gérard scripsit:

> 0-Let me suggest that we should adopt a precise, uniform and 
> recognized terminology when discussing about transformations between 
> languages and/or scripts.

As far as I can tell, we are currently using the terms "transcription", "transliteration",
(Continue reading)

Gerard Meijssen | 3 Oct 17:11
Picon

Re: [Ltru] Ltru Digest, Vol 44, Issue 15

Hoi,
In that case the definition in French has to change. ISO-639-3 does include sign languages and that is a good thing too.
Thanks,
     Gerard

On Fri, Oct 3, 2008 at 4:41 PM, Lang Gérard <gerard.lang <at> insee.fr> wrote:
I do not think that all variants of "Sign languages" taken care of inside ISO 639 and IANA's Registry could enter under the"means of verbal communication" that are described as a condition for a language by UNGEGN.
This question of definition of "languages" is clearly linked with the fact that the english word "language" has two possible interpretations in french:
-(i) "langue", that is linked whith "tongue" (that has the same translation "langue" in french), evidently connected with "verbal communication" and oriented on the semantics (this interpretation clearly excludes all forms of signed or only symbolic languages);
-(ii) "language", that is more extensive and more oriented on syntax, and allows to take care of sign languages as well as many sorts of artificial and symbolic languages, like informatics, or "chess game description", ......

The french title of ISO 639 is "Codes pour la representation des noms de LANGUES" that , in principle, does not include Sign languages (that are not "verbal communication means").

Gérard LANG

-----Message d'origine-----
De : John Cowan [mailto:cowan <at> ccil.org]
Envoyé : vendredi 3 octobre 2008 16:18
À : Lang Gérard
Cc : ltru <at> ietf.org; ietf-languages <at> iana.org
Objet : Re: [Ltru] Ltru Digest, Vol 44, Issue 15

Lang Gérard scripsit:

> 0-Let me suggest that we should adopt a precise, uniform and
> recognized terminology when discussing about transformations between
> languages and/or scripts.

As far as I can tell, we are currently using the terms "transcription", "transliteration", "romanization", "language" (except that we do not require a language community to be large), and "script" in the same senses as UNGEGN.  We have not used the broader terms "transformation" (meaning translation, transcription, or transliteration) and "conversion" (meaning transcription or transliteration), but they are reasonable additions to the toolkit.  The term "translation" is not relevant to our work.

We also use a different taxonomy of scripts, dividing them into alphabets, abjads, abugidas, syllabaries, and logosyllabaries: see http://www.unicode.org/glossary for terse definitions, or Section 6.1 of the Unicode Standard for detailed explanations (available online at http://www.unicode.org/versions/Unicode5.0.0/ch06.pdf .

--
John Cowan    http://ccil.org/~cowan  cowan <at> ccil.org
'Tis the Linux rebellion / Let coders take their place, The Linux-nationale / Shall Microsoft outpace, We can write better programs / Our CPUs won't stall, So raise the penguin banner of / The Linux-nationale.  --Greg Baker
_______________________________________________
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
John Cowan | 3 Oct 17:21

Re: [Ltru] Ltru Digest, Vol 44, Issue 15

CE Whitehead scripsit:

> However, "le tresor de la langue francaise" online
> (http://atilf.atilf.fr/tlf.htm) seems to largely agree with your
> definition of "langue" -- as something pertaining to the "tongue" or to
> things that remind one of a "tongue" (such as a "the tongue of a flame")

Etymology is not a key to meaning.  "Verbal communication" is
communication in words, and although sign languages don't involve the
tongue, they definitely have words.

--

-- 
John Cowan    cowan <at> ccil.org    http://ccil.org/~cowan
Nobody expects the RESTifarian Inquisition!  Our chief weapon is
surprise ... surprise and tedium  ... tedium and surprise ....
Our two weapons are tedium and surprise ... and ruthless disregard
for unpleasant facts....  Our three weapons are tedium, surprise, and
ruthless disregard ... and an almost fanatical devotion to Roy Fielding....
CE Whitehead | 3 Oct 17:15
Picon

[Ltru] Ltru Digest, Vol 44, Issue 15


Hi, Are you saying that "langage" is a better French translation of "languages" in "Codes for the
representation of names of languages" than is "langue"?  Or what?

(I do think it's possible to translate "sign language" as
"langue des signes"
Is this correct?)

However, "le tresor de la langue francaise" online (http://atilf.atilf.fr/tlf.htm) seems to largely
agree with your definition of "langue" -- as something pertaining to the "tongue" or to things that remind
one of a "tongue" (such as a "the tongue of a flame")

Best,

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

Lang Gérard gerard.lang at insee.fr 
Fri Oct 3 16:41:11 CEST 2008

> I do not think that all variants of "Sign languages" taken care of inside ISO 639 and IANA's Registry could
enter under the"means of verbal communication" that are described as a condition for a language by UNGEGN.
> This question of definition of "languages" is clearly linked with the fact that the english word
"language" has two possible interpretations in french:
> -(i) "langue", that is linked whith "tongue" (that has the same translation "langue" in french),
evidently connected with "verbal communication" and oriented on the semantics (this interpretation
clearly excludes all forms of signed or only symbolic languages);
> -(ii) "language", that is more extensive and more oriented on syntax, and allows to take care of sign
languages as well as many sorts of artificial and symbolic languages, like informatics, or "chess game
description", ......

> The french title of ISO 639 is "Codes pour la representation des noms de LANGUES" that , in principle, does
not include Sign languages (that are not "verbal communication means").

> Gérard LANG
Lang Gérard | 6 Oct 10:27
Picon
Favicon

UNGEGN definitions and UNICODe Glossary of terms

Dear John Cowan,

1-I made a terrible mistake. The second possible interpretation of the english word "language" in french
reads "langage", not "language". So much for me, maybe too much Neglish is not good for my french !
2-I am happy to understand that you plainly approve at least 7 of the 8 definitions I selected from UNGEGN's
Manual M 85.
3-Anyway, I found no definition for the term "LANGUAGE" inside the GLOSSARY OF UNICODE TERMS source you
mentionned. Nor did I find any definition concerning the terms "CONVERSION", "ROMANIZATION",
"TRANSLATION", TRANSCRIPTION" or "TRANSLITERATION".
I found a definition for the term "SCRIPT" that seems in line, and perfectly compatible with the definition
given by UNGEGN.
I also found in the glossary a definition for "TRANSFORMATION FORMAT" (and also one for "TRANSCODING"), so
it is difficult for me to think that "TRANSFORMATION" is not a concept used by UNICODE.
4-I am certainly not enough expert in english language to decide if "Sign language" can be considered to be
covered by "verbal communication", that nevertheless seems to me have a flavour of "oral
communication". Anyway, I do not see any possibility that "pronunciation of words" could cover "Sign languages".
5-Coming back to the proper interpretation in french of the english word "language", I verified that from
the beginning (Recommendation ISO 639 [November 1967] "Symbols for Languages, Countries and
Authorities// Indicatifs de LANGUES, de pays et d'autorités", and with strictly no exception, ISO 639
systematically translated the english word "Language" by the french word "langue" and not by "langage".
This is also the case for UNGEGN's Manual M58, that never uses the french word "langage".
So, I have absolutely no doubt that "langue" is the proper french interpretation for "Language" inside ISO
639, as the general title of this standard  and as UNGEGN interpretation both prove.
And I maintain that, under this clear interpretation, "Sign languages" should not be taken inside ISO 639.
This is also reinforced by the fact that no "Sign Language" was present inside the publications of ISO 639
(1988) or ISO 639-2 (1998), or even ISO 639-1 (2002).But, a collective "Sign Languages", with alpha-3
code element "sgn" was added by ISO 639/RA-JAC inside ISO 639-2 on 2000-02-18 only, with no corresponding
alpha-2 code element. 
This addition does not seem in line with the scope of ISO 639-2, whose  "1 Scope" writes :
 " This part of ISO 639 provides two sets of three-letter alphabetic codes for the representation of names of
languages, one for TERMINOLOGY applications, and the other    for BIBLIOGRAPHIC applications...."
Moreover, ISO 639-5 (2008), that also uses "familles de langues" and "groupes de langues", recognizes
"sgn" as a group of languages, so that ideally "sgn" should be  suppressed inside ISO 639-2 to be only
mentionned inside ISO 639-5. And in this case, there would be strictly no mention of any form of "Sign
languages" inside ISO 639-1 or ISO 639-2.

Bien cordialement.
Gérard LANG

"Là où il n'y a pas de loi,
Il y a quand même la conscience"
  Publilius Syrus
 (1er siècle avant J.-C.)

-----Message d'origine-----
De : ietf-languages-bounces <at> alvestrand.no [mailto:ietf-languages-bounces <at> alvestrand.no] De la
part de John Cowan
Envoyé : vendredi 3 octobre 2008 17:21
À : CE Whitehead
Cc : ietf-languages <at> iana.org; ltru <at> ietf.org
Objet : Re: [Ltru] Ltru Digest, Vol 44, Issue 15

CE Whitehead scripsit:

> However, "le tresor de la langue francaise" online
> (http://atilf.atilf.fr/tlf.htm) seems to largely agree with your 
> definition of "langue" -- as something pertaining to the "tongue" or 
> to things that remind one of a "tongue" (such as a "the tongue of a 
> flame")

Etymology is not a key to meaning.  "Verbal communication" is communication in words, and although sign
languages don't involve the tongue, they definitely have words.

--

-- 
John Cowan    cowan <at> ccil.org    http://ccil.org/~cowan
Nobody expects the RESTifarian Inquisition!  Our chief weapon is surprise ... surprise and tedium  ...
tedium and surprise ....
Our two weapons are tedium and surprise ... and ruthless disregard for unpleasant facts....  Our three
weapons are tedium, surprise, and ruthless disregard ... and an almost fanatical devotion to Roy Fielding....
_______________________________________________
Ietf-languages mailing list
Ietf-languages <at> alvestrand.no
http://www.alvestrand.no/mailman/listinfo/ietf-languages
Martin Duerst | 6 Oct 12:09
Picon
Gravatar

[OT] Re: [Ltru] UNGEGN definitions and UNICODe Glossary of terms

Dear Gerard,

[co-chair hat on]
Unless you have a concrete suggestion re. one of the two
LTRU documents being worked on, please refrain from cc'ing
ltru <at> ietf.org (or at least mark your postings with [OT]
(off topic)). Thanks!

[I'm not responsible for ietf-languages <at> iana.org.]

See below for a different interpretation re. sign languages.

Regards,    Martin.

At 17:27 08/10/06, Lang G$BqS(Bard wrote:
>Dear John Cowan,

>5-Coming back to the proper interpretation in french of the english word 
>"language", I verified that from the beginning (Recommendation ISO 639 
>[November 1967] "Symbols for Languages, Countries and Authorities// 
>Indicatifs de LANGUES, de pays et d'autorit$BqT(B", and with strictly no 
>exception, ISO 639 systematically translated the english word "Language" by 
>the french word "langue" and not by "langage". This is also the case for 
>UNGEGN's Manual M58, that never uses the french word "langage".
>So, I have absolutely no doubt that "langue" is the proper french 
>interpretation for "Language" inside ISO 639, as the general title of this 
>standard  and as UNGEGN interpretation both prove.
>And I maintain that, under this clear interpretation, "Sign languages" 
>should not be taken inside ISO 639.

[technical hat on]

I think it's very easy to come up with a different interpretation.
[For the sake of exposition, I'm assuming that the documents were
translated from English to French, but much of the stuff below also
works in other scenarios.]

When translating from English to French, 'langue' seemed the most
obvious and precise term, and the translator simply either forgot
about the existence of sign languages or checked the then-current
actual list and didn't find any.

The ideal thing to happen when a standard gets translated is that
the translation detects some ambiguity. This could have happened
in this case, the French translator asking back "Is this supposed
to include sign languages or not; I have to know that in order to
be able to translate correctly." As a result, there should have
been some explicit text saying either that sign languages are
included or excluded, which I guess doesn't exist.

I think it's inappropriate, in this case, to conclude from the
French translation 'langue' that this excludes sign languages.
The chance that this translation was in essence the result of
an oversight (not to blame the translator; it's essentially an
oversight by everybody involved) is in my opinion at least as big,
and leads to the (in my opinion) much more desirable result of
including sign languages.

>This is also reinforced by the fact that no "Sign Language" was present 
>inside the publications of ISO 639 (1988) or ISO 639-2 (1998), or even ISO 
>639-1 (2002).

That may explain the choice of word by the translator, but doesn't
prove any intent of coverage.

>But, a collective "Sign Languages", with alpha-3 code element 
>"sgn" was added by ISO 639/RA-JAC inside ISO 639-2 on 2000-02-18 only, with 
>no corresponding alpha-2 code element. 
>This addition does not seem in line with the scope of ISO 639-2, whose  "1 
>Scope" writes :
> " This part of ISO 639 provides two sets of three-letter alphabetic codes 
>for the representation of names of languages, one for TERMINOLOGY 
>applications, and the other    for BIBLIOGRAPHIC applications...."
>Moreover, ISO 639-5 (2008), that also uses "familles de langues" and 
>"groupes de langues", recognizes "sgn" as a group of languages, so that 
>ideally "sgn" should be  suppressed inside ISO 639-2 to be only mentionned 
>inside ISO 639-5.

I guess ideally, yes, but apparently the need to code sign languages
was so strong (at a time when 639-5 didn't exist yet) that the relevant
committees ignored this "detail". This may be taken as strong evidence
that once the parties involved got aware of sign languages, they
really thought they should be covered.

>And in this case, there would be strictly no mention of 
>any form of "Sign languages" inside ISO 639-1 or ISO 639-2.

That would make the French translation more 'correct' on paper,
but it's still not clear whether it would match the (original) intent.

Regards,    Martin.

>
>
>Bien cordialement.
>G$BqS(Bard LANG
>
>"L$B_(Bo$B‘(Bil n'y a pas de loi,
>Il y a quand m$BsN(Be la conscience"
>  Publilius Syrus
> (1er si$BoD(Ble avant J.-C.)
>
>-----Message d'origine-----
>De : ietf-languages-bounces <at> alvestrand.no 
>[mailto:ietf-languages-bounces <at> alvestrand.no] De la part de John Cowan
>Envoy$Bq(B: vendredi 3 octobre 2008 17:21
>$B%?(B : CE Whitehead
>Cc : ietf-languages <at> iana.org; ltru <at> ietf.org
>Objet : Re: [Ltru] Ltru Digest, Vol 44, Issue 15
>
>CE Whitehead scripsit:
>
>> However, "le tresor de la langue francaise" online
>> (http://atilf.atilf.fr/tlf.htm) seems to largely agree with your 
>> definition of "langue" -- as something pertaining to the "tongue" or 
>> to things that remind one of a "tongue" (such as a "the tongue of a 
>> flame")
>
>Etymology is not a key to meaning.  "Verbal communication" is communication 
>in words, and although sign languages don't involve the tongue, they 
>definitely have words.
>
>-- 
>John Cowan    cowan <at> ccil.org    http://ccil.org/~cowan
>Nobody expects the RESTifarian Inquisition!  Our chief weapon is 
>surprise ... surprise and tedium  ... tedium and surprise ....
>Our two weapons are tedium and surprise ... and ruthless disregard for 
>unpleasant facts....  Our three weapons are tedium, surprise, and ruthless 
>disregard ... and an almost fanatical devotion to Roy Fielding....
>_______________________________________________
>Ietf-languages mailing list
>Ietf-languages <at> alvestrand.no
>http://www.alvestrand.no/mailman/listinfo/ietf-languages
>_______________________________________________
>Ltru mailing list
>Ltru <at> ietf.org
>https://www.ietf.org/mailman/listinfo/ltru

#-#-#  Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University
#-#-#  http://www.sw.it.aoyama.ac.jp       mailto:duerst <at> it.aoyama.ac.jp     

_______________________________________________
Ietf-languages mailing list
Ietf-languages <at> alvestrand.no
http://www.alvestrand.no/mailman/listinfo/ietf-languages
Doug Ewell | 6 Oct 15:00
Favicon

Re: UNGEGN definitions and UNICODe Glossary of terms

I thought it had already been established that:

1.  our terminology is largely consistent with UNGEGN (except that we 
don't classify certain types of scripts as "defective"), so we have no 
changes to make there, and

2.  neither LTRU nor ietf-languages is responsible for either the 
French-language title of ISO 639 nor the decision to include sign 
languages in the scope of that standard (though we agree with that 
decision), so we have no changes to make there either.

--
Doug Ewell  *  Thornton, Colorado, USA  *  RFC 4645  *  UTN #14
http://www.ewellic.org
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

Gmane