John--<br><br>I don't think, at this stage of the game, that trying to so switch over to the<br>3-character language codes would be a practical one for Asterisk. The "use-the-<br>2-character-language-code-if-one-exists-else-use-the-3-char-code" rule covers<br>
the situation quite well. The 2-char code covers about 200 of the most "popular"<br>languages. That leaves the remaining 6700 or so living languages to be covered<br>under the 3-char tables.<br><br>Seeing as how only Swedish and Czech speakers would be affected, I'd say<br>
that making the corrections, and letting them update their dialplans or source<br>preferred language settings to fix the resulting problems will be more minimal<br>than waiting another year for a couple hundred/thousand/whatever more installations<br>
using those languages experience the joy when it does get addressed. Make big<br>bold notations in the release notes. Send out notices via the users and dev lists.<br>You can try to give them notice. But, they'll update to the new version, have problems,<br>
debug it, and make the fix, then they'll read the release notes to figure out why the <br>change was made, and then kick themselves for not reading the notes first. That's<br>the way **I** work, usually ;)<br><br>
murf<br><br><br><br><br><div class="gmail_quote">On Mon, Nov 16, 2009 at 1:37 PM, John Todd <span dir="ltr"><<a href="mailto:jtodd@digium.com">jtodd@digium.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
[title changed, threading retained]<br>
<br>
Hmmm... Good point. This is a serious namespace conflict. The<br>
problem is that it requires fixes for backwards compatibility. Argh.<br>
While the most correct response would be to just move over to<br>
ISO-639-2 standards (three letter language codes) as per the standard<br>
here:<br>
<br>
<a href="http://www.loc.gov/standards/iso639-2/php/code_list.php" target="_blank">http://www.loc.gov/standards/iso639-2/php/code_list.php</a><br>
<br>
But... sometimes doing the "correct" thing causes more problems than<br>
it resolves. Is there a strenuous opinion from anyone that we should<br>
change? I'd like to solicit opinions. Personally, I'd lean towards<br>
the three-digit codes since it's the better thing to do, but...<br>
<br>
This is actually a pretty big change. For instance, all of our<br>
language soundfile distributions have two-letter names. If we go to<br>
three-digit versions, then we either need to symlink the old ones, or<br>
keep the old ones (which then will be slowly falling out of sync), or<br>
delete the old ones (which will cause every distribution to fail<br>
that's already out there, and which will be out there... forever.)<br>
<br>
JT<br>
<br>
<br>
<br>
On Nov 16, 2009, at 10:23 AM, Steve Murphy wrote:<br>
<br>
> Pavel--<br>
><br>
> I've noticed myself that cs and cz are used in the Asterisk source.<br>
> But it's not a matter of what seems right...<br>
> the code should be from ISO 639-1 if there is a 2-letter language<br>
> code there, or ISO-639-2's 3 letter code instead.<br>
> "cs" is the correct 2 letter code for Czech. "ces" is the correct 3-<br>
> digit code.<br>
><br>
> I also note that "se" is used for swedish, but really, it should be<br>
> "sv". "se" is the 2-letter code for Northern Saami,<br>
> spoken in Norway, otherwise known as “Norwegian Lapp”, with 3-digit<br>
> code "sme". The 3-letter code for swedish is<br>
> "swe".<br>
><br>
> I haven't filed any bug report for this yet; you are welcome to; for<br>
> both these languages if you want.<br>
><br>
> The only problem I can see with "fixing" these wrong language codes,<br>
> is that those involved will have<br>
> to make changes to their source/dialplans/whatever, or they suddenly<br>
> will find that things aren't<br>
> quite working right anymore. But a conflict (cs vs. cz) is a<br>
> conflict and really should be fixed, in 1.4, 1.6.x and trunk,<br>
> and everyone will just have to adapt. While sv vs. sw is apparently<br>
> not yet a conflict, someday, the true owners<br>
> of se will want to provide translations, and then there will be a<br>
> conflict also. Might as well get it straightened out<br>
> now.<br>
><br>
> murf<br>
><br>
><br>
> On Mon, Nov 16, 2009 at 10:14 AM, Pavel Troller <<a href="mailto:patrol@sinus.cz">patrol@sinus.cz</a>><br>
> wrote:<br>
> Hi there,<br>
> I've found that we have (at least in 1.6.1 branch) a conflict in<br>
> language<br>
> codes for the Czech language.<br>
> - app_voicemail.c requires the "cz" code to activate the Czech<br>
> voicemail<br>
> syntax rules. It doesn't work if the "cs" code is used (it is not<br>
> used<br>
> anywhere in the code).<br>
> - say.c contains the following:<br>
><br>
> } else if (!strncasecmp(language, "cz", 2)) { /* deprecated<br>
> Czech syntax */<br>
> static int deprecation_warning = 0;<br>
> if (deprecation_warning++ % 10 == 0) {<br>
> ast_log(LOG_WARNING, "cz is not a standard<br>
> language code. Please switch to using cs instead.\n");<br>
> }<br>
> return ast_say_number_full_cs(chan, num, ints,<br>
> language, options, audiofd, ctrlfd);<br>
><br>
> but if the user follows the request, the voicemail stops speaking<br>
> properly.<br>
> So, which language code should be preferred ? I think that cz is<br>
> better,<br>
> becaus cs means "CzechoSlovak" and we don't have such entity<br>
> anymore, Slovakia<br>
> has its own "sk" code, so it should be okay to use cz for Czech...<br>
> With regards,<br>
> Pavel Troller<br>
<br>
---<br>
John Todd <a href="mailto:email%3Ajtodd@digium.com">email:jtodd@digium.com</a><br>
Digium, Inc. | Asterisk Open Source Community Director<br>
445 Jan Davis Drive NW - Huntsville AL 35806 - USA<br>
direct: +1-256-428-6083 <a href="http://www.digium.com/" target="_blank">http://www.digium.com/</a><br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
--Bandwidth and Colocation Provided by <a href="http://www.api-digital.com--" target="_blank">http://www.api-digital.com--</a><br>
<br>
asterisk-dev mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-dev" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-dev</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Steve Murphy<br>ParseTree Corp<br><br>