Doug Ewell | 13 Dec 23:19
Favicon

Revised paperwork for 'Hluw'

LANGUAGE SUBTAG MODIFICATION
File-Date: 2011-12-28
%%
Type: script
Subtag: Hluw
Description: Anatolian Hieroglyphs
Description: Luwian Hieroglyphs
Description: Hittite Hieroglyphs
Added: 2011-12-28
%%

---

LANGUAGE SUBTAG REGISTRATION FORM

1. Name of requester: Doug Ewell
2. E-mail address of requester: doug at ewellic.org
3. Record Requested:

   Type: script
   Subtag: Hluw
   Description: Anatolian Hieroglyphs
   Description: Luwian Hieroglyphs
   Description: Hittite Hieroglyphs

4. Intended meaning of the subtag:

5. Reference to published description
   of the language (book or article):

(Continue reading)

Doug Ewell | 12 Dec 02:33
Favicon

Re: Paperwork for 'Hluw'

Michael Everson wrote:

>> Luwian Hittite Hieroglyphs
>
> That's a mistake, it's supposed to be Luwian Hieroglyphs

It's written that way in the normative plain-text file on the Unicode 
site, as well as all five HTML pages.  The French version seems to align 
with what Michael says the English version should be.  I'll wait for 
corrected ISO 15924 data.

--
Doug Ewell | Thornton, Colorado, USA | RFC 5645, 4645, UTN #14
www.ewellic.org | www.facebook.com/doug.ewell | @DougEwell ­ 
Doug Ewell | 11 Dec 04:49
Favicon

Paperwork for 'Hluw'

ISO 15924 has added a new code element for a previously uncoded script.  Below are the record and registration form to add a corresponding subtag to the LSR.  The review period would end Christmas Day, though I’m not picturing IANA adding the subtag that day.
 
---
 
LANGUAGE SUBTAG MODIFICATION
File-Date: 2011-12-25
%%
Type: script
Subtag: Hluw
Description: Anatolian Hieroglyphs
Description: Luwian Hittite Hieroglyphs
Description: Hittite Hieroglyphs
Added: 2011-12-25
%%
 
---
 
LANGUAGE SUBTAG REGISTRATION FORM
 
1. Name of requester: Doug Ewell
2. E-mail address of requester: doug at ewellic.org
3. Record Requested:
 
   Type: script
   Subtag: Hluw
   Description: Anatolian Hieroglyphs
   Description: Luwian Hittite Hieroglyphs
   Description: Hittite Hieroglyphs
 
4. Intended meaning of the subtag:
 
5. Reference to published description
   of the language (book or article):
 
6. Any other relevant information:
 
   This registration tracks a change made to ISO 639-3 effective
   2011-12-09, adding the code element 'Hluw' for "Anatolian Hieroglyphs
   (Luwian Hittite Hieroglyphs, Hittite Hieroglyphs)".
 
--
Doug Ewell | Thornton, Colorado, USA | RFC 5645, 4645, UTN #14
www.ewellic.org | www.facebook.com/doug.ewell | <at> DougEwell ­
_______________________________________________
Ietf-languages mailing list
Ietf-languages <at> alvestrand.no
http://www.alvestrand.no/mailman/listinfo/ietf-languages
Doug Ewell | 11 Nov 17:33
Favicon

Registration form and record for LY

As predicted, ISO 3166/MA has changed the English short name for code
element LY from "Libyan Arab Jamahiriya" to "Libya".  (Similar changes
were made to the English long name and French names, which do not affect
the Language Subtag Registry.)  Below are the proposed record and
registration form to make this change in the Registry.

This particular change was discussed on this list six weeks ago, with no
objections to speak of, so the two-week review period ending November 25
might be expected to go smoothly.

---

LANGUAGE SUBTAG MODIFICATION
File-Date: 2011-11-25
%%
Type: region
Subtag: LY
Description: Libya
Added: 2005-10-16
%%

---

LANGUAGE SUBTAG REGISTRATION FORM

1. Name of requester: Doug Ewell
2. E-mail address of requester: doug at ewellic.org
3. Record Requested:

   Type: region
   Subtag: LY
   Description: Libya

4. Intended meaning of the subtag:

5. Reference to published description
   of the language (book or article):

