Y'all:
For future reference: I have found that JEdit, with the XML addon, using
the Sword xsd, osisCore.2.1.1-cw-latest.xsd, is able to pick up OSIS
errors and report on their exact location. This process does show some
discrepancies between OSIS.pdf documentation and what the schema will
act
Thank you for your insight. It is appreciated. I'll scrutinize the XML
more closely (again). I find general many of the XML validation tools
expect small xml files not large ones. XML can be a pain to find errors
in.
On Mon, Feb 19, 2018 at 2:16 AM, ref...@gmx.net wrote:
> Thanks for confirmi
Tom - thank you for your suggestion. I had been using linux command line
tools and in windows notepad++. I had forgotten about jedit, but Ill look
at that again. Many validator tools will tell you there's an error but not
point out where it is.
Is osisCore.2.1.1-cw-latest.xsd different from os
Responding to Vince about alternate versification (av11n).
Before we'd contemplate creating a new av11n for a Spanish Bible, a lot of
detailed research would be required to show how and why this might be required.
It's the kind of work that Dominique did for (Protestant) French Bibles, as
tabled
On 2018-02-19, 14:47 GMT, David Haslam wrote:
> Before we'd contemplate creating a new av11n for a Spanish
> Bible, a lot of detailed research would be required to show
> how and why this might be required.
> It's the kind of work that Dominique did for (Protestant)
> French Bibles, as tabled in
Y'all:
One point about JEdit - with very large files, it can hang. So be
prepared to just find an error or 2, then kill the process and go again.
Tedious, but searching for a needle in a haystack is easier with a
magnet, but still not always a lot of fun.
Tom
Tom Sullivan
i...@beforgiven.in
Recommend breaking your input into files by book. Run the Osis2mod for Genesis
as before but the others w -a.
This will incrementally build a module.
Smaller files are better handled by other xml tools.
— DM Smith
From my phone. Brief. Weird autocorrections.
> On Feb 19, 2018, at 9:43 AM, A
DM:
Can you give some more info on the -a option? Normally, the complete
OSIS file will have a header, then a body. The body will be broken into
books. So when running osis2mod the first time, do we repeat the header?
Does the first segment simply end abruptly without closing tags for the
bod
Osis2mod does not care much about whether it is actually semantically valid
OSIS. Just that it is well formed OSIS.
To do this each file has to have a container element surrounding the entire
content. … should do. But you certainly can have each
book be a semantically complete OSIS document of
