search

lukeme / gobible

Automatically exported from code.google.com/p/gobible
1 stars 0 forks source link

Enhance GoBibleCreator to make use of chapter and verse tag values #92

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Up to version 2.4.0, GoBibleCreator does not make any use of the numerical
values of chapter and verse USFM tags or XML markup. It merely assumes that
all verses within a chapter are numbered consecutively.

It is this that causes all the problems for missing verses, and verse
ranges. It would also cause a problem for a book with a whole chapter missing.

GoBibleCreator should be further developed so as to make proper use of
these values.

Until GoBibleCore can cope with verse ranges, a workaround for these will
still be needed for these and for missing verses. Yet this could be
automated, by specifying a dummy text to appear in missing verses, or those
dummy verses that follow where the text for a verse range has been assigned
to the first verse number.

Tackling this issue would be a significant boost to Bible translation &
Bible publishing agencies desirous of using full automation with
GoBibleCreator.

Original issue reported on code.google.com by DFH...@gmail.com on 2 Jan 2010 at 12:52

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
With us on the verge of the 2.4.0 release, I would prefer to see us put out 
that 
version before starting a task of this level / complexity.

Original comment by dhinton...@gmail.com on 31 Mar 2010 at 5:15

GoogleCodeExporter commented 8 years ago 
I agree with this decision.

Original comment by DFH...@gmail.com on 31 Mar 2010 at 5:21

GoogleCodeExporter commented 8 years ago 
This has to get done.  It is stopping Bible translations from distributing on 
cell phones.  THIS IS A BIG BIG PROBLEM! As far as I know it was not yet 
accomplished.  At least the current GoBibleCreator doesn't fix it.  Where can I 
find a work around?

Original comment by dcoschro...@gmail.com on 19 Mar 2011 at 10:23

GoogleCodeExporter commented 8 years ago 
It is on the list of improvements to be tackled by our currently active 
programmer.

Workaround - manual edits to a copy of the source text, prompted by analysis of 
the versification issues. The latter is easiest when the source text is USFM, 
as one can then use the GoBibleCreator USFM Preprocessor utility developed by 
geodirk.

David

Original comment by DFH...@gmail.com on 20 Mar 2011 at 10:09

GoogleCodeExporter commented 8 years ago 
There is a further complication arising from some translations. Split verses!!
The verse tags end up as non-numeric.

Example: (Ambonese Malay)

\v 19a Tarus, dia makang la jadi kuat kombali.
\v 19b Saulus tinggal deng orang-orang yang iko Yesus di kota Damsik kurang 
labe dua tiga hari bagitu.

Ideally, these should be combined into a single verse 19.

A complication arises when there other tags in between parts a & b of the verse.
The above example actually has:

\v 19a Tarus, dia makang la jadi kuat kombali.
\s1 Saulus kasi tau Kabar Bae soal Yesus par orang-orang di Damsik
\sr 9:19b-25
\p
\v 19b Saulus tinggal deng orang-orang yang iko Yesus di kota Damsik kurang 
labe dua tiga hari bagitu.

Original comment by DFH...@gmail.com on 26 Jul 2012 at 3:58