6. Any other relevant information:

   This registration tracks a change made to ISO 3166-1 effective
   2011-11-08, changing the English short name from "Libyan Arab
   Jamahiriya" to "Libya".

   For more information, refer to ISO 3166-1 Newsletter VI-11,
   "Name change for Libya", at
   http://www.iso.org/iso/nl_vi-11_name_change_for_libya.pdf .

--
Doug Ewell | Thornton, Colorado, USA | RFC 5645, 4645, UTN #14
www.ewellic.org | www.facebook.com/doug.ewell | @DougEwell
Kristen Eisenberg | 9 Oct 22:59
Picon
Favicon

Fwd: draft-davis-t-langtag-ext

Most of the people on the ietf-languages list are probably on the
ltru at ietf.org list as well, but I wanted to confirm that everyone got a
chance to review this before it proceeded to the IESG. Please have a
look at the ltru archive
<http://www.ietf.org/mail-archive/web/ltru/current/maillist.html> and
send any comments to the ltru at ietf.org list since that's where
discussion seems to be taking place.

Thanks.

Kristen Eisenberg
Billige Flüge
Marketing GmbH
Emanuelstr. 3,
10317 Berlin
Deutschland
Telefon: +49 (33)
5310967
Email:
utebachmeier at
gmail.com
Site:
http://flug.airego.de - Billige Flüge vergleichen
_______________________________________________
Ietf-languages mailing list
Ietf-languages <at> alvestrand.no
http://www.alvestrand.no/mailman/listinfo/ietf-languages
CE Whitehead | 30 Sep 23:03
Picon

Libya

Hi, I'm not sure what RFC 5646 regarding ISO 3166 requires here but if the change is adopted -- then I support having the short name Libya ( followed temporarily with a reference to the former name too if this is allowed -- is this what Doug has suggested?).  That said, I went to: http://tools.ietf.org/html/rfc5646
Section 3.1.5 "Description Field" says,
firstly:
" They are not intended to provide general background information or to provide all possible alternate names or designations. "

Thus may not need both names (but it might be nice for a time).

Secondly:
" For subtags taken from a source standard (such as ISO 639 or ISO 15924), the 'Description' fields in the record are also initially taken from that source standard."
I'm not sure what is meant by "initially" here. If the name changes in ISO-3166, are we then at the "initial" stage again, and required to take the new name as is?

The main guidelines in any case seem to be in section 3.4:
3.4 "Stability of IANA Registry Entries"
" 3. . . . The description MAY be broadened somewhat in scope, changed to add information, or adapted to the most common modern usage. For example, countries occasionally change their names; a historical example of this is "Upper Volta" changing to "Burkina Faso"."

Doug Ewell doug at ewellic.org Wed Sep 28 20:33:08 CEST 2011

> The UN Statistics Division has changed the M.49 name associated with their code element 434 from "Libyan Arab Jamahiriya" to "Libya." This could be the first step toward a corresponding name change in ISO 3166, so we might want to have the discussion now. > Traditionally, and in accordance with RFC 5646, Section 3.1.5, Description fields for subtags that are based directly on code elements in core standards like ISO 3166 match the core standard. This is so users of the Language Subtag Registry can look up the meaning of the subtag by consulting the code list for the core standard. (This would break if the core standard ever reused a code element and the Registry were forced to deviate from it, but I assume publicity and Comments fields would cover that case.) >In the case of ISO 3166, which defines a "long name" and a "short name," the Registry uses the short name, which is freely available and often corresponds to the name ordinary people (not standards wonks) use in practice. The correspondence is not always ideal; for example, "Democratic People's Republic of Korea" and "Republic of Korea" appear instead of the more common "North Korea" and "South Korea." > However, recent short-name changes in ISO 3166 such as "Bolivia, Plurinational State of" and "Venezuela, Bolivarian Republic of" have not been reflected in the Registry, because this list has considered these changes unnecessary for correctly identifying the country (the purpose of any Description field). > Currently, the short names for Libya in ISO 3166 are "Libyan Arab Jamahiriya" (English) and "Libyenne, Jamahiriya Arabe" (French). The Registry uses this English "short name" instead of the more common "Libya." The Arabic word "jamahiriya" occurs only in the name for Libya, while the ISO 3166 names for countries such as "Islamic Republic of Iran" and "Syrian Arab Republic" used the English word "republic." > According to Wikipedia, "Jumhūriyyah (Arabic: جمهورية‎) is the word for 'republic' in the Arabic language,"

Yes, that's right.

