[sword-devel] OSIS Validation
greg.hellings at gmail.com
Tue Jun 29 21:26:25 MST 2010
On Tue, Jun 29, 2010 at 8:39 PM, troypulk <troypulk at yahoo.com> wrote:
> The error lies in the mod2osis and how it renders the .xml
Actually this is not the case. Chris Little and I got to the bottom
of this over IRC today and it was actually a problem with how the
older versions of osis2mod stored the new module as they created it.
Newer versions of osis2mod do not have this bug. Chris said he was
going to upload a new version of the KJV to the Beta repository that
was imported with the newer versions of the tool. The new utility
also renders the problematic epigraphs validly.
With a properly imported module, my current version of mod2osis only
presents a single invalid point for the KJV. I have not tried other
Bibles recently, but when I was working in the past, it worked even
better on other modules, which generally have simpler markup than the
I hope to have a new patch set for mod2osis available soon that fully
supports round-tripping of OSIS-source modules, and I've also made
headway in the past on working with ThML and GBF module sources. I'll
let you know how things turn out.
> I've modified the mod2osis to reproduce a valid osis.xml using the EMTV bible but when I use it for the KJV I get the following:
> kjv.xml:33566: parser error : Opening and ending tag mismatch: chapter line 33544 and osisText
> kjv.xml:33567: parser error : Opening and ending tag mismatch: div line 33117 and osis
> kjv.xml:33567: parser error : Premature end of data in tag chapter line 33091
> kjv.xml:33567: parser error : Premature end of data in tag div line 33089
> kjv.xml:33567: parser error : Premature end of data in tag osisText line 5
> kjv.xml:33567: parser error : Premature end of data in tag osis line 3
> But when you look at the xml it appears fine.
> So I'm not seeing the title error as you are.
> As soon as I can figure out why I'm getting these error's I will be able to reproduce a valid xml using xmllint.
> OSIS and import experts,
> So I'm working on the elusive Holy Grail of dumping out valid OSIS
> from the engine into an XML file of the module. What I am currently
> getting from the engine has two parts that fail to validate as OSIS
> when I'm working with the KJV module. Namely, those Psalms that have
> pre-verse titles in the source OSIS document but have had the title
> moved into the first verse now render the title as
> <title canonical="true" subType="x-preverse" type="section">[Title text]</title>
> xmllint complains that "section" is not a valid value for the type
> attribute on a title element. I can't find any mention of
> type="section" anywhere in either the importers or the filters, so I'm
> not sure where this would be corrected. I'll keep searching, in hopes
> that it's in the filters somewhere and can be corrected. The schema
> allows for values of acrostic, chapter, continued, main, parallel,
> psalm, runningHead, scope and sub. Psalm is how they are marked in
> the source file, but somewhere along the lines they were transformed
> into section. Is this something that has been fixed in the tools
> since the release of the current version of the KJV module?
> Also, in the epistles of Paul it seems there are stray <div> elements
> which made it into verses as some type of footnote. The validator
> chokes on this, as div apparently cannot be a child of the verse
> element in OSIS 2.1.1. Is there any way these can be changed from a
> div into something that is both valid OSIS and still semantically
> correct there? Again, this is probably something that happened at
> import time and not at export time, or am I guessing wrong on that?
> sword-devel mailing list: sword-devel at crosswire.org
> Instructions to unsubscribe/change your settings at above page
More information about the sword-devel