<div dir="ltr">H<div class="gmail_default" style="font-size:small;display:inline">i friends,</div><div><div class="gmail_default" style="font-size:small;display:inline"><br></div></div><div><div class="gmail_default" style="font-size:small;display:inline">
Thank you for the input.</div></div><div><div class="gmail_default" style="font-size:small;display:inline"><br></div></div><div><div class="gmail_default" style="font-size:small;display:inline">I mentioned about basic input consisting of \id, \p, and \v markers only, but did not mention that the \c marker is there too. Thank you Michael for pointing that out.</div>
</div><div><div class="gmail_default" style="font-size:small;display:inline"><br></div></div><div><div class="gmail_default" style="font-size:small">On my workstation, it will now download the newest version of the Python script every night, and then integrate it into bibledit-web, so that the software always has the newest version of the Python script. It's part of the chain to product Sword modules from bibledit-web. Thank you David for the suggestion.</div>
<div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">I tried to reproduce the bug about unhandled USFM tags, and am now only getting "Unhandled USFM tags: \id (1 total)" in a sample situation where all the 66 books of the Bible are lumped together into one USFM file, so that this one file has many \id ABC tags. But when leaving each book in one file, and converting them like "python usfm2osis.py bible -r -x -o bible.xml 01_Genesis.usfm 02_Exodus.usfm ...", it works fine. Thank you Chris, for leading me to look deeper into it.</div>
<div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">Regards,</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">
Teus.</div><div class="gmail_default" style="font-size:small"><br></div></div></div>