> while "Jamahiriya (Arabic: جماهيرية‎ jamāhīriyyah) is an Arabic term generally translated as 'state of the masses.'" The Wikipedia article on Gaddafi's Libya indicates that "jamahiriya" is a portmanteau invented by Gaddafi: > "The word jamāhīriyyah was derived from jumhūriyyah, which is the usual Arabic translation of 'republic'. It was coined by changing the component jumhūr — 'public' — to its plural form, jamāhīr — 'the masses'. Thus, it is similar to the term People's Republic.
Perhaps so. Good that you noted this.
> It is often left untranslated in English, with Libya's long-form name thus rendered as Great Socialist People's Libyan Arab Jamahiriya." <http://en.wikipedia.org/wiki/Great_Socialist_People%27s_Libyan_Arab_Jamahiriya#Name> > The name change in M.49 to simply "Libya" could be seen not only as a simplification of the short name to that used by most people in conversation, but also as a reflection of the current or expected ouster of Gaddafi and change in the form of government. Approximately 94 nations now recognize the National Transitional Council as the legitimate authority in Libya, while many others do not. > If this name change is adopted by ISO 3166/MA, and subsequently in the Registry—where the Bolivia and Venezuela changes were not accepted—it could be viewed by some as a political statement that the Registry adopts only those name changes that reflect Western political or diplomatic preferences (i.e. opposition to Gaddafi, Morales in Bolivia, and Chávez in Venezuela). Of course, this is not the purpose of the Registry, but it could be perceived that way by those who choose to. > I support making this change in the Registry if it shows up in 3166, > with the goal of keeping names brief and vernacular,
Do we have an option of not taking the name in 3166? (Just curious.)
> *not* with the goal of making any sort of statement. I suggest we look at future name changes in the same light. We might also consider adding the occasional second Description field that matches common use, such as "South Korea" or "Iran," to ease the transition and reduce the potential for controversy the next time this happens.
This is fine IMO -- if it's allowed.

Thanks.

Best,

--C. E. Whitehead
cewcathar <at> hotmail.com
> -- > Doug Ewell | Thornton, Colorado, USA | RFC 5645, 4645, UTN #14 > www.ewellic.org | www.facebook.com/doug.ewell | <at> DougEwell ­
_______________________________________________
Ietf-languages mailing list
Ietf-languages <at> alvestrand.no
http://www.alvestrand.no/mailman/listinfo/ietf-languages
Doug Ewell | 28 Sep 20:33
Favicon

Libya

The UN Statistics Division has changed the M.49 name associated with
their code element 434 from "Libyan Arab Jamahiriya" to "Libya."  This
could be the first step toward a corresponding name change in ISO 3166,
so we might want to have the discussion now.

Traditionally, and in accordance with RFC 5646, Section 3.1.5,
Description fields for subtags that are based directly on code elements
in core standards like ISO 3166 match the core standard.  This is so
users of the Language Subtag Registry can look up the meaning of the
subtag by consulting the code list for the core standard.  (This would
break if the core standard ever reused a code element and the Registry
were forced to deviate from it, but I assume publicity and Comments
fields would cover that case.)

In the case of ISO 3166, which defines a "long name" and a "short name,"
the Registry uses the short name, which is freely available and often
corresponds to the name ordinary people (not standards wonks) use in
practice.  The correspondence is not always ideal; for example,
"Democratic People's Republic of Korea" and "Republic of Korea" appear
instead of the more common "North Korea" and "South Korea."

However, recent short-name changes in ISO 3166 such as "Bolivia,
Plurinational State of" and "Venezuela, Bolivarian Republic of" have not
been reflected in the Registry, because this list has considered these
changes unnecessary for correctly identifying the country (the purpose
of any Description field).

Currently, the short names for Libya in ISO 3166 are "Libyan Arab
Jamahiriya" (English) and "Libyenne, Jamahiriya Arabe" (French).  The
Registry uses this English "short name" instead of the more common
"Libya."  The Arabic word "jamahiriya" occurs only in the name for
Libya, while the ISO 3166 names for countries such as "Islamic Republic
of Iran" and "Syrian Arab Republic" used the English word "republic."

According to Wikipedia, "Jumhūriyyah (Arabic: جمهورية‎) is the
word for 'republic' in the Arabic language," while "Jamahiriya (Arabic:
جماهيرية‎ jamāhīriyyah) is an Arabic term generally
translated as 'state of the masses.'"  The Wikipedia article on
Gaddafi's Libya indicates that "jamahiriya" is a portmanteau invented by
Gaddafi:

