0 votes
505 vues

One of the projects I support has the following formatting for their chapter/verse references in footnotes (the part after the \fr and before the \ft tag) 31.5 rather than 31:5 which is what they want. I had them check their scripture reference settings and they specify a :.

Does anyone know how to get PT to convert the Footnote chapter/verse references to the desired format or does the team need to do that manually?

Thanks!

Ancienne publication - affichée dans sa langue d'origine
Paratext par (155 points) | 505 vues

3 Réponses

0 votes
Meilleure réponse

It might be worth pointing out here that Paratext uses the current chapter/verse separator from the Reference Settings each time it inserts a footnote, but if the separator changes, existing footnotes are not affected. So at one point the chapter/verse separator must have been set to a full stop (period). Changing it to colon will result in all new footnotes using colon, but you will still need a regex to fix existing footnotes.

Ancienne publication - affichée dans sa langue d'origine
par (304 points)
0 votes

It is fairly straightforward to do using RegexPal. I think Randy Hasty actually set up a batch of preconfigured regexes including one that that covers standardizing the footnote reference format. If you are familiar with RegexPal, I can try to send you a search and replace string that would fix the reference format, or you might be able to get the more complete preconfigured user menu that Randy already set up.

Ancienne publication - affichée dans sa langue d'origine
par (418 points)
0 votes

Thanks! I figured that a regex could be a solution, but I wasn’t sure how exactly to use it.

Thanks for the input. I think we’ll be able to solve the problem from here.

Ancienne publication - affichée dans sa langue d'origine
par (155 points)

anon469793,
To find the period in the middle of a reference and change it to a colon I use the following in the Paratext Find/Replace.
Find:
regex:(?<=\d).(?=\d)
Replace:
:
This says, “use regex” to look for a period that is proceeded by a digit and followed by a digit and replace it with a colon.

Obviously if you have other places in the text where you have digit period digit and want to keep them you would need to expand the find. You might want to do a find first and examine the results to see if there are any items that need to be maintained (like $200.00)

Ancienne publication - affichée dans sa langue d'origine

To just get the \fr field you could expand the find to be:
Find:
regex:(?<=\fr \d+).(?=\d)
Replace:
:

Ancienne publication - affichée dans sa langue d'origine

Questions connexes

0 votes
1 réponse 9,5k vues
Concernant le livre des Psaumes, nous aimerions utiliser le pluriel Psaumes dans les titres de livres et dans la ... Reference Settings) et le pluriel dans le texte USFM ?
bit 495 posée nov. 12, 2021
0 votes
3 réponses 534 vues
Lorsqu'on donne des références bibliques qui s'étendent sur plusieurs chapitres, l'équipe Komba préfère les marquer comme suit : 1: ... est trop long et n'est pas agréable à l'œil.
anon142050 118 posée avr. 17, 2019
0 votes
2 réponses 355 vues
When you make corrections to \toc headers, the Book Names under Scripture Reference Settings don’t seem to update automatically. Is that by design?
anonyme posée avr. 10, 2015
0 votes
4 réponses 871 vues
Je fais face à un certain nombre de notes de bas de page souffrant de copier-coller-itis : la référence de la note de ... même pas besoin de mettre le \fr (ou \xo) du tout.
CraigF 237 posée oct. 23, 2020
0 votes
2 réponses 566 vues
Je travaille avec une équipe qui souhaite rédiger des références bibliques de cette manière : \xt book_name rukuh # ayat #\xt* où ... . Y a-t-il un moyen de contourner cela ?
mnjames 1,9k posée sept. 12, 2022
Welcome to Support Bible, where you can ask questions and receive answers from other members of the community.
For we were all baptized by one Spirit so as to form one body—whether Jews or Gentiles, slave or free—and we were all given the one Spirit to drink.
1 Corinthians 12:13
3,053 questions
6,013 réponses
5,677 commentaires
2,032 utilisateurs