On Oct 28, 2009, at 12:04 PM, <johndu...@cgcf.net> wrote:
Hi Daniel,
Yes, it works even using a relative path if only one file is
specified but not the *.sfm.
Expansion of * is something that the os needs to do. I don't know if
or how Windows does it.
It is interesting that an unrecognised character is seen at the
start of the file, which appears as a square box in front of (or
here on top of) the first backslash.
This sounds like a BOM (byte order mark). FEFF, I think. It can be
deleted if the file is utf-8.
It also keeps the \id as in the extract below, but misses the book
div and all book abbreviations in the verseIDs.
From USFM2osis.pl for single book of Psalms in Windows:
</header>
\id PSA
<title type="main">Leabhar na SALM</title>
<div type="majorSection">
<title>An Chéad Leabhar</title>
<chapter sID=".1" osisID=".1"/>
<div type="section">
<title>Fíorshonas</title>
<lg>
<l level="1">
<verse sID=".1.1" osisID=".1.1"/>
Is aoibhinn don fhear nach...
From USFM2osis.pl in Linux Psalms extract from whole Bible (Note no
poetry markup was present when this was done, as well as combined
titles):
<div type="book" osisID="Ps">
<title short="Leabhar na SALM"/>
<div>
<title type="main">Leabhar na SALM</title>
<chapter sID="Ps.1" osisID="Ps.1" n="1"/>
</div>
<div type="section" canonical="true">
<title level="1">An Chéad Leabhar -- Fíorshonas</title>
<verse sID="Ps.1.1" osisID="Ps.1.1"/>
<p> Is aoibhinn don fhear nach...
In the process, I've seen on individual files that USFM2osis.pl does
handle poetry as well as paragraph markup. If it handled the
verseIDs correctly, I'd be tempted to do each Bible book separately
and then try to put them all together into a single osis file.
Alternatively, since I'm happy with the USFM content now that I've
got both the paragraph and poetry markup in place, as well as
headings separated out into different levels, do you think that
you'd have time to compile it again in Linux?
Thanks
John Duffy
When I have used usfm2osis.pl successfully it has always been in
Linux.
I'd be willing to bet that Chris knows the answer to this one, but the
problem is not the USFM files but how usfm2osis.pl grabs the input
from
them. It is possible to process one file if you give an argument
with an
absolute path. However, if you use wildcards like *.sfm, it doesn't
work. I don't know why. Again, I'm guessing Chris knows how to do
this,
but I've never figured it out. I've just used Linux.
Daniel
_______________________________________________
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 mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