"The word jamāhīriyyah was derived from jumhūriyyah, which is the
usual Arabic translation of 'republic'. It was coined by changing the
component jumhūr — 'public' — to its plural form, jamāhīr —
'the masses'. Thus, it is similar to the term People's Republic. It is
often left untranslated in English, with Libya's long-form name thus
rendered as Great Socialist People's Libyan Arab Jamahiriya."
<http://en.wikipedia.org/wiki/Great_Socialist_People%27s_Libyan_Arab_Jamahiriya#Name>

The name change in M.49 to simply "Libya" could be seen not only as a
simplification of the short name to that used by most people in
conversation, but also as a reflection of the current or expected ouster
of Gaddafi and change in the form of government.  Approximately 94
nations now recognize the National Transitional Council as the
legitimate authority in Libya, while many others do not.

If this name change is adopted by ISO 3166/MA, and subsequently in the
Registry—where the Bolivia and Venezuela changes were not
accepted—it could be viewed by some as a political statement that the
Registry adopts only those name changes that reflect Western political
or diplomatic preferences (i.e. opposition to Gaddafi, Morales in
Bolivia, and Chávez in Venezuela).  Of course, this is not the purpose
of the Registry, but it could be perceived that way by those who choose
to.

I support making this change in the Registry if it shows up in 3166,
with the goal of keeping names brief and vernacular, *not* with the goal
of making any sort of statement.  I suggest we look at future name
changes in the same light.  We might also consider adding the occasional
second Description field that matches common use, such as "South Korea"
or "Iran," to ease the transition and reduce the potential for
controversy the next time this happens.

--
Doug Ewell | Thornton, Colorado, USA | RFC 5645, 4645, UTN #14
www.ewellic.org | www.facebook.com/doug.ewell | @DougEwell ­

_______________________________________________
Ietf-languages mailing list
Ietf-languages <at> alvestrand.no
http://www.alvestrand.no/mailman/listinfo/ietf-languages
Doug Ewell | 18 Sep 18:17
Favicon

Re: Portuguese subtags

António H F P A Emiliano - FCSH/UNL <ah dot emiliano at fcsh dot unl dot 
pt> wrote:

>> As a native English speaker, I didn't have any problems with the
>> English in these proposals.
>
> OK. So what does 'Minister's Council Resolution' mean in English?
>
> Is it a resolution issued/put forward by the council of a minister?
> Which minister in this particular case?
> What does council mean in this context?
> Is it a group of advisors?
> Or is it a formal gathering of close collaborators or subordinates?
> If the council is an advisory group or a formal body of collaborators
> how can it issue resolutions?
> Usw.

That isn't a question of native English or non-native English; it's a 
question of the Portuguese political structure.  I read "Minister's 
Council Resolution" as saying that there is a Minister's Council of some 
sort that issued a resolution.  I didn't ask how the council was 
constituted, or at which minister's pleasure it serves, or whether it 
has authority to issue resolutions.  I imagine an organizational chart 
of the Portuguese government would be of more use here than an English 
proofreader.

>> Look through the variant subtags in the Registry and you will find
>> many which are not specified to this level of precision.
>
> I don't really care about other variant subtags: as a Portuguese
> professional linguist and Professor of Portuguese Linguistics I just
> want this particular proposal to be well written and well conceived.
> I accept the need for a subtag <1990aolp> (I even proposed its final
> designation). However I cannot ignore the fact that there is not a
> single full specification for the orthography that it encodes.

Other variant subtags do provide some perspective on the guidelines for 
acceptability of new subtag proposals.  But the primary source is, of 
course, RFC 5646.

RFC 5646, Section 2.2.5 says that variants "are used to indicate 
additional, well-recognized variations that define a language or its 
dialects that are not covered by other available subtags."

RFC 5646, Section 3.5 gives expanded information on the qualifications 
for registering a variant.  Basically, if a language variation is 
well-enough known and not already available via a non-private BCP 47 
tag, it qualifies.  Some examples of variants of English that would not 
meet the criterion of "not already available" might be "Australian 
English" (use "en-AU") or "Jamaican Creole English" (use "jam").

There is a requirement to provide a reference to a published description 
of the language, but that is expressly to confirm whether the language 
variation is well-enough known and not already encoded, not to judge 
whether the variation is a "good" one or whether all countries where the 
basic language is spoken approve of the variation.  The last paragraph 
of Section 3.5 says:

