<br>Our project, the Finnish OSIS Bible, seems to be very much an on-off project. Now we're back in the "on" state and getting quite close to the finish line. A few questions again, this time mostly related to validity / validation.<div>
<br></div><div><br></div><div>1) What XML validators (online or for Windows, preferably free) are you using for OSIS? I've used <a href="http://www.validome.org/xml/validate/">http://www.validome.org/xml/validate/</a>, but it chokes on larger files - and my bible.xml is about 8 Mb :). If I split the file in smaller chunks, it does work.</div>
<div><br></div><div><br></div><div>2) The Durusau OSIS User Manual doesn't give any directions for specifying the doctype or charset of the documents. And at least the <a href="http://w3.org">w3.org</a> validator refuses to validate the file without them. How do I do that?</div>
<div><br></div><div><br></div><div>3) How should I code en or em dashes in OSIS? The (for an HTML expert) obvious solutions, &ndash; and &mdash; seem to be HTML specific and invalid in XML. Or at least I this get error message from the validator:</div>
"Entity 'ndash' was referenced, but not declared"<div>I'd like to be able to use some code or entity instead of an actual dash characters (– or —), at least in some places, since we have two different semantics for the dashes and I'd like to keep them separate in the code.</div>
<div><br></div><div><br></div><div>4) Finally, a question not related to validation. In our translation, there are two paragraphs that span over chapter borders. In those places, the translation committee requires an inline chapter number instead of one that starts a new line (or paragraph). Obviously, this can't be handled by regular OSIS, since it would result in something like this:</div>
<div><br></div><div><chapter></div><div> ...</div><div> <p></div><div> ...</div><div></chapter></div><div><br></div><div><chapter></div><div> ...</div><div> </p></div><div> ...</div><div>
</chapter></div><div><br></div><div>which is of course invalid.</div><div><br></div><div>How would you suggest that an exception like this should be coded? Add some custom type attribute value to indicate special handling in layout?</div>
<div><br></div><div>Thanks again,</div><div><br></div><div>Markku</div>