Would there be any objection if I do following:
1) Many of the description lines of our locale files have the language
name in long form with an added (Unicode)
e.g. ru_RU-utf8 reads as follows:
[Meta]
Name=ru_RU
Description=Russian (Unicode)
I see no good reason that the (Unicode) is there.
I think your suggestion makes sense. It is how we do it in JSword.
Several places I've run into the need to have a designation beyond lang:
Portuguese (Portugal vs Brazil), Chinese (Traditional vs Simplified) and Arabic
(Egypt vs ???). In the case of Chinese it is a script difference, but the
On Fri, 2014-01-03 at 10:54 -0500, DM Smith wrote:
BTW, I like how Java searches for localized resource files. The actual
implementation is rather complex (because it searches multiple
locations), but to simplify:
Given a language code, a country code and a script code (script is new
to Java
On Jan 3, 2014, at 11:37 AM, Peter von Kaehne ref...@gmx.net wrote:
On Fri, 2014-01-03 at 10:54 -0500, DM Smith wrote:
BTW, I like how Java searches for localized resource files. The actual
implementation is rather complex (because it searches multiple
locations), but to simplify:
Given a
Hi guys,
Let me clear up 2 things, and suggest a third.
1) SWORD does have fallback locale logic:
http://crosswire.org/svn/sword/trunk/src/mgr/localemgr.cpp
(search for setDefaultLocaleName)
The problem is here:
if (!getLocale(tmplang)) {
// then continue to search for a fallback
}
On Fri, Jan 03, 2014 at 10:54:03AM -0500, DM Smith wrote:
Several places I've run into the need to have a designation
beyond lang: Portuguese (Portugal vs Brazil), Chinese
(Traditional vs Simplified) and Arabic (Egypt vs ???). In the
case of Chinese it is a script difference, but the others
On Jan 3, 2014, at 2:52 PM, Matej Cepl mc...@redhat.com wrote:
On Fri, Jan 03, 2014 at 10:54:03AM -0500, DM Smith wrote:
Several places I've run into the need to have a designation beyond lang:
Portuguese (Portugal vs Brazil), Chinese (Traditional vs Simplified) and
Arabic (Egypt vs ???).
Thanks Troy,
Both for bug-fix and for the advice. I will see what I can do wrt
creation of adequate parents where these are needed.
On Fri, 2014-01-03 at 12:16 -0700, Troy A. Griffitts wrote:
Remember, we have MANY MORE language modules than we have locales for
the engine. Wycliffe alone has
Troy,
Chris has documented that the locale mechanism should look for 3 things:
language, optional country and optional script. The code as it stands works for
any two, treating script as country (I didn't look but assume that country can
take a 4 character script.).
The standard (I read it at
As you will see from sword-svn I have created the missing parent files
etc.
I left Chinese alone as I am a bit lost with that.
Peter
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
10 matches
Mail list logo