"The Language Subtag Reviewer decides what constitutes 'good enough' 
reference material."

which means it is up to Michael to decide, not the rest of us; but 
immediately after that it says:

"This requirement [to provide a reference to a published description] is 
not intended to exclude particular languages or dialects due to the size 
of the speaker population or lack of a standardized orthography."

What I have seen from this discussion is that at least the 
orthographical reform identified with the year "1990" is indeed 
well-known, well enough for some countries or publications to refuse 
pointedly to adopt it while others do adopt it.  A BCP 47 subtag would 
serve the purpose of distinguishing text written in the new orthography 
from other Portuguese text.  Does anyone deny that such a distinction 
exists, for a large enough text sample?

>> I don't think there are any truly authoritative dictionaries for
>> Scouse or Boontling, either.
>
> We are discussing here a major world language and a very
> controversial reform that has yet to be fully implemented 21 years
> after its official approval. I say this with all due respect to minor
> language variants, of course.

English (the basic language of Scouse and Boontling) is sometimes 
considered to be a major world language, too.

Orthographical reforms do take some time, and aren't always successful 
in the end.  I've heard that some users of de-1996 have reverted to 
de-1901, for various reasons, which other German speakers held it in 
contempt and never adopted it.

>> I hope I am reading the situation wrong.
>
> You are IMHO.

I'm glad to hear you say that you do support the creation of a subtag, 
because the language variation does exist.  I hope when Michael returns 
from his travels, we can get a speedy resolution to the question of 
"good-enough reference material" and move forward.

> I am a vocal opponent to this reform. I think it is a shambles, a
> fraud, a crime (this is my first and last nonlinguistic appraisal
> in this discussion of the matter under scrutiny). I have participated
> in this discussion with total fairness. I have stuck to facts, like
> for instance the fact that there is no official specification of the
> reform. This is a fact. If this group does not deem this fact to be
> relevant move on. I have not raised a single political issue in this
> discussion and I have not found any political issues being raised by
> any of the participants.
>
> I strongly oppose (with facts) that such an important subtag be
> associated to such a unworthy and problematic reference like the
> online resource referred to in previous messages. I have suggested
> alternatives (printed dictionaries).

When Michael is available, I would like to see him rule specifically on 
the application of the last paragraph of RFC 5646, Section 3.5 to the 
present question of whether the available references are acceptable for 
registration.  That should be the final word.

--
Doug Ewell | Thornton, Colorado, USA | RFC 5645, 4645, UTN #14
www.ewellic.org | www.facebook.com/doug.ewell | @DougEwell ­ 
Picon
Favicon

Re: Portuguese subtags (was Re: Ietf-languages Digest, Vol 104, Issue 16)

Hello.

On 2011/09/16, at 11:00, ietf-languages-request <at> alvestrand.no wrote:

> Message: 1
> Date: Thu, 15 Sep 2011 15:02:13 -0700
> From: "Doug Ewell" <doug <at> ewellic.org>
> To: ietf-languages <at> iana.org
> Subject: Portuguese subtags (was: RE: Ietf-languages Digest, Vol 104,
> 	Issue 15)
>
> Ant?nio H F P A Emiliano (FCSH/UNL) <ah dot emiliano at fcsh dot unl
> dot pt> wrote:
>
> As a native English speaker, I didn't have any problems with the  
> English
> in these proposals.

OK. So what does 'Minister's Council Resolution' mean in English?

Is it a resolution issued/put forward by the council of a minister?
Which minister in this particular case?
What does council mean in this context?
Is it a group of advisors?
Or is it a formal gathering of close collaborators or subordinates?
If the council is an advisory group or a formal body of collaborators  
how can it issue resolutions?
Usw.

>> I strongly object to the reference to an "official vocabulary": there
>> is no such thing. There is an online database that contains errors
>> and typos. Furthermore it is not a stable resource and no complete
>> wordlist can be extracted from it. There are at least two
>> commercially available dictionaries in print that could be used as
>> references, provided that the proposal mentions i) that these
>> dictionaries do not coincide 100%, and ii) that these dictionaries do
>> not fulfil the stipulation of the 1990 Treaty.
>
> The argument seems to be that without a stable, definitive, error-free
> and typo-free reference, this is not a variation worthy of tagging.  I
> don't think there is general consensus for that position.  Look  
> through
> the variant subtags in the Registry and you will find many which  
> are not
> specified to this level of precision.

