[sword-devel] BPBible's handling of alternative versification

2011-05-26 Thread Luke Schroeder

Hey Jon,
I like BPBible a lot!  The portability of it is really nice.  The 
entire Bible is correct in BPBible until 3 John.  3 John is correct as 
well, but the last verse is left off.  The last verse is then displayed 
at the beginning of Jude before the book introduction.  The first 
heading becomes verse one and all of the verses are off by one verse.  
After Revelation 12 the verses are all off by two.  Hope that helps.


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] Sword 1.6.x and various frontends

2011-05-24 Thread 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

2011-05-24 Thread 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 Schroederl...@motimail.com  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] MDF/SFM Dictionary Import into Sword Format

2011-04-17 Thread Luke Schroeder
Does anyone with a basic knowledge of programming see any merit in the 
following idea?  Make a script that takes basic components of a 
dictionary and formats it alphabetically into the sword imp format.  The 
imp format being as follows:


$$$word in another language
Definition or gloss of word immediately below.

The dictionary format being the standard used by Bible translators, 
called MDF (Manual for Dictionary Formatting?) and adapted in the SIL's 
program Fieldworks.  My idea of a script would be to allow the user to 
input the backslash codes into the script for the word, sense number, 
part of speech, definition, example sentence, example sentence 
translated.  In our dictionary these codes would be: \lc, \sn, \ps, \ge, 
\xv, \xe but in others dictionaries they would want the ability to adapt 
the backslash codes a little since often Fieldworks gives backslash 
codes that include the language name.  The script would then output a 
file in imp format.  The file would look like this:

$$$Word
[Part of speech] [Definition] (1st sense of word)

[Example Sentence]
[Example Sentence translation]

[Part of speech] [Definition] (2nd sense of word

[Example Sentence]
[Example Sentence translation]
etc.

It seems to me like this is very basic programming.  It also seems to me 
that if someone really go into the project they could do a lot more than 
what I just described.  Finally I find this beneficial, because most of 
the Bible translation teams for minority languages are working on 
dictionaries at the same time.  For people like the group I work with, 
the dictionary is valued more than the Bible.  It is easy to get the 
Bibles into Sword format.  If this script were made it would be easy to 
get dictionaries into sword format (at least in their most basic form).  
Having the two distributed together allows interaction between both 
works.  It helps younger people in the language understand the deeper 
words of their language.


Any programmers out their interested?

Sincerely yours,
Luke S.





___
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] Help with versification

2011-03-28 Thread Luke Schroeder
My wife and I are team members of a minority Bible translation that we 
have received permission to proceed with the final stages of preparing a 
SWORD module for and a GoBible module.  I don't completely understand 
how versification works.  In the Sword module things work pretty well.  
Our translation of Matthew 1 has verse numberings that go like this: 1, 
2-6, 7-11, 12-16, 17, 18, 19, 20, 21, 22, 23, 24, 25.  In Sword it is 
currently displayed like this: 1, 2, 7, 12, 17, 18, etc.  It would be 
preferable if I could get it to display like the first set, but that 
isn't so big of a problem.


However in GoBible I have a major problem because it displays like this: 
1,2 (represents 2-6), 3 (represents 7-11), 4 (represents 12-16), 5 (17), 
6 (18), and so on.


Did I make myself clear?  Is there anything I can do to keep the GoBible 
looking pretty but not have people look for a certain verse reference 
and find out that it is several verses off because of how we have 
combined some verses due to translation practice?


Any help would be appreciated,
Thanks

___
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