<div style="font-family: Arial, sans-serif; font-size: 14px;"><br></div><div style="font-family: Arial, sans-serif; font-size: 14px;">Resending without attachment!</div>
<div style="font-family: Arial, sans-serif; font-size: 14px;" class="protonmail_signature_block">
<div class="protonmail_signature_block-user"><br></div></div><div style="font-family: Arial, sans-serif; font-size: 14px;"><div class="protonmail_quote">
On Saturday, July 26th, 2025 at 11:07 AM, David Haslam <dfhdfh@protonmail.com> wrote:<br>
<blockquote class="protonmail_quote" type="cite">
<div style="font-family: Arial, sans-serif; font-size: 14px;"><p>Thanks Dom,</p><p>It would seem therefore that the "ampersand issue" is not a bug in how <b>libsword</b> processes module content for <b>output</b>!<br>
<br>
I just did the following experiment...</p><p></p><ol data-editing-info="{"orderedStyleType":1,"unorderedStyleType":1}" style="margin-top: 0px; margin-bottom: 0px;" data-listchain="__List_Chain_200"><li style="list-style-type: "1. ";">Used <b>mod2imp</b> to output the latest update of <b>FreGeneve1669</b> version 2.0 to a text file.</li><li style="list-style-type: "2. ";">Used <b>Notepad++</b> to insert a space after each <b>&</b> where it was missing.<br>(except where the ampersand was wrapped within a <b>transChange</b> element)</li><li style="list-style-type: "3. ";">Used <b>imp2vs</b> to create eXperimental module <b>FreGeneve1669X</b></li><li style="list-style-type: "4. ";">Used <b>mod2imp</b> to output the latter to another text file.</li><li style="list-style-type: "5. ";">Compared the two raw imp txt files. There are identical.</li></ol><div><br></div><div>Hence the long established "round trip" assertion (<b>mod2imp </b>=> <b>imp2vs</b>) is still valid!<br><br>I therefore conclude that the spaces must have been removed by <b>osis2mod</b>.<br>This is serious! It needs to be investigated by our Sword developers.<br><br>NB. I also wish to repeat that this uppercase word in <b>Titus 3:1</b> should not have a SMALL LONG S</div><div><br></div><blockquote style="border-left: 3px solid rgb(200, 200, 200); border-top-color: rgb(200, 200, 200); border-right-color: rgb(200, 200, 200); border-bottom-color: rgb(200, 200, 200); padding-left: 10px; color: rgb(102, 102, 102);"><div><span><span>Titus 3:1: <b>ADMONNE</b></span><span style="color: rgb(237, 65, 57);"><b>ſ</b></span><span><b>TE</b> les qu'ils ſoyent ſujets aux Principautez puiſſances , qu'ils obeïſſent aux Gouverneurs , qu'ils ſoyent preſts à toute bonne œuvre :</span></span></div></blockquote><div><br></div><div><br></div><div>Best regards,</div><p></p><div style="font-family: Arial, sans-serif; font-size: 14px;" class="protonmail_signature_block"><div class="protonmail_signature_block-user"><br>David
</div>
<div style="font-family: Arial, sans-serif; font-size: 14px;"><br></div>
<div class="protonmail_signature_block-proton">
Sent with <a href="https://pr.tn/ref/SWXT9A5YZ67G" target="_blank" rel="noreferrer nofollow noopener">Proton Mail</a> secure email.
</div>
</div>
<br>
<br>
On Saturday, July 26th, 2025 at 9:49 AM, domcox <a href="mailto:dominique@corbex.org" rel="noreferrer nofollow noopener">dominique@corbex.org</a> wrote:<p></p>
<p></p>
<blockquote>
<p>David Haslam <a href="mailto:dfhdfh@protonmail.com" rel="noreferrer nofollow noopener">dfhdfh@protonmail.com</a> writes:</p>
<blockquote>
<p>Dear Dom,</p>
<p>I had already reported this issue!</p>
<p>* Only 11 instances of & are followed correctly by a space<br>
character.<br>
* 6226 instances of & are not followed by a space!!!</p>
<p>This outstanding defect still requires fixing! Please insert the<br>
required spaces.</p>
</blockquote>
<blockquote>
<p>Dear Dom,</p>
<p>I had already reported this issue!</p>
<p>* Only 11 instances of & are followed correctly by a space<br>
character.<br>
* 6226 instances of & are not followed by a space!!!</p>
<p>This outstanding defect still requires fixing! Please insert the<br>
required spaces.</p>
</blockquote>
<p>Hi David!</p>
<p>I replied yesterday, but I'm resending this email @modules, as I<br>
suppose my emails to ProtonMail are blocked somewhere.</p>
<p>Thank you for your report.</p>
<p>This point let me think there is another issue in SWORD with the<br>
ampersand, as I have 0 instance of & not followed by a space<br>
in<br>
the source file....</p>
<p>1. Search for '&' (all instances of &):<br>
$ grep -o -i '&' fregeneve1669.osis.xml | wc -l<br>
6237<br>
2. Search for '& ' (followed by a space):<br>
$ grep -o -i '& ' fregeneve1669.osis.xml | wc -l<br>
6200<br>
3. Search for '>amp;<' (transChange):</p>
<p>$ grep -o -i '>&<' fregeneve1669.osis.xml | wc -l</p>
<p>35<br>
4. Search for 'amp; ' (followed by a narrow no-break space<br>
(u+202F)<br>
$ grep -o -i '& ' fregeneve1669.osis.xml | wc -l<br>
2</p>
<p>Please find the OSIS file attached.</p>
<blockquote>
<p>Aside: It may be a further point of interest to discuss whether<br>
the spaces surrounding each ampersand ought to be a<br>
punctuation space. In my view they shouldn't, because the symbol<br>
is an abbreviation for the French word "et".</p>
<p>While libsword doesn't handle the three entities: & ><br>
< we still need a workaround for use in SWORD-based<br>
front-ends!</p>
</blockquote>
<p>There are other modules affected with the ampersand issue, with a<br>
less<br>
serious impact:<br>
- asv: 5 (Not a big deal, all & are in the intro)<br>
- geroffbist: 234 (almost all links in footnotes are broken)<br>
- tdavid: 77 (mainly &c.)</p>
<p>TEI dictionnaries are OK, no issue so far with the ampersand</p>
<blockquote>
<p>btw. Has anyone researched why Android devices cannot display a<br>
FULL WIDTH AMPERSAND ?</p>
</blockquote>
<p>The default font on Android is Roboto from Google.<br>
<a href="https://fonts.google.com/specimen/Roboto" target="_blank" rel="noreferrer nofollow noopener">https://fonts.google.com/specimen/Roboto</a><br>
Looks like this font includes the FULL WIDTH AMPERSAND among<br>
others<br>
So why And Bible displays a white square ? that's the question</p>
<p>--<br>
Dom</p>
</blockquote></div>
</blockquote><br>
</div></div>