[sword-devel] New Beta Module: FreGeneve1669

[David Haslam]

Resending without attachment!

On Saturday, July 26th, 2025 at 11:07 AM, David Haslam <dfhdfh at protonmail.com> wrote:

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