Title: signature
|
My apologies, Chris. I did indeed
confuse usfm2osis.py with usfm2osis.pl. I have not tested the
former.
I'm pleased that a better USFM to OSIS option is being worked on.
Haiola currently supports all USFM tags in normal "reader's
edition" Bible translations. It does not yet support all "study
Bible" and "peripheral" markup, primarily because it is not yet
clear how that should best be represented in the output formats.
Haiola generates OSIS that validates with the OSIS schema, as long
as the USFM/USFX input is well formed. It only varies from OSIS
best practices in minor ways that should not affect display in
Sword front ends at all. I call it "Modified OSIS" instead of
"OSIS" just as an acknowledgement that there is a little
deviation, there. So far, the only problem I have heard of in
using Haiola output to generate Sword modules was that some front
ends incorrectly display OSIS metadata as part of the first Book
of the Bible. That is apparently a front end issue, and not an
OSIS compliance or Haiola issue.
On 05/07/2013 11:18 AM, Chris Little wrote:
On
05/07/2013 11:20 AM, Kahunapule Michael Johnson wrote:
On 05/07/2013 02:18 AM, David Haslam
wrote:
Apart from Chris, has anyone else done
any testing on his Python script
usfm2osis.py ?
Seehttp://crosswire.org/wiki/Converting_SFM_Bibles_to_OSIS#usfm2osis.py
Yes. I found that it works for a small subset of USFM, and
produces
proper OSIS fragments for those files that use only those tags.
For
support of a broader range of USFM tags, see http://haiola.org.
That has
source in C# instead of Python.
I'm not sure if this was trollbait (in which case, sorry all for
feeding the troll) or genuine ignorance, but you don't know what
you're talking about. Maybe you're thinking of usfm2osis.pl, which
is definitely less capable, though it hardly only 'works for a
small subset of USFM'. (So, I'm leaning towards trollbait.)
usfm2osis.py handles the full set of USFM tags (excepting perhaps
any that were added within the last year). As such, I would
estimate that usfm2osis.py supports more USFM tags than does
Haiola. The fact you claim it supports a 'broader range' suggests
that it does not support all USFM tags, and thus falls short of
usfm2osis.py's support.
On top of this, usfm2osis.py actually targets the OSIS schema and
best practices, rather than a private non-standard derivative.
And in general, anyone interested in converting USFM to OSIS for
use with Sword ought really to employ usfm2osis.py since it's the
only supported pathway for USFM->OSIS->Sword, inasmuch as
its author has a fairly close connection with Sword and regularly
commits stuff to Sword filters and whatnot. I definitely will not
make the least effort to accommodate any non-standard output from
converters other than usfm2osis.py.
--Chris
_______________________________________________
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
--
Aloha,
Michael Johnson
mljohnson.org
1215 S KIHEI RD STE O # 728
KIHEI HI 96745-5278
USA
Phone: +1 808-333-6921
Skype: kahunapule
|
_______________________________________________
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