I don't really care about other variant subtags: as a Portuguese  
professional linguist and Professor of Portuguese Linguistics I just  
want this particular proposal to be well written and well conceived.  
I accept the need for a subtag <1990aolp> (I even proposed its final  
designation). However I cannot ignore the fact that there is not a  
single full specification for the orthography that it encodes.

>>> Message: 3
>>> Date: Thu, 15 Sep 2011 12:50:09 +0200
>>> From: Luc Pardon <lucp <at> skopos.be>
>>> To: ietf-languages <at> iana.org
>>> Subject: Re: Portuguese subtags
>>>
>
>> There are no authoritative dictionaries for the 1990 reform. No well-
>> known publications.
>
> I don't think there are any truly authoritative dictionaries for  
> Scouse
> or Boontling, either.

We are discussing here a major world language and a very  
controversial reform that has yet to be fully implemented 21 years  
after its official approval. I say this with all due respect to minor  
language variants, of course.

> I don't know Portuguese, so I can't comment on the worthiness of these
> proposals from a linguistic perspective.  But this is starting to feel
> like an effort to use legal technicalities to reject the proposals on
> the basis of not liking the reforms.

I resent that. Please read the preceding messages.

> I hope I am reading the situation
> wrong.

You are IMHO.

> Message: 4
> Date: Fri, 16 Sep 2011 07:55:03 +0100
> From: Jo?o Miguel Neves <joao <at> silvaneves.org>
> To: ietf-languages <at> alvestrand.no
> Subject: Re: Portuguese subtags (was: RE: Ietf-languages Digest, Vol
> 	104,	Issue 15)
>
> Em 16-09-2011 06:05, Philip Newton escreveu:

> People seem to get sidetracked by political issues, like whether the
> linguistic community likes a change or not, more than if there are
> references or if the ortography change is relevant. Those eventually
> appeared in the discussion

I do not agree. Absolutely. I am a vocal opponent to this reform. I  
think it is a shambles, a fraud, a crime (this is my first and last  
nonlinguistic appraisal in this discussion of the matter under  
scrutiny). I have participated in this discussion with total  
fairness. I have stuck to facts, like for instance the fact that  
there is no official specification of the reform. This is a fact. If  
this group does not deem this fact to be relevant move on. I have not  
raised a single political issue in this discussion and I have not  
found any political issues being raised by any of the participants.

I strongly oppose (with facts) that such an important subtag be  
associated to such a unworthy and problematic reference like the  
online resource referred to in previous messages. I have suggested  
alternatives (printed dictionaries).

>
Best regards. - A.
Picon
Favicon

Re: Language subtag registration for 1990aolp (CEWhitehead) [was Ietf-languages Digest, Vol 104, Issue 17]


On 2011/09/17, at 11:00, ietf-languages-request <at> alvestrand.no wrote:

> Message: 1
> Date: Fri, 16 Sep 2011 23:12:12 -0400
> From: CE Whitehead <cewcathar <at> hotmail.com>
> To: <ietf-languages <at> iana.org>
> Subject: Language subtag registration for 1990aolp

> I briefly went to both Publico and Diario de Noticias, after  
> reading Antonio's post (Antonio says that "Publico" is not adopting  
> the reform).
> (One Note:  Regardless of whether or not these newspapers are  
> adopting the reform, unfortunatley both "Diario de Noticias" and  
> "Publico" sometimes carry the same articles. An example is the  
> following article -- the first copy came from "Diario de Noticias;"  
> the second from "Publico":
>
> "O ministro da Educa??o e Ci?ncia, Nuno Crato afirmou hoje em Valpa? 
> os que sempre houve professores com contratos a termo de um m?s,  
> mas que este ano se verificou uma renova??o autom?tica."
>
> "O ministro da Educa??o e Ci?ncia, Nuno Crato, afirmou hoje, em  
> Valpa?os, que sempre houve professores com contratos a termo de um  
> m?s, mas que este ano se verificou uma renova??o autom?tica."
>
> In this case I guess the spelling is the same both with/without  
> implementing the orthographic reform -- is this correct?

Yes, because that quotation has no words affected by the reform.

>   But I wonder what what spelling will be used if these newspapers  
> opt to carry other identical articles where there are words that  
> are not spelled the same way pre- and post-reform?  Oh well.)

