Update to note: Apparently BibleTime has a setting in its
configuration that allows the user to specifically select which
language Bible book names will be displayed in. This is used across
all parsing and display.
On Tue, Sep 11, 2012 at 9:08 PM, DM Smith wrote:
>
> On Sep 11, 2012, at 8:27 PM,
On Tue, Sep 11, 2012 at 9:52 AM, Jonathan Morgan wrote:
> For the record, BPBible allows the locale for book names to be selected
> independently from the locale for the user interface (though it will default
> to being the same). From memory this was added to handle the case where
> book names w
On Sep 11, 2012, at 8:27 PM, Greg Hellings wrote:
> On Mon, Sep 10, 2012 at 8:01 PM, DM Smith wrote:
>> This is a hard question. And a good one.
>>
>> For the record (not saying it is right or that it is best or even good) here
>> is how JSword does it:
>> It does not use the Locale of the mo
On Mon, Sep 10, 2012 at 8:01 PM, DM Smith wrote:
> This is a hard question. And a good one.
>
> For the record (not saying it is right or that it is best or even good) here
> is how JSword does it:
> It does not use the Locale of the module.
> It uses the OSIS book names first. (Assumes that the
For the record, BPBible allows the locale for book names to be selected
independently from the locale for the user interface (though it will
default to being the same). From memory this was added to handle the case
where book names were available for another language but no one was ever
likely to
I agree - it's a very good question, and more important for some front-ends
than for others.
Front-ends such as *And Bible* do not include a text entry method for "go to
passage".
*And Bible* has a 2 dimensional table for Passage; selecting Book, then
Chapter, then (optionally) Verse.
/The latte
