Hi Troy,
On Mon, Feb 13, 2012 at 3:19 AM, scribe...@gmail.com
scr...@crosswire.orgwrote:
Thanks for delineating the discussion, DM.
I would certainly be in favor of discussing the possible enhancement to
our filters (or import tools) for providing language span tags around
segments of
On 11.2.2012 23:32, Jaak Ristioja wrote:
There's even one dating October 23, 2006. Twice I've written about
this issue in this mailing list wishing that they'd add news about
new BibleTime releases... but no avail. I guess they are not kidding.
:(
And that Android thing? If you want to find on
Hi Matej,
On Mon, Feb 13, 2012 at 10:02 PM, Matej Cepl mc...@redhat.com wrote:
On 11.2.2012 23:32, Jaak Ristioja wrote:
There's even one dating October 23, 2006. Twice I've written about
this issue in this mailing list wishing that they'd add news about
new BibleTime releases... but no
Which is preferred in OSIS Bibles for the two main testament divisions?
div type=bookGroup ... /div
or
div type=x-testament ... /div
The former is exemplified in http://crosswire.org/wiki/OSIS_Bibles#Body
The latter is exemplified in
http://crosswire.org/wiki/OSIS_Tutorial#Text_Divisions
IMHO, there are two separate issues here.
1) Appropriate markers for a verse.
2) Lossiness of information in the construction of an OSIS Bible module.
I'll answer the first:
As you noted it is important for the verse markers to represent the range. (In
the case of JSword it is even more
On 2/13/2012 6:13 AM, David Haslam wrote:
Which is preferred in OSIS Bibles for the two main testament divisions?
bookGroup is real OSIS (defined by the schema). x-testament isn't and
shouldn't be used. It won't cause problems to use x-testament, but if
you don't want to follow a standard,
Hi DM,
Your reply is most helpful.
The point about the size of the range is a good one.
cf. The largest range I've come across to date is 12-83 in the Falam
version from Myanmar Bibles.
verse sID=Num.7.12-Num.7.83 n=12-83 osisID=Num.7.12 Num.7.13 Num.7.14
Num.7.15 Num.7.16 Num.7.17 Num.7.18
That being the case, it prompts the question,
Why does mod2osis use type=x-testament ?
i.e. when processing a module most probably made using imp2vs
David
--
View this message in context:
On 02/13/2012 01:16 PM, David Haslam wrote:
That being the case, it prompts the question,
Why does mod2osis use type=x-testament ?
I'm not really sure what the utility of mod2osis is at all. The
transforms of ThML and GBF to OSIS are very incomplete. It is best when
processing an OSIS module.
On Mon, Feb 13, 2012 at 12:36 PM, DM Smith dmsm...@crosswire.org wrote:
On 02/13/2012 01:16 PM, David Haslam wrote:
That being the case, it prompts the question,
Why does mod2osis use type=x-testament ?
I'm not really sure what the utility of mod2osis is at all. The transforms
of ThML and
Greg,
Please don't say you were ignored. I certainly didn't ignore you.
Troy
On 02/13/2012 07:51 PM, Greg Hellings wrote:
On Mon, Feb 13, 2012 at 12:36 PM, DM Smithdmsm...@crosswire.org wrote:
On 02/13/2012 01:16 PM, David Haslam wrote:
That being the case, it prompts the question,
Why
On Mon, Feb 13, 2012 at 1:54 PM, Troy A. Griffitts scr...@crosswire.org wrote:
Greg,
Please don't say you were ignored. I certainly didn't ignore you.
If you gave me write permissions to mod2osis.cpp then it escaped me. I
remember us talking about my rewrite to use non-for loops as well as
The issues, if I can remember correctly, are deeper than the utility
mod2osis, and adding lots of checks in mod2osis to account for all the
other issues is only putting a bandaide on the problem.
mod2osis should be a very simply utility. It's logic should be:
set output format to OSIS
grab
On Mon, Feb 13, 2012 at 3:08 PM, Troy A. Griffitts scr...@crosswire.org wrote:
The issues, if I can remember correctly, are deeper than the utility
mod2osis, and adding lots of checks in mod2osis to account for all the other
issues is only putting a bandaide on the problem.
mod2osis should be
For anyone who likes to cross-build from Linux into Windows (c'mon, I
know you all love it...) I have added a pair of toolchain files to the
engine which will work with either the MinGW packages I specifically
built for SWORD support in Ubuntu or with SuSE's toolchain. It also
works building with
On 2/13/2012 10:16 AM, David Haslam wrote:
That being the case, it prompts the question,
Why does mod2osis use type=x-testament ?
Use of x-testament indicates that the associated code originates from
the period before the adoption of the bookGroup type by OSIS.
--Chris
16 matches
Mail list logo
