well-formed USFM checking

[warpok]

First of all, I want to thank you, Teus. I have been working on our formatting of the Bible text for submission to various apps, and the way Bibledit works so reliably has been a great blessing to me and our team. We use Paratext for basic checks, so that is part of the mix. Some editing tasks are way easier to do in Bibledit, and then I can reliably merge the files to Paratext. [Example: Paratext cannot tell you which \s lines are followed by \r, but Bibledit can. Search for \s in the cloud app, and use Ctrl-f to tell your browser to search for \r in the displayed results.]

Recently YouVersion updated their app, and I think that some things that displayed properly before no longer work. The requirements I need to satisfy for YouVersion have become more like what I face in preparing our text for the QuickBibles app. Certain things that I like to do in our printed text no longer show up properly every time I try to make a file that will be sent to DBL for use in YouVersion and other apps. So I am recommending that Bibledit also include some things in the well formed USFM checks.

• We put cross references right in section headings, with a special \xta Pericope \xta* marking in them. I liked not having some section headings with references (\r) below and others without them. The page appearance is more consistent if the section references appear down with all the other footnotes and cross references at the bottom of the page. But this flat out doesn't work anymore. Bibledit doesn't currently see that as an error, but now with the reality of what we have in apps, I think it would be good if Bibledit did check such things.
• We also had footnotes in some section headings. Those footnotes just get skipped, and I didn't realize they were not appearing in the apps. There is always a place where such footnotes can be put in the text itself, where they are expected.
• The YouVersion app and QuickBibles do not recognize \s2 second-level section headings. What a pity! First I tried using \b \pc to replace \s2. Now I am using \b \qr (like for Selah in Psalms) to replace \s2. BUT those two markings only work inside scripture text. If you want to put an \s2 heading (now using \qr) above verse 1, then it is not in the Scripture text. I don't actually know if YV will accept such and display them, but I am sure that QuickBibles does not display them.
• Previously there were about 10 places in our text where we placed a section heading inside of a verse. We split some verses with a section heading. This causes the part of the verse below the section heading to be added to the section heading in QuickBibles. YV displays that properly.

Perhaps these things might be added to items that can be checked in Bibledit.

[teusbenschop]

Sounds like a good idea.

[teusbenschop]

About putting cross references in headers, like the eta markup, in USFM 3 this is allowed, and there is an example from that in the USFM 3 documentation.

https://ubsicap.github.io/usfm/notes_basic/xrefs.html

\c 3
\s1 The Preaching of John the Baptist\x - \xo 3.0 \xta Compare with \xt Mk 1.1-8;
Lk 3.1-18; \xta and \xt Jn 1.19-28 \xta parallel passages.\x*
\p
\v 1 At that time John the Baptist came to the desert of Judea and started preaching.

If Bibledit does not flag this as an error, then this is good, because it's not an error in the USFM.

[warpok]

This is true. If a project administrator only wants to print Scripture, then this is not something that needs to be checked for. But increasingly, all projects are going to want to publish to apps, and expecially YouVersion. I believe that the new version of YouVersion no longer supports the use of \xta, as we used it before.

If so, Bible edit users will probably want to be able to activate or non-activate the checking of headings, based on where they are currently targeting their publication efforts.

[warpok]

But on second thought, perhaps it is better for us to use the various methods of searching and replacing such special format issues as \s2 and cross references in headings.

[teusbenschop]

It looks like YouVersion not taking \xta anymore would be a regression on their part, a regression in their software. Once thought that comes up right now is that perhaps it would help to report this bug to them - likely you already did - that this will enable them to fix their import routine. Because the USFM standard is moving forward, and Bibledit supports (most of) it, and I think that YouVersion would do good to move along with the USFM standards, to stay up-to-date, and support USFM 3 too.

[warpok]

Actually, I haven't reported this to them. They have been busy with many new features. So I wonder if this will be important to them.

Thanks for your ideas. I may report this, since I sometimes get their attention.

Phil

Phil Fields USA: 479-343-9291 Indonesia and Whatsapp: +62 821 2586 7775 303 Ryan Ct., Siloam Springs, AR 72761

albata.info dailybiblereading.info Firman Allah adalah Kunci Kehidupan

Pada Rab, 13 Mar 2024 pukul 15.14 Teus Benschop @.***> menulis:

It looks like YouVersion not taking \xta anymore would be a regression on their part, a regression in their software. Once thought that comes up right now is that perhaps it would help to report this bug to them - likely you already did - that this will enable them to fix their import routine. Because the USFM standard is moving forward, and Bibledit supports (most of) it, and I think that YouVersion would do good to move along with the USFM standards, to stay up-to-date, and support USFM 3 too.

— Reply to this email directly, view it on GitHub https://github.com/bibledit/cloud/issues/928#issuecomment-1995643685, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABDSIJMORY3LOFIUKTKI2R3YYCXRJAVCNFSM6AAAAABCFLO5OSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJVGY2DGNRYGU . You are receiving this because you modified the open/close state.Message ID: @.***>