<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'><div dir='ltr'>
Hi.<br><br>António H F P A Emiliano (FCSH/UNL) ah.emiliano at fcsh.unl.pt<br>Thu Aug 25 16:48:54 CEST 2011<br><br>> 1945 - Portuguese orthography of 1945 (Convenção Ortográfica Luso- <br>> Brasileira, 1945)<br>> 1990 - Portuguese orthography of 1990 (Acordo Ortográfico da Língua <br>> Portuguesa, 1990) --><br>> --> alternatives: 1991 (ratification), 2008 (transitional <br>> enforcement), 2014 (full enforcement?)<br><br><br>We cannot predict the full enforcement date so I would probably if I were you avoid 2014 (as you note the full enforcement date would be acceptable as the language subtag name after all ratify this treaty).<br><br>A question for you: is it acceptable to you to use abbreviations of the Portuguese terms for this treaty, "acordo -> acord" or "convencao -> conv" ? I suppose these end up being too opaque.)<br><br>> Regional variants should also be encoded in subtags: at least one for <br>> each the signatories of the Treaty of 1990.<br>Hmm. Sometimes people have suggested doing this with country codes (when the regional boundary is the country). Of course indicating that a language is pt-[xxxxxxxx]-PT or anything else does not mean it is Portuguese Portuguese as specified by the 1990 treaty.<br>Do you prefer to register a variant instead of using PT, etc?<br><br>Philip Newton philip.newton at gmail.com<br>Thu Aug 25 16:59:39 CEST 2011<br>> When someone comes along and says, "I have material which I wish to<br>> tag with language subtags. I have a business need to distinguish<br>> between [variety 1] and [variety 2], and would like to propose two<br>> subtags to cover them", that's when variant subtags get created.<br><br>I agree with Phillip here.<br><br>Best,<br><br>--C. E. Whitehead<br>cewcathar@hotmail.com <br> </div></body>
</html>