[sword-devel] Sword 1.6.x and various frontends

[Luke Schroeder]

I'm slowly but surely working on getting our translation's electronic 
bible published.
I can only install the file into Xiphos when I have it unzipped.  It 
installs into BPBible Porteable fine from the Zip file.

I cannot install it at all into Alkitab or Bibledesktop.
XULrunner recognizes the file I installed from Xiphos.  Alkitab and 
Bibledesktop do not.
After several hours of trying to figure this out, I decided I would go 
here for help.  Are several of the frontends for SWORD not capable of 
using Sword 1.6.x?  I came to this hypothesis because my translation 
requires NRSV versification and I used the most current sword to make it.


These are the steps I took:
- I exported from Paratext to OSIS.
- I used the most current OSIS2Mod.
- I configured it to use NRSV's versification and rawtext
- I manually created .config file
- I manually setup a zip file to work with this.

Please give me any tips I might be missing here.  I need to send the 
file on to my boss.


Blessings,
Luke



___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Sword 1.6.x and various frontends

[Jonathan Morgan]

Hi Luke,

On Tue, May 24, 2011 at 5:11 PM, Luke Schroeder  wrote:

> I'm slowly but surely working on getting our translation's electronic bible
> published.
> I can only install the file into Xiphos when I have it unzipped.  It
> installs into BPBible Porteable fine from the Zip file.
> I cannot install it at all into Alkitab or Bibledesktop.
> XULrunner recognizes the file I installed from Xiphos.  Alkitab and
> Bibledesktop do not.
> After several hours of trying to figure this out, I decided I would go here
> for help.  Are several of the frontends for SWORD not capable of using Sword
> 1.6.x?  I came to this hypothesis because my translation requires NRSV
> versification and I used the most current sword to make it.
>

As far as I know, any frontends based on JSword (e.g. Alkitab, BibleDesktop,
FireBible, AndBible) will not be able to support other versifications.

As for the other applications, using Sword 1.6.x does not necessarily imply
that other versifications are well supported.  I know for both BPBible and
Xiphos that only the KJV versification is supported.  While books with other
versifications are able to be installed and opened, they will not go to the
correct references.

Jon
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Sword 1.6.x and various frontends

[David Haslam]

Front-ends based on JSword do not yet have any support for 
http://crosswire.org/wiki/Alternate_Versification Alternate Versification .
This is because JSword itself is not yet at that stage, though DM assures us
that they are working towards that goal.

To see which apps are based on SWORD and which on JSword, see the 
http://crosswire.org/wiki/Main_Page Main page .

Finally, it should also be understood that some SWORD-based front-ends do
not have "full support" for av11n.
See also  http://crosswire.org/wiki/Choosing_a_SWORD_program
http://crosswire.org/wiki/Choosing_a_SWORD_program 

Conclusion: Please pray for the programmers in each development team.

David


--
View this message in context: 
http://sword-dev.350566.n4.nabble.com/Sword-1-6-x-and-various-frontends-tp3546296p3546790.html
Sent from the SWORD Dev mailing list archive at Nabble.com.

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Sword 1.6.x and various frontends

[Daniel Owens]

On 05/24/2011 06:21 AM, Jonathan Morgan wrote:

Hi Luke,

On Tue, May 24, 2011 at 5:11 PM, Luke Schroeder > wrote:


I'm slowly but surely working on getting our translation's
electronic bible published.
I can only install the file into Xiphos when I have it unzipped.
 It installs into BPBible Porteable fine from the Zip file.
I cannot install it at all into Alkitab or Bibledesktop.
XULrunner recognizes the file I installed from Xiphos.  Alkitab
and Bibledesktop do not.
After several hours of trying to figure this out, I decided I
would go here for help.  Are several of the frontends for SWORD
not capable of using Sword 1.6.x?  I came to this hypothesis
because my translation requires NRSV versification and I used the
most current sword to make it.


As far as I know, any frontends based on JSword (e.g. Alkitab, 
BibleDesktop, FireBible, AndBible) will not be able to support other 
versifications.


As for the other applications, using Sword 1.6.x does not necessarily 
imply that other versifications are well supported.  I know for both 
BPBible and Xiphos that only the KJV versification is supported.  
While books with other versifications are able to be installed and 
opened, they will not go to the correct references.


