You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
where * is whatever marker you want to use. Note that you can also add a kerning space after the marker if required. So, for example, if you want a dash ‘-’ to be the marker to show where the verse starts and then have a 1pt space before the 1st word of the next verse, then use this:
\def\marginversemarker{-\kern 1pt}
Currently this does it everywhere (even at the start of a paragraph/line) which may not be ideal, but it is as far as we’ve got so far.
I have several projects who are asking for this feature and I’m not sure how tech savvy they are to follow your excellent instructions. They want to use this for community checking the books and portions as they work through the translation process.
The text was updated successfully, but these errors were encountered:
OK, I can't find the snippet, but I've reimplemented it. Once I've pushed (I'm running pytest now), then
if you only want them mid-paragraph, set \noparstartmvmtrue (the default) otherwise \noparstartmvmfalse.
\def\marginversemarker{*}
where * is whatever marker you want to use. Note that you can also add a kerning space after the marker if required. So, for example, if you want a dash ‘-’ to be the marker to show where the verse starts and then have a 1pt space before the 1st word of the next verse, then use this:
\def\marginversemarker{-\kern 1pt}
Currently this does it everywhere (even at the start of a paragraph/line) which may not be ideal, but it is as far as we’ve got so far.
https://community.scripture.software.sil.org/t/marker-for-the-inside-text-of-verses/3750/2
I have several projects who are asking for this feature and I’m not sure how tech savvy they are to follow your excellent instructions. They want to use this for community checking the books and portions as they work through the translation process.
The text was updated successfully, but these errors were encountered: