<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">For what it is worth, I just looked
through the USFM standard again, and there is nothing there about
requiring or forbidding a newline as part of markup. What Paratext
actually does is to regard newline and space as equivalent
characters most of the time, although on writing out USFM it
usually (but apparently not always) starts metadata and paragraph
style markers on a new line. Thus Mike's second regular
expression, below, is more likely to work all of the time in
reading USFM input.<br>
<br>
On 12/10/2013 09:11 AM, Mike Hart wrote:<br>
</div>
<blockquote
cite="mid:1386702680.70031.YahooMailNeo@web120706.mail.ne1.yahoo.com"
type="cite">
<div style="color:#000; background-color:#fff;
font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial,
Lucida Grande, sans-serif;font-size:12pt">
<div>FYI -- item came up on another mailing list. </div>
<div><br>
</div>
<div style="color: rgb(0, 0, 0); font-size: 16px; font-family:
HelveticaNeue, 'Helvetica Neue', Helvetica, Arial, 'Lucida
Grande', sans-serif; background-color: transparent;
font-style: normal;">It appears that recently USFM tagging
completely ignores the return character in many places, and
validates only on the start of another tag. </div>
<div style="color: rgb(0, 0, 0); font-size: 16px; font-family:
HelveticaNeue, 'Helvetica Neue', Helvetica, Arial, 'Lucida
Grande', sans-serif; background-color: transparent;
font-style: normal;"><br>
</div>
<div style="color: rgb(0, 0, 0); font-size: 16px; font-family:
HelveticaNeue, 'Helvetica Neue', Helvetica, Arial, 'Lucida
Grande', sans-serif; background-color: transparent;
font-style: normal;">That is, USFM2OSIS apparently considers
something like (regex)</div>
<div style="color: rgb(0, 0, 0); font-size: 16px; font-family:
HelveticaNeue, 'Helvetica Neue', Helvetica, Arial, 'Lucida
Grande', sans-serif; background-color: transparent;
font-style: normal;"><br>
</div>
<div style="color: rgb(0, 0, 0); font-size: 16px; font-family:
HelveticaNeue, 'Helvetica Neue', Helvetica, Arial, 'Lucida
Grande', sans-serif; background-color: transparent;
font-style: normal;"><span class="Apple-tab-span"
style="white-space:pre"> </span>\\id (...)(.+$) </div>
<div style="color: rgb(0, 0, 0); font-size: 16px; font-family:
HelveticaNeue, 'Helvetica Neue', Helvetica, Arial, 'Lucida
Grande', sans-serif; background-color: transparent;
font-style: normal;"><br>
</div>
<div style="color: rgb(0, 0, 0); font-size: 16px; font-family:
HelveticaNeue, 'Helvetica Neue', Helvetica, Arial, 'Lucida
Grande', sans-serif; background-color: transparent;
font-style: normal;">to be the ID field; <span
style="background-color: transparent;">while ParaTExt USFM
now considers something more like</span></div>
<div style="color: rgb(0, 0, 0); font-size: 16px; font-family:
HelveticaNeue, 'Helvetica Neue', Helvetica, Arial, 'Lucida
Grande', sans-serif; background-color: transparent;
font-style: normal;"><br>
</div>
<div style="color: rgb(0, 0, 0); font-size: 16px; font-family:
HelveticaNeue, 'Helvetica Neue', Helvetica, Arial, 'Lucida
Grande', sans-serif; background-color: transparent;
font-style: normal;"><span style="background-color:
transparent;"><span class="Apple-tab-span"
style="white-space:pre"> </span>\\id (...)([^\]+) </span></div>
<div style="color: rgb(0, 0, 0); font-size: 16px; font-family:
HelveticaNeue, 'Helvetica Neue', Helvetica, Arial, 'Lucida
Grande', sans-serif; background-color: transparent;
font-style: normal;"><span style="background-color:
transparent;"><br>
</span></div>
<div style="color: rgb(0, 0, 0); font-size: 16px; font-family:
HelveticaNeue, 'Helvetica Neue', Helvetica, Arial, 'Lucida
Grande', sans-serif; background-color: transparent;
font-style: normal;"><span style="background-color:
transparent;">to be the ID field. </span></div>
<div style="color: rgb(0, 0, 0); font-size: 16px; font-family:
HelveticaNeue, 'Helvetica Neue', Helvetica, Arial, 'Lucida
Grande', sans-serif; background-color: transparent;
font-style: normal;"><span style="background-color:
transparent;">( \1 = machine readable Bible book ID for
import, \2= Optional human readable text explaining what the
file is.) </span><br>
</div>
<div style="color: rgb(0, 0, 0); font-size: 16px; font-family:
HelveticaNeue, 'Helvetica Neue', Helvetica, Arial, 'Lucida
Grande', sans-serif; background-color: transparent;
font-style: normal;"><span style="background-color:
transparent;"><br>
</span></div>
<div style="color: rgb(0, 0, 0); font-size: 16px; font-family:
HelveticaNeue, 'Helvetica Neue', Helvetica, Arial, 'Lucida
Grande', sans-serif; background-color: transparent;
font-style: normal;"><span style="background-color:
transparent;">Further discussion describes this
'ignore-return-trend' is appearing around other tags as
well, with chapters starting without a return after the end
of the last verse.... </span></div>
<div style="color: rgb(0, 0, 0); font-size: 16px; font-family:
HelveticaNeue, 'Helvetica Neue', Helvetica, Arial, 'Lucida
Grande', sans-serif; background-color: transparent;
font-style: normal;"><br>
</div>
<div id="divExpHdr" style="height: 47px; width: auto; position:
relative; cursor: pointer; font-family: 'Segoe UI', Helvetica,
Arial, sans-serif; font-size: 13px;"><br
class="Apple-interchange-newline">
<img moz-do-not-send="true"
src="https://outlook.tblusa.org/owa/14.3.158.1/themes/resources/clear1x1.gif"
class="csimg csimgbg sprites-hdiv-l-png" id="divDividerLeft"
style="overflow: hidden; background-image:
url(https://outlook.tblusa.org/owa/14.3.158.1/themes/base/csssprites.png);
width: 132px; height: 1px; position: absolute; top: 0px;
max-width: 50%; left: 0px; background-position: -30px
-329px;"><img moz-do-not-send="true"
src="https://outlook.tblusa.org/owa/14.3.158.1/themes/resources/clear1x1.gif"
class="csimg csimgbg sprites-hdiv-r-png"
id="divDividerRight" style="overflow: hidden;
background-image:
url(https://outlook.tblusa.org/owa/14.3.158.1/themes/base/csssprites.png);
width: 132px; height: 1px; position: absolute; top: 0px;
max-width: 50%; right: 0px; background-position: -164px
-329px;">
<div id="divSn" class="divSn divTx" style="padding: 0px 20px
0px 0px; float: left; text-overflow: ellipsis; overflow:
hidden; white-space: nowrap; position: absolute; width:
auto; left: 0px; right: 216px; bottom: 15px;"><span
id="spnSender" class="rwRRO"
_e_ondblclick="onDblClkReadRcp(event);"
_e_onclick="onClkRcp(event);"
_e_oncontextmenu="onRwCm(event);" _fjnk="1"
_dn="PTSupporters" _rt="SMTP"
_em="ptsupporters-bounces@ubs-icap.org" _ao="3"
title="ptsupporters-bounces@ubs-icap.org on behalf of
Robert_Hunt@sil.org" style="cursor: pointer; font-size:
15pt;">Robert Hunt wrote: </span></div>
</div>
<div id="divSelDisplay" class="" style="position: relative;
z-index: 0; top: -18px; padding-right: 15px; padding-bottom:
1px; font-family: 'Segoe UI', Helvetica, Arial, sans-serif;
font-size: 13px;">
<div id="divRws">
<div id="divWellTo" class="roWellRow" style="width: 710px;
margin: 2px 0px; overflow: hidden; min-width: 20em;">
<div id="divToL" class="roWellLabel pvwLabel"
style="vertical-align: top; color: rgb(102, 102, 102);
float: left; margin: 0px 6px 0px 0px; line-height: 18px;
font-weight: bold; font-size: 8.25pt; width: 72px;"><span
class="nowrap" style="white-space: nowrap;">To:</span></div>
<div class="roWellWrap" style="max-height: 5.3em;
overflow-y: auto; overflow-x: hidden; margin: 0px 10px
0px 0px; line-height: 18px; font-size: 8.25pt;">
<div id="divFieldTo" class="wellField" style="width:
auto; overflow: hidden;">
<div id="divTo" class="rwW rwWRO" style="overflow:
hidden; padding: 0px; background-color: transparent;
border: 0px none transparent; cursor: text;
word-wrap: break-word; word-break: break-all;
text-overflow: ellipsis; color: rgb(153, 153, 153);"> <span
id="spnR" _e_oncontextmenu="onRwCm(event);"
_e_ondblclick="onDblClkReadRcp(event);"
_e_onclick="onClkRcp(event);" class="rwRRO"
_ao="3" _rf="0" _rt="SMTP"
_em="ptsupporters@ubs-icap.org"
title="ptsupporters@ubs-icap.org"
_sa="ptsupporters@ubs-icap.org" _dn="Paratext
Supporters" style="color: rgb(64, 140, 217);
white-space: nowrap; cursor: pointer;">Paratext
Supporters </span></div>
</div>
</div>
</div>
</div>
<div id="divWellAttach" class="roWellRow roAttMrg"
style="width: 710px; margin: 0px 0px 2px; overflow: hidden;
min-width: 20em;">
<div id="divAttachL" class="roCatAttWellLabel pvwLabel"
style="vertical-align: middle; color: rgb(102, 102, 102);
float: left; margin: 0px 6px 0px 0px; line-height: 18px;
font-weight: bold; font-size: 8.25pt; width: 72px;">Attachments:</div>
<div class="roWellWrap rowAttMaxH" style="max-height: 5.3em;
overflow-y: auto; overflow-x: hidden; margin: 0px 10px 0px
0px; line-height: 18px; font-size: 8.25pt;">
<div id="divFieldAttach" class="wellField" style="width:
auto; overflow: hidden;">
<div id="divAtch" class="awRO" _iseventattach="1"
style="width: 622px; background-color: transparent;
border: 0px none transparent; line-height: 17px;"><span
id="spnAtmt" tabindex="-1"
_sid="RgAAAACKnVLk3KHlQb2CNmwbPdnHBwA8IP2dR8gaTbQMqHFWZgBSAAAActAZAAA8IP2dR8gaTbQMqHFWZgBSAAAVfsiSAAAJ"
_attid="BAAAAAAA" _level="3" _attname="ATT00001.txt"
_attsize="231" _fisitem="False" _protectable="0"
style="cursor: pointer;"><a moz-do-not-send="true"
class="lnkClickAtmt" id="lnkAtmt" _fallwcm="1"
href="https://outlook.tblusa.org/owa/#"
target="_blank" _e_onclick="atLnk(event, 3, 0);"
title="ATT00001.txt" style="text-decoration: none;
color: rgb(64, 140, 217);"><img
moz-do-not-send="true"
src="https://outlook.tblusa.org/owa/14.3.158.1/themes/resources/clear1x1.gif"
class="csimg csimgbg sprites-dc-txt-gif"
style="border-width: 0px; overflow: hidden;
width: 16px; height: 16px; background-image:
url(https://outlook.tblusa.org/owa/14.3.158.1/themes/base/csssprites2.png);
vertical-align: bottom; margin: 0px 2px 0px 0px;
background-position: -108px -156px;">ATT00001.txt
(231 B)</a></span></div>
</div>
</div>
</div>
<div id="divExpSubHdr" style="position: relative; height:
14px; padding-top: 7px; width: 710px;">
<div id="divSubFs" style="position: absolute; left: 0px;
right: 250px;">
<div id="divFs" style="position: absolute; left: 0px;
right: 0px; color: rgb(102, 102, 102); font-size:
7.5pt;">
<div class="divTx" style="text-overflow: ellipsis;
overflow: hidden; white-space: nowrap; position:
absolute;"> </div>
</div>
</div>
<div id="divSubSent" style="position: absolute; right: 0px;
width: 250px; text-align: right; bottom: 2px;"><span
id="spnSent" style="font-size: 7.5pt; padding: 0px 0px
0px 5px; color: rgb(102, 102, 102);">Tuesday, December
10, 2013 3:43 AM</span></div>
</div>
</div>
<div id="divBdy" class="bdyItmPrt" _fallwcm="1"
style="font-size: 16px; word-wrap: break-word; width: auto;
overflow: hidden; position: relative; top: -5px; padding: 0px
15px 15px 0px; clear: both; font-family: 'Segoe UI',
Helvetica, Arial, sans-serif;">Dear all,<br>
<br>
With increasing pressure to get Bibles and even partial
Bibles onto mobile devices these days, there is lots of
interest in converting from Paratext/USFM files to other
formats. <a moz-do-not-send="true"
href="https://outlook.tblusa.org/owa/redir.aspx?C=uF6tZoPryESH1yaE7W0snDg8eAhjydAIuniVydqnEu6X8J0zEHxq1IQZAzmiYDgcr33HTqwWsio.&URL=http%3a%2f%2fwww.crosswire.org%2findex.jsp"
target="_blank">Crosswire Bible Society</a> have the Sword
Project which has its own binary format for Bible modules
which are readable by "<a moz-do-not-send="true"
href="https://outlook.tblusa.org/owa/redir.aspx?C=uF6tZoPryESH1yaE7W0snDg8eAhjydAIuniVydqnEu6X8J0zEHxq1IQZAzmiYDgcr33HTqwWsio.&URL=http%3a%2f%2fwww.crosswire.org%2fapplications.jsp"
target="_blank">front-ends</a>" on many operating systems,
including Windows, Linux, Android, etc. However, the current
Crosswire usfm2osis.py converter chokes on the following:<br>
<div style="margin: 14pt 30pt;">\id 1TH My test version \mt2
The first letter of Paul to the<br>
\mt1 Corinthians<br>
\c 1<br>
\s Paul introduces himself<br>
\p<br>
\v 1 Hi there, I'm Paul.<br>
</div>
In reading the USFM spec, I can't find confirmation that
markers like \mt2 MUST start on a new line. The closest that I
can see is:<br>
<div style="margin: 14pt 30pt;">Most paragraph or poetic
markers (like \p, \m, \q# etc.) can be followed immediately
by<br>
a verse number (\v) on a new line.<br>
</div>
All examples, however, do show these (what I call "newline
markers") on new lines.<br>
<br>
However, I notice that the last few Paratext versions have a
tendency to pop some markers and their text up onto the end of
the previous line. I'm pretty sure that PT6 didn't do this. I
don't think this is an intentional feature, but seems to be
either a bug or some kind of weird side-effect. (It happens
often enough that I don't think the user can be blamed for it,
especially the way \c markers pop onto the previous line, but
of course because Paratext usually displays by chapter, the
user can't even see that without changing view mode.)<br>
<br>
So anyway, I have a few questions:<br>
<ol style="margin-top: 14pt; margin-bottom: 14pt;">
<li>Do you agree that these types of markers (\mt2, \c, \q1)
should/must start on a new line?</li>
<li>If so, would it be good to make that clear in the USFM
standard (or did I miss something)?<br>
</li>
<li>Is having these markers pop up to the end of the
previous line a known bug in Paratext?</li>
<li>Is there any way in Paratext to automatically fix this
in the USFM files?</li>
<li>Does the Pathway code handle files like this better than
the Crosswire converter?</li>
</ol>
<div style="margin-top: 14pt; margin-bottom: 14pt;">Thanks,<br>
Robert.</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
sword-devel mailing list: <a class="moz-txt-link-abbreviated" href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a>
<a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a>
Instructions to unsubscribe/change your settings at above page</pre>
</blockquote>
<br>
<br>
<div class="moz-signature">-- <br>
<meta http-equiv="CONTENT-TYPE" content="text/html; charset=UTF-8">
<title>signature</title>
<table border="0" cellpadding="7" cellspacing="3">
<tbody>
<tr>
</tr>
<tr>
<td><img src="cid:part7.07040704.01000100@eBible.org"></td>
<td><font color="#000000" size="4">Your partner in
electronic Bible publishing,<br>
<img src="cid:part8.05080500.05090401@eBible.org"><br>
</font></td>
</tr>
</tbody>
</table>
<table border="0" cellpadding="7" cellspacing="3">
<tbody>
<tr>
<td style="background: rgb(255, 255, 0)"><font
color="#000000"><a href="http://MLJohnson.org">MICHAEL
JOHNSON</a><br>
<b>1215 S KIHEI RD STE O # 728<br>
KIHEI HI 96753-5225</b><br>
USA<br>
<br>
Verizon Wireless Mobile: +1 <b>808-333-6921</b><br>
Skype: kahunapule or +1 719-387-7238</font>
</td>
<td style="background: rgb(0, 255, 255)"><font
color="#000000">
<a href="http://eBible.org">eBible.org</a><br>
<a href="http://MLJohnson.org">MLJohnson.org</a><br>
<a href="http://PacificBibles.org">PacificBibles.org</a><br>
<a href="http://PNGScriptures.org">PNGScriptures.org</a><br>
<a href="http://TokPlesBaibel.org">TokPlesBaibel.org</a><br>
<a href="http://VanuatuBibles.org">VanuatuBibles.org</a><br>
</font></td>
</tr>
</tbody>
</table>
</div>
</body>
</html>