<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello, David.<br>
<br>
I'm looking forward to meeting you in person, too.<br>
<br>
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
<a class="moz-txt-link-freetext" href="http://ubs-icap.org/chm/usfm/2.3/index.html">http://ubs-icap.org/chm/usfm/2.3/index.html</a> 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*.<br>
<br>
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.<br>
<br>
The magic key to a treasure trove of USFM files is:<br>
<a class="moz-txt-link-freetext" href="http://Bible.cx/">http://Bible.cx/</a><b><i>tid</i></b>/<b><i>tid</i></b>_usfm.zip, where
<b><i>tid</i></b> 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.<br>
<br>
Even more valuable is:<br>
<a class="moz-txt-link-freetext" href="http://Bible.cx/">http://Bible.cx/</a><b><i>tid</i></b>/<b><i>tid</i></b>_usfx.zip, which
contains the Scriptures in <a href="http://eBible.org/usfx/">USFX
format</a> 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.)<br>
<br>
<a class="moz-txt-link-freetext" href="http://Bible.cx">http://Bible.cx</a> 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.<br>
<br>
Happy coding!<br>
<br>
<br>
<br>
On 02/20/2012 10:07 AM, David F. Haslam wrote:
<blockquote cite="mid:4F42A7FD.8050401@btinternet.com" type="cite">
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
Hi Michael,<br>
<br>
I was pretty certain that it was you that I was writing to, but
felt the official contact form was the right channel.<br>
<br>
Look forward to meeting you in Germany next month. I must book
flights soon before I forget and/or leave it too late.<br>
<br>
btw. This translation was the first one that I've come across
that makes use of the <b>\rq_...\rq*</b> tag.<br>
It prompted a minor improvement to Dirk Kaiser's utility. <span
class="moz-smiley-s3"><span> ;-) </span></span><br>
<br>
David<br>
<br>
On 2012-02-20 19:23, Kahunapule Michael Johnson wrote:
<blockquote cite="mid:4F429DAA.5030608@wycliffe.org" type="cite">
<meta content="text/html; charset=UTF-8"
http-equiv="Content-Type">
Fixed. Thanks.<br>
<br>
On 02/20/2012 06:21 AM, you wrote:
<blockquote cite="mid:20120220162156.25709.qmail@www.mpj.us"
type="cite">
<pre wrap=""> From: David Haslam <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="mailto:dfh@crosswire.org"><dfh@crosswire.org></a>
Translation: Southwest Tanna (nwi)
Source IP address: 109.155.169.177
Message:
Dear friends in Vanuatu,
For the Paratext/USFM files downloaded for the Southwest Tanna (nwi) translation,
in the file 64-MAT.usfm, chapter 24, the second verse has a "." after the number.
This is a USFM violation, which can cause other Bible software to crash.
It requires correcting.
Detected using <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://gbcpreprocessor.codeplex.com/">http://gbcpreprocessor.codeplex.com/</a>
David Haslam
Go Bible project leader
CrossWire Bible Society
</pre>
</blockquote>
</blockquote>
</blockquote>
<br>
</body>
</html>