|
Hello, David. I'm looking forward to meeting you in person, too. I think \rq ...\rq* is used in at least 2 of the 218 (as of today) Scriptures I have posted publicly, so far. Between them all, you will find that almost all of the tags at http://ubs-icap.org/chm/usfm/2.3/index.html are used, including tables. Just support them ALL, and you will be OK. If you want to leave something for last to implement, let it be study Bible content, and maybe some of the peripheral markers. I think that pretty much anything that can be in a plain reader's edition Bible is there, though, including deprecated markers like \it ...\it*. To avoid insanity and/or excessive backlogs, the conversion from USFM to Sword SHOULD be fully automatic if the input is really USFM compliant. If you give me such an automatic tool, I'll integrate it into my build process. I'll be publishing Scriptures as they are translated, reprocessing them as each book is translated at times. Work on the World English Bible and its 2 derivatives will continue at a faster pace, too. The magic key to a treasure trove of USFM files is: http://Bible.cx/tid/tid_usfm.zip, where tid is the translation ID. Normally, that is just the Ethnologue code if the reference is just to the first translation into that language in the first dialect that I encountered. Otherwise, it is followed by a dash and something to make it globally unique among my projects by including at least one letter of a dialect, translation name, or publication year. Even more valuable is: http://Bible.cx/tid/tid_usfx.zip, which contains the Scriptures in USFX format AND some XML files containing metadata that should be useful in giving proper attribution and getting the copyright notices right. So far, most of the translations are Creative Commons BY-ND-NC with additional permission to change formats (i. e. from USFM or USFX to Sword), provided that you don't change any of the text or punctuation in the process. The text and punctuation displayed must be the same as the text and punctuation displayed on the distribution web site. Note that if quotation marks are put in markup instead of text, OSIS-style, and the front end doesn't display it exactly the same as it started, that will be considered a copyright violation and treated as such. At this point, we can't risk annoying the copyright owners with such sloppiness. Exceptions to the CC BY-ND-NC license are khm and khm-h, which you shouldn't touch, yet; eng-glw, which has its own free copying license; and eng-asv, eng-kjv, eng-web, eng-webbe, & eng-webme, which are Public Domain. (Yes, I know about the Crown Patent on the KJV which doesn't expire, but which King James failed to mention digital rights in. I'll not worry about it in my home country.) http://Bible.cx also has some password-protected directories, like for the Tok Pisin (tpi) translation, that I'm still (after many years) waiting for permission to publish. The text in that directory is in much better shape than the old copy of Tok Pisin that was previously published by Crosswire, and matches the printed edition as far as I can tell. Happy coding! On 02/20/2012 10:07 AM, David F. Haslam wrote: Hi 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
