<div dir="ltr"><div dir="ltr"><div dir="ltr">In general I've found the osisCore.2.1.1.xsd file to be incompatible with claims made in the OSIS 2.1 User Manual:</div><div dir="ltr"><a href="https://www.crosswire.org/osis/OSIS%202.1.1%20User%20Manual%2006March2006.pdf">https://www.crosswire.org/osis/OSIS%202.1.1%20User%20Manual%2006March2006.pdf</a><br></div><div dir="ltr"><br></div><div>It was something of an epiphany to find that people had been making incremental improvements to the osisCore.2.1.1.xsd file:</div><div><a href="https://wiki.crosswire.org/OSIS_211_CR">https://wiki.crosswire.org/OSIS_211_CR</a> <br></div><div><br></div><div>To many module-makers issues with the osisCore.2.1.1.xsd file itself are not obvious.</div><div><br>While the copy called <a rel="nofollow" class="external gmail-text" href="http://www.crosswire.org/~dmsmith/osis/osisCore.2.1.1-cw-latest.xsd" style="text-decoration-line:none;color:rgb(102,51,102);padding-right:13px;font-family:sans-serif;font-size:14px">osisCore.2.1.1-cw-latest.xsd</a>solved many of the most egregious issues, there still appears to be as of yet unidentified OsisCore issues in-congruent with with the User Manual. Peter, is it possible the issue you describe is one such example?</div><div>Regardless, there should likely be, at some point in the future, a commitment to a review/refresh/update of osisCore itself subject of course to project priority. </div><div><br></div><div dir="ltr"><div><br></div></div></div></div><br><div class="gmail_quote"><div dir="ltr">On Thu, Sep 13, 2018 at 10:02 AM David Haslam <<a href="mailto:dfhdfh@protonmail.com">dfhdfh@protonmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>Is the Uighur translation being maintained using ParaTExt ?</div>
<div>
<br>
</div>
<div>If so, what was used for the conversion from USFM to OSIS?</div>
<div>
<br>
</div>
<div>IMHO, to maintain the controlled version of a Bible translation in OSIS XML would be terribly unwieldy, so it’s nigh on certain that the user space x-prefix attributes (etc) must result from a script. </div>
<div>
<br>
</div>
<div>They don’t come from any of the Python scripts we are familiar with, such as adyeths u2o.py</div>
<div>
<br>
</div>
<div>Best regards,</div>
<div>
<br>
</div>
<div>David</div>
<div>
<br>
</div>
<div id="m_-2002176181782745536protonmail_mobile_signature_block">Sent from ProtonMail Mobile</div>
<div>
<br>
<div>
<div>
<br>
</div>On Thu, Sep 13, 2018 at 14:45, Peter Von Kaehne <<a href="mailto:refdoc@gmx.net" target="_blank">refdoc@gmx.net</a>> wrote:</div>
<blockquote class="m_-2002176181782745536protonmail_quote" type="cite">> Von: "David Haslam" <<a href="mailto:dfhdfh@protonmail.com" target="_blank">dfhdfh@protonmail.com</a>>
<br>> What does the Uighur translation team envisage as the practical use of osisRef in the OSIS example given?
<br>> What would we expect SWORD to do with it?
<br>
<br>Reading the OSIS source, my best reading of the purpose of the marker is to provide an alternative verse start and end reference
<br>"This is Romans 14:23, but you could also have it as Romans 16:26" or some such. I think the source is convoluted, has too many extensions which are probably by and large irrelevant - but this is how I read it.
<br>
<br>What should SWORD do? Good question - maybe nothing at this moment, but always consider - we do not write modules for the current engine, but we try and encode everything and if rthere is enough demand by way of new encodings in new modules we extend
the engine to cover that. So, up to a point I am perfectly happy with having plenty codes in modules which is ignored at this moment in time. A time may well come when it becomes useful. Particularly as for many things a CSS setting is all that
is required. Not sure here.
<br>
<br>
<br>Peter
<br>
<br>> 30965 <verse osisID="Rom.14.23 Rom.14.24 Rom.14.25 Rom.14.26"
<br>> sID="Rom.14.23 Rom.14.24 Rom.14.25 Rom.14.26" type="x-vsys-
<br>> fitted"/><milestone type="x-vsys-verse-start" annotateRef="Rom.14.23"
<br>> annotateType="x-vsys-source"/>Лекин бирәр йемәкликкә шәк кәлтүрүп
<br>> туруп, йәнә шу йемәкликни йегән киши вижданиниң әйиплишигә учрайду.
<br>> Чүнки у киши өзи йегән йемәкликниң тоғра екәнлигигә ишәнч қилалмиди.
<br>> Тоғра екәнлигигә ишәнч йоқ һалда қилинған һәр қандақ иш
<br>> гунадур.</p><milestone type="x-vsys-movedto" annotateRef="Rom.16.25"
<br>> annotateType="x-vsys-source" osisRef="Rom.14.24"/><milestone type="x-
<br>> vsys-movedto" annotateRef="Rom.16.26" annotateType="x-vsys-source"
<br>> osisRef="Rom.14.25"/><milestone type="x-vsys-movedto"
<br>> annotateRef="Rom.16.27" annotateType="x-vsys-source"
<br>> osisRef="Rom.14.26"/><verse eID="Rom.14.23 Rom.14.24 Rom.14.25
<br>> Rom.14.26" type="x-vsys-fitted"/><milestone type="x-vsys-verse-end"
<br>> annotateRef="Rom.14.23" annotateType="x-vsys-source"/>
<br>
</blockquote>
</div>_______________________________________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org" target="_blank">sword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" rel="noreferrer" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page</blockquote></div>