<div dir="ltr">Hi DM/Chris<div><br></div><div>The standard is defined in BCP47 which only supports a '-'. (<a href="http://tools.ietf.org/html/bcp47">http://tools.ietf.org/html/bcp47</a>)</div><div><br></div><div style>
as documented by JAVA here: <a href="http://docs.oracle.com/javase/7/docs/api/java/util/Locale.html#def_variant">http://docs.oracle.com/javase/7/docs/api/java/util/Locale.html#def_variant</a>. Java seems to support both a dash and an underscore.</div>
<div style><br></div><div style>DM, we should ideally be using the Java functionality which supports both, rather than implementing our own decoding scheme. Not sure what we do/don't do here.</div><div style>Chris</div>
<div style><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 10 February 2013 20:09, DM Smith <span dir="ltr"><<a href="mailto:dmsmith@crosswire.org" target="_blank">dmsmith@crosswire.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Chris,<br>
We've got this in JSword (not sure it works) for a while now for the next release. We used the codes as you've given here. But in the conf file you have ur_Deva. We're not expecting an _ but a -. We can change the code. Please advise.<br>
<br>
In Him,<br>
DM<br>
<div class="HOEnZb"><div class="h5"><br>
On Feb 10, 2013, at 5:56 AM, Chris Little <<a href="mailto:chrislit@crosswire.org">chrislit@crosswire.org</a>> wrote:<br>
<br>
> Just a quick heads up:<br>
><br>
> In general, locale codes (the Lang= field of .confs) can have subtags that indicate region, script, etc. Ideally these should be dealt with in some fashion by front ends since they identify important distinctions (in the eyes of the module maker or publisher at least).<br>
><br>
> When unknown subtags are encountered, it's probably best to recursively fall back to the tag minus its right-most subtag. For example, if 'en-Latn-US' is unknown, fall back to 'en-Latn'. If that is unknown, fall back to 'en'. (Hopefully nearly all language subtags are known.)<br>
><br>
> We should handle this in the library, but currently don't. :(<br>
><br>
><br>
> As a specific case in point:<br>
> We now have two Urdu translations. They're the same translation and differ in their script (one is Arabic, the other Devanagari). Their language codes (as of the 1.2.1 release just made, which corrected the code for the Devanagari version) are: ur (Urdu in Arabic script--the usual script for Urdu) and ur-Deva (Urdu in Devanagari script).<br>
><br>
> Possible behaviors are to categorize the ur-Deva module as belonging to an unknown language (bad), to fall back and categorize it as simply Urdu (better, but certainly confusing if the language name is written in Arabic and the module is itself written in Devanagari), or to categorize it separately as Urdu written in Devanagari (best).<br>
><br>
> For implementers who localize the language name, Urdu written in Arabic is written "اردو". Urdu written in Devanagari is written "उर्दू".<br>
><br>
> --Chris<br>
><br>
> _______________________________________________<br>
> sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
> <a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
> Instructions to unsubscribe/change your settings at above page<br>
<br>
<br>
_______________________________________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page</div></div></blockquote></div><br></div>