Jon
Bibletime (http://www.bibletime.info/) works well with the Leningrad 
versification. You might try testing there.


Daniel

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Sword 1.6.x and various frontends

[David (Mailing List Addy)]

On Tuesday, May 24, 2011 08:24:50 AM Daniel Owens wrote:
> Bibletime (http://www.bibletime.info/) works well with the Leningrad 
> versification. You might try testing there.

It seems to work well with others too. I have the blank place holder 
versification modules and at least the book order is correct for the BHS 
(Hebrew OT cannon)

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Sword 1.6.x and various frontends

[Chris Little]

Since the NRSV varies from the KJV by exactly 2 verses, I would recommend just 
switching to KJV in osis2mod.
--Chris

On May 24, 2011, at 9:11, Luke Schroeder  wrote:

> I'm slowly but surely working on getting our translation's electronic bible 
> published.
> I can only install the file into Xiphos when I have it unzipped.  It installs 
> into BPBible Porteable fine from the Zip file.
> I cannot install it at all into Alkitab or Bibledesktop.
> XULrunner recognizes the file I installed from Xiphos.  Alkitab and 
> Bibledesktop do not.
> After several hours of trying to figure this out, I decided I would go here 
> for help.  Are several of the frontends for SWORD not capable of using Sword 
> 1.6.x?  I came to this hypothesis because my translation requires NRSV 
> versification and I used the most current sword to make it.
> 
> These are the steps I took:
> - I exported from Paratext to OSIS.
> - I used the most current OSIS2Mod.
> - I configured it to use NRSV's versification and rawtext
> - I manually created .config file
> - I manually setup a zip file to work with this.
> 
> Please give me any tips I might be missing here.  I need to send the file on 
> to my boss.
> 
> Blessings,
> Luke
> 
> 
> 
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Sword 1.6.x and various frontends

[Luke Schroeder]

It is very informative to know that it is only 2 verses.  That would 
give good reason to switch to KJV versification for Sword modules.  Also 
thanks for the info especially on java based front-ends.  XulSword and 
Xiphos are installing it and gets the versification correct, expect for 
the header gets lost for Revelations 12.  I don't know why that 
happened.  BPBible installs it, keeps the right headings, but messes up 
the versification.  Finally, it still is a bit frustrating that even 
using KJV versification the java based front-ends don't recognize the 
Bible mod I made using the latest osis2mod where the osis was derived 
from Paratext export.


Overall a big thanks to all of you for the numerous replies given.

Luke

On 5/25/2011 2:48 AM, Chris Little wrote:

Since the NRSV varies from the KJV by exactly 2 verses, I would recommend just 
switching to KJV in osis2mod.
--Chris

On May 24, 2011, at 9:11, Luke Schroeder  wrote:


I'm slowly but surely working on getting our translation's electronic bible 
published.
I can only install the file into Xiphos when I have it unzipped.  It installs 
into BPBible Porteable fine from the Zip file.
I cannot install it at all into Alkitab or Bibledesktop.
XULrunner recognizes the file I installed from Xiphos.  Alkitab and 
Bibledesktop do not.
After several hours of trying to figure this out, I decided I would go here for 
help.  Are several of the frontends for SWORD not capable of using Sword 1.6.x? 
 I came to this hypothesis because my translation requires NRSV versification 
and I used the most current sword to make it.

These are the steps I took:
- I exported from Paratext to OSIS.
- I used the most current OSIS2Mod.
- I configured it to use NRSV's versification and rawtext
- I manually created .config file
- I manually setup a zip file to work with this.

Please give me any tips I might be missing here.  I need to send the file on to 
my boss.

Blessings,
Luke



___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

.



___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Sword 1.6.x and various frontends

[Jonathan Morgan]

Hi Luke,

On Wed, May 25, 2011 at 10:23 AM, Luke Schroeder  wrote:

> It is very informative to know that it is only 2 verses.  That would give
> good reason to switch to KJV versification for Sword modules.  Also thanks
> for the info especially on java based front-ends.  XulSword and Xiphos are
> installing it and gets the versification correct, expect for the header gets
> lost for Revelations 12.  I don't know why that happened.  BPBible installs
> it, keeps the right headings, but messes up the versification.


It looks like Revelation 12 is one of the two places KJV and NRSV differ, so
presumably Xiphos/XULRunner is doing something with the versification that
means the header is lost.

>From memory, BPBible would always assume KJV versification is used (an
assumption which predated Sword 1.6.x).  Just out of curiousity, is
versification in BPBible correct up until 3 John? (which I think is the
second place the versifications differ)

Jon

Finally, it still is a bit frustrating that even using KJV versification the
> java based front-ends don't recognize the Bible mod I made using the latest
> osis2mod where the osis was derived from Paratext export.
>
> Overall a big thanks to all of you for the numerous replies given.
>
> Luke
>
>
> On 5/25/2011 2:48 AM, Chris Little wrote:
>
>> Since the NRSV varies from the KJV by exactly 2 verses, I would recommend
>> just switching to KJV in osis2mod.
>> --Chris
>>
>> On May 24, 2011, at 9:11, Luke Schroeder  wrote:
>>
>>  I'm slowly but surely working on getting our translation's electronic
>>> bible published.
>>> I can only install the file into Xiphos when I have it unzipped.  It
>>> installs into BPBible Porteable fine from the Zip file.
>>> I cannot install it at all into Alkitab or Bibledesktop.
>>> XULrunner recognizes the file I installed from Xiphos.  Alkitab and
>>> Bibledesktop do not.
>>> After several hours of trying to figure this out, I decided I would go
>>> here for help.  Are several of the frontends for SWORD not capable of using
>>> Sword 1.6.x?  I came to this hypothesis because my translation requires NRSV
>>> versification and I used the most current sword to make it.
>>>
>>> These are the steps I took:
>>> - I exported from Paratext to OSIS.
>>> - I used the most current OSIS2Mod.
>>> - I configured it to use NRSV's versification and rawtext
>>> - I manually created .config file
>>> - I manually setup a zip file to work with this.
>>>
>>> Please give me any tips I might be missing here.  I need to send the file
>>> on to my boss.
>>>
>>> Blessings,
>>> Luke
>>>
>>>
>>>
>>> ___
>>> sword-devel mailing list: sword-devel@crosswire.org
>>> http://www.crosswire.org/mailman/listinfo/sword-devel
>>> Instructions to unsubscribe/change your settings at above page
>>>
>> .
>>
>>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Sword 1.6.x and various frontends

[Konstantin Maslyuk]

> It is very informative to know that it is only 2 verses.

I would only add that NRSV:Rev.12.18-Rev.13.1 == KJV:Rev.13.1 afaik.


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page