There is Portuguese news agency called Lusa which has adopted the  
reform. Many newspapers opt to quote from Lusa's dispatches about  
current events or last minute news without any text editing. Público  
and others however always correct the spelling in the Lusa texts.

> I did find another text:
>
> "Na sequ?ncia de um relat?rio publicado em Abril pelo Tribunal de  
> Contas sobre os encargos assumidos e n?o pagos pela Madeira, o INE  
> e o BdP avaliaram as contas da regi?o e detectaram que ?as d?vidas  
> contra?das desde 2004 e objecto de Acordos de Regulariza??o de D? 
> vidas (ADR) em 2008 e 2009 n?o foram registadas como encargos  
> assumidos e n?o pagos, n?o tendo sido igualmente comunicadas ?s  
> autoridades estat?sticas?."
>
> This is from Publico  (http://economia.publico.pt/noticia/dividas- 
> da-madeira-obrigam-a-revisao-dos-defices-entre-2008-e-2010_1512210);
>
> So I do have a question:
> would  "
> contra?das" be written without the accent if this were written  
> according to the 1990 orthographic reform?

No.

> In any case, my take is that whether there is a suitable reference  
> or not, there is clearly a demonstrated need for a subtag for an  
> orthograpy if an online newspaper is using it.  So no problem there.
>
> (Also, of course, there is no way that I know of for ietf-languages  
> to enforce the agreement, that is to force the creation of a good  
> reference vocabulary for the orthography agreed on in the 1990  
> accord.)
>
> So I don't oppose this subtag, not at all.  I just have these  
> questions, because of all the conversation.  Sorry.
>
> (Also I apologize to Doug if I asked to have additional sources  
> listed in the subtag request form itself;
> additional sources can be cited on the list I guess;
> however I did not come up with a good dictionary for Portuguese  
> Portuguese that follows the 1990 accord --
>
> unless of course
>
> http://www.priberam.pt/dlpo/
> Dicionaria Priberam,
> is acceptable.)

No it is not acceptable. I use that dictionary daily and I have  
respect for that company. The problem is that this dictionary  
includes several thousand Galician words as if they were PT words  
(because there is a so-called Galician Academy for the Portuguese  
Language which has accepted the 1990 reform so that may be accepted  
as a Portuguese-speaking ... thing). Also Priberam has no stable  
form. It is however a respectable resource, which is not the case of  
the aforementioned VOP.

There is a good dictionary in print by Porto Editora. There are two  
not so good dictionaries by Texto Editora. These latter two were  
compiled from materials stolen (yes, stolen) from the Portuguese  
Academy by one of the authors of the 1990 reform. However per the  
1990 treaty these dictionaries cannot be considered authoritative  
references regarding the application of the reform. Until a common  
vocabulary is published by all 8 PT-speaking countries there will be  
no official specification for the reform. That is the letter and  
spirit of the treaty that was signed in 1990.

Best regards. - A.
Picon
Favicon

Re: Re: Language subtag registration for 1990aolp (Jo?o Miguel Neves) [was Ietf-languages Digest, Vol 104, Issue 15]


On Sep 15, 2011, at 22:27, ietf-languages-request <at> alvestrand.no wrote:

> ------------------------------
>
> Message: 2
> Date: Thu, 15 Sep 2011 19:48:03 +0100
> From: Jo?o Miguel Neves <joao <at> silvaneves.org>
> To: ietf-languages <at> alvestrand.no
> Subject: Re: Language subtag registration for 1990aolp
>
> For examples of texts with this orthography check any Portuguese
> newspaper (they've adopted the new orthography within the last year):

!!!

> http://www.dn.pt/inicio/portugal/interior.aspx? 
> content_id=1998432&seccao=Madeira&page=-1
>
> Newspaper sites:
> http://www.dn.pt/
> http://www.ionline.pt/
> http://www.publico.pt/

This not accurate information.
Not all newspapers have adopted the reform.
In fact 'Público' has stated that they will NOT adopt it.

> <This variant subtag is intended to apply to text that uses the
> <Portuguese orthography introduced in an international agreement  
> signed
> <in 1945 and implemented from 1945 in Portugal and 1971 in Brazil.
>
> Jo?o, "from 1945 in Portugal and 1971 in Brazil"?
> It may seem that Brazil adopted the 1945 rules in 1971. Which is  
> not the case.

Right.

BR rejected the 1945 reform within 2 years of having signed it.
I do think that these proposals require a solid background and  
accurate descriptions (and precise wording).

Regards. - A.

Gmane