Re: [be] Multiple Verse USFM problem in export to SWORD

[Teus Benschop]

Somebody said that the GoBibleCreator takes usfm code to convert it to
its own dialect of OSIS, but I don't know whether that can solve your
problem.

As far as Bibledit is concerned, the newest version in the git
repository has now two says of creating a sword module. It produces the
OSIS file in the user's home directory. If that OSIS file is not
according to the OSIS standard, feel free to submit a bug report against
the bibledit package.

If the OSIS so formed is fine, then the bug may be in the sword related
programs.

I tried to export Mat 1:1-2 to BibleTime, and indeed, as you said, the
second verse is blank, and everything is in the first one.

If nothing helps, temporarary changing the verses from \v 1-2 to \v 1
<text> \v 2 <text> may help but of course could be a lot of work.

Teus.


On Wed, 2009-03-11 at 14:53 +0800, Luke & Ruth Schroeder wrote:
> I have had this problem with taking USFM to SWORD as well as taking USFM 
> to GoBible and was wondering if anyone would know of an immediate 
> solution or if the programs have to be updated.
> 
> Standard format in both translation teams I'm connected with for the 
> first verse of a chapter is: \v 1
> 
> Some translation issues require that two verses be translated into one 
> sentence and therefore the translation must within the text label it 1-3 
> etc.
> Standard format in both translation teams projects I'm connected with 
> for verse 1-3 being translated is as follows
> \v 1-3
> 
> My problem is that this apparently is not recognized. So in my wife's 
> translation language the original translator combined the genealogies of 
> Matthew 1 like this. When Matthew 1:2-6 are combined, then SWORD leaves 
> verses 3-6 empty instead of noticing that they were combined in from 
> verse 2 until 6.
> 
> Anyone have any solutions?  Is there better coding for USFM or is there 
> a solution that doesn't involve program changes, but changes on my side 
> of things.
> 
> Any expertise would be appreciated.
> Thanks,
> Luke
> 
> 
>