0 votes

In our project (Mussau), we have a footnote at Psalms 3:2 which has the following format:

\f + \fr 3:2 \ft Tale inangari nge Ibru, laghe pitila \tl Selah\tl*, me tee tale ves 4 me ves 8. Malloeana karika ita kilakila amasina, me tau ngalomasaanga la aiesoaa va malloeana va \fqa toitoi \ft o \fqa uainoana me unannaa.\f*

In Paratext 10 Studio (β1 developer preview), the part after \tl* as far as \fqa is put into the text, and the part from \fqa to the end is back in the footnote, so it looks like this after the caller:

, me tee tale ves 4 me ves 8. Malloeana karika ita kilakila amasina, me tau ngalomasaanga la aiesoaa va malloeana va

The spacing in the footnote is a bit off, too, with what looks like two spaces before Selah and on each side o in the last part, so that I suspect an extra space is coming from the markup codes.

Paratext 10 Studio ago by (334 points)

1 Answer

0 votes
I'm not sure if it will fix the issue (since I can't get into 10 Studio right now), but the \tl ... \tl* is a "nested" character style and should be written as \+tl ...\+tl*. See if that fixes the issue.
ago by (8.7k points)
OK, I hadn't known that, and it hadn't caused a problem with typesetting the New Testament seven years ago!

I'll try that tomorrow, if I can get send/receive to actually complete. I haven't been able to get it to complete for 62 days (not that I'm using it every day...). I just get the continuous circle indicator in a dimmed button. I'll let it run overnight to see if I can get it to complete.
John, I just tested it and it does appear to be very buggy. Please note that 10 Studio is still an early Beta. Use with caution.
Leaving it overnight just gave me an RPC error, and trying to do send/receive again immediately fails. I was using it for having a second version of the data visible, with my actual work going on in a virtual machine, so that I could jump around and copy text as we're working on consistency of translation within Psalms. So not a big deal in the end.

It's interesting that the Paratext 9.5 marker checks don't flag the original issue, and PT 9 does display correctly. It seems that PT 10 Studio is more rigorous in its interpretation of the markup. That's a good thing, and it makes me go back and fix several other places where we have transliterated text in a footnote.
Just a note on the particular error that you first saw. Paratext doesn't see the \tl ...\tl* as an error with the marker check, but if you hold shift while opening the Run Basic Checks you will see the Schema check. This will report on issues, but is difficult to interpret as it normally reports 50 errors for each issue. When you see the list of issues, look for the second verse listed and it is likely that there is an issue in a footnote at that point (as I said, difficult to interpret).
I undid the fix and tried the schema check. It certainly generated a lot of difficult to interpret messages, none of which would have shown me what the actual error was. With the fix, all was good there. Thanks for the help!

Related questions

0 votes
2 answers
0 votes
1 answer
PTXprint Apr 15, 2023 asked by mnjames (1.8k points)
0 votes
2 answers
0 votes
2 answers
PTXprint Nov 10, 2022 asked by anon180868 (190 points)
Welcome to Support Bible, where you can ask questions and receive answers from other members of the community.
Give proper recognition to those widows who are really in need.
1 Timothy 5:3
2,805 questions
5,653 answers
5,219 comments
1,679 users