On 03/03/2012 09:55 AM, Matěj Cepl wrote: > On 3.3.2012 20:38, Kahunapule Michael Johnson wrote: >> Bible formatting that were not shared by my good friends, the Bible >> translators. That means that either the Bible formatting has to > > Tell me about. What I am doing is converting from the document actually > created as a product of translation, which was actually used (I wonder how) > in producing printed Bibles. I have been blessed by the fact that it is XML. > I have been less blessed by it being very obviously completely non-designed > scheme created as need happened (XML element <amacron/> FTW!; and that's one > of around twenty of similar elements). It has not only milestoned verses > (which seems to be common), but also milestoned paragraphs > (which apparently is not proper OSIS).
That might be easier to convert to USFM first, then from USFM to USFX or USX, then to whatever you need, like Sword OSIS, because in USFM, paragraphs, titles, chapters, and verses are all milestones. Milestones that should be characters can be converted to Unicode characters. >> I applaud any effort to directly support USFM (or an equivalent XML >> format like USX) in any component of SWORD, because that is where the >> majority of minority-language translations are. > > Hmm, interesting. Is there a quality usfx2mod program? Not yet, but I'm seriously contemplating making one... or at least usfx2osis, which could feed into usfx2mod. > Should I switch from OSIS to USFX? I would, if I were doing what you are doing. Others on this list probably would not. OSIS is hard to generate, at least for me. Apparently, I'm not unique in that position, because I've never seen a proper USFM to OSIS converter that actually handles all real world cases, yet. Maybe I'm crazy thinking I can be the first one to actually pull it off in such a way that it works for all of the projects I have queued up, but it isn't the craziest thing I've ever tried. I think it will work if osis2mod is coded to match http://crosswire.org/wiki/OSIS_Bibles and if the front ends can handle the resulting output. It will be an interesting stress test, if nothing else. > I really don't want to work on non-XML format given I have XML sources and > XSLT scripts to work on it. I understand. >> except the emergence of OXES (and attempt to make OSIS more >> practical) > > Where does it grow? OXES is described at http://code.google.com/p/oxes/. It is supported by SIL Translation Editor for import/export. You can pull a USX Relax NG schema from https://bitbucket.org/paratext/dblvalidation if you like. USX and USFM are supported by Paratext (http://paratext.ubs-translations.org/), a non-free program with strict distribution limits. USFM is supported by Bibledit (http://Bibledit.org), an open source project. USFM and USFX are supported by Haiola (https://code.google.com/p/haiola/) and WordSend (http://eBible.org/wordsend/). WordSend needs some updating, and that will come in the form of integration into Haiola, which is on the verge of its initial release. Shalom, Michael _______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
