> On Oct 15, 2017, at 5:02 PM, David Haslam wrote:
>
> In reply to:
>
>>
>> And how about another problem?
>>
>> What does a cross-reference to 1 Kings 13:12 point to?
>
> All references within a module should use an OSIS ID. If so it is not a
> problem.
>
> User input is a different story
In reply to:
>
> And how about another problem?
>
> What does a cross-reference to 1 Kings 13:12 point to?
All references within a module should use an OSIS ID. If so it is not a
problem.
User input is a different story.
>
> In a Catholic Bible with 1/2/3/4 Kings, it should point to 1 Samuel 13
The problem of "no spaces" when both readings are shown is very easy to
solve.
Just take proper care when making the module.
I documented this ages ago in the wiki page for OSIS Bibles.
Rather than having (may|can) you'd have ( may| can) - using simplified
notation to illustrate.
It can help al
David, it is hard to see the context of your reply when you post from Nabble.
Please include the context in your post.
See below:
> On Oct 15, 2017, at 11:43 AM, David Haslam wrote:
>
> Something that we forgot to review when Av11n was first implemented?
No. We didn’t have translations of the
There is no other option for the front-end.
The engine (SWORD and JSword) will only show one or the other of two variants.
I’m pretty sure JSword doesn’t allow “the other”. To do otherwise means that
the engine has to determine another mechanism which the front-end has to
choose. Example, show
Something that we forgot to review when Av11n was first implemented?
And how about another problem?
What does a cross-reference to 1 Kings 13:12 point to?
In a Catholic Bible with 1/2/3/4 Kings, it should point to 1 Samuel 13:12
but would our scripts to fix cross-references even have a clue abou
I would agree that makes sense for a front-end that has UI support for
selecting variants,
but otherwise, the user never even gets to see the text for the Secondary
Reading.
Remaining invisible is much worse than any potential confusion!
The problem therefore never gets reported to the app develo
An Italian user came into #xiphos with several questions. One was about
book name localization. Only these locale.d files contain translations
for the Apocrypha book names.
fr_abbrev.conf
fr_abbrev-utf8.conf
fr.conf
fr-utf8.conf
ga-utf8.conf
ja-utf8.conf
lt-utf8.conf
sk.conf
sk-utf8.conf
vi-utf8
Default should be to show only the first variant. Confusing otherwise.
— DM Smith
> On Oct 15, 2017, at 7:34 AM, David Haslam wrote:
>
> Xiphos already has UI support for OSIS Variants. It works fine for a module
> with variants.
>
> When installed in other apps (such as PocketSword for iO
Xiphos already has UI support for OSIS Variants. It works fine for a module
with variants.
When installed in other apps (such as PocketSword for iOS or And Bible for
Android OS),
such a module should (in theory at least) display All Readings [as the
fall-back default].
NB. Unfortunately, PocketS
10 matches
Mail list logo
