[jsword-devel] Idea for optimisation/improvement in iso639 lang props init

[Martin Denham]

Hi,

David's recent comments on the Sword mailing list seem relevant.  They might
imply that a more limited list of languages might be acceptable and he also
mentions the approach taken by Xiphos.  He says:

"Referring to http://www.crosswire.org/wiki/DevTools:confFiles
the only language related element is lang itself.
This means that when a front-end encounters a new module for which it cannot
yet provide a look-up for the localized language name, it will show Unknown
as the name of the language. That's what Xiphos does, for example.
As a fall-back position, might it be sensible to allow the conf file to
optionally include the localized language name in addition to the lang
element?
This would be processed as follows:
If the lang identifier can be looked up, use the look-up value.
If not, then if the conf file includes the localized language name, use
that.
Then if not either, fall back to using unknown, as at present."


Regards
Martin

On 22 December 2010 22:42, Martin Denham <mjdenham at gmail.com> wrote:

> I was wondering if we need the iso639 properties files if the language
> codes and names returned by the standard Locale class contained all the
> codes and names that are in the large properties file - I don't know if they
> do.  Using Locale could (I think) also automatically give us locale specific
> country names automatically for all Locales e.g. Angličtina instead of
> English on Czech mobiles.
>
> I haven't tried this out yet and we are only talking about 2 secs at
> startup but I am trying to whittle away the 17 secs it currently takes to
> start up JSword-And Bible.  However, this does possibly give other
> advantages.
>
>
> On 22 December 2010 18:04, DM Smith <dmsmith at crosswire.org> wrote:
>
>> I've gone back and forth on this one. The goal is to have names for all
>> the codes. There are a bunch of minority languages with Bibles in beta that
>> this covers.
>>
>> The simplest solution is to rename the _en file to be the default.
>>
>> The bigger problem is that the confs are fully read on startup which is in
>> necessary. This is causing the Lang lookup.
>>
>> In Him,
>> DM
>>
>> Cent from my fone so theer mite be tipos. ;)
>>
>> On Dec 22, 2010, at 7:07 AM, Martin Denham <mjdenham at gmail.com> wrote:
>>
>> > I have occasionally tried to improve the slow start-up times of And
>> Bible & JSword without much success.  However, one area which I have a
>> suspicion may take time is property file loading.
>> >
>> > I run out of memory part way through when profiling startup but I notice
>> iso639.properties which has 7600 lines can take 2 seconds to load up on slow
>> phones.  I wonder if, instead of storing the language codes in properties
>> files we could use methods like Locale.getDisplayLanguage(loc) and other
>> Locale methods to completely remove the need for the iso639 properties
>> files.
>> >
>> > What do you think?
>> >
>> > Regards
>> > Martin
>> >
>> > _______________________________________________
>> > jsword-devel mailing list
>> > jsword-devel at crosswire.org
>> > http://www.crosswire.org/mailman/listinfo/jsword-devel
>>
>> _______________________________________________
>> jsword-devel mailing list
>> jsword-devel at crosswire.org
>> http://www.crosswire.org/mailman/listinfo/jsword-devel
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.crosswire.org/pipermail/jsword-devel/attachments/20101229/511eb839/attachment.html>