0 votos
200 visualizações

Working on a Glossary and running basic checks. A lot of helpful errors coming up.

But where we refer in the text to certain chapters like Book 2—5 or certain verses like Book 4.12-14 we get errors. Those should not be errors.

I then go to > Checking > Punctuation Inventory… and the “bad” characters are not even listed under medial.

The long-dash and the hyphen are properly defined in the project Scripture Reference Settings as “Range of Chapters or Books” and “Range of Verses”.

The only “exotic use” we are doing here is that we use those references in actual text, not in a technical “Cross Reference” since those are not working for this project (where many books have not been translated yet). For example:

Ɩ tɩɩ ŋǝ̂ ʊkɛɛshɩɩ ɖe Lefitiki 12—14 nɩ.

The above example means “You can see examples of this in Leviticus chapters 12 to 14”.

So it feels to me that the checking tool is “finding” punctuation in the Glossary, but the inventory tool is somehow ignoring the Glossary.

Or I am overlooking something. Thank you for your input.

Publicação antiga - exibida no idioma original
Paratext por (934 pontos)
reexibida | 200 visualizações

1 Resposta

+1 voto
Melhor resposta

Tim,
There are multiple things at work with Scripture References.

  1. Any reference that has been marked with markers like \r, \mr, \xt, \ior get checked by the Scripture reference settings. One issue that can be a problem here is that you need to mark references, but the names may sometimes be abbreviated and sometimes written out. The settings only allow one option for \xt (for instance) and so if you mix abbreviations and short names you will have reference errors.
  2. Any numbers that are not specifically marked as Scripture references get checked as numbers. When numbers report medial punctuation errors, these errors are based on the number settings.

So, if you have Scripture references, they need to be marked appropriately.

Publicação antiga - exibida no idioma original
por (9,9k pontos)

Thank you @anon848905, you got me on the right track. No more wrong errors in this project.

As I had written, this is not about Scripture References in the technical sense. All we do, we mention in the Glossary, in prose, that people could eventually read more about Mr. XYZ in certain chapters.

So when you sent me to number settings, that did the trick. Since we follow the syntax of the Scripture Reference Settings, we would write 12—16 when we mean chapters. Normally one might write 12 — 16, but we want to help our readers with some consistency.

So PT, not seeing spaces, has (correctly) reported the longer dash in 12—16 as a medial punctuation.

I had not understood the error messages, because “all the stuff that goes with numbers” (like decimal points or plus or minus signs) was in my brain not classified as “punctuation”. Normally when I get punctuation errors, it means there is a first-ever use of a character somewhere in text, so I had forgotten that there are several places where PT collects data for valid characters.

All is well, thread can be closed (I have not yet found where to tick that). I give you one pink heart and say thank you.

Publicação antiga - exibida no idioma original

Perguntas relacionadas

0 votos
3 respostas 498 visualizações
Estou recebendo um erro nas verificações básicas (Basic Checks): REV 11:3 Invalid medial punctuation: (1 260). Ele ... configuração das verificações, ou este é um bug do Paratext?
jeffh 1,4k perguntada Set 1, 2020
0 votos
2 respostas 356 visualizações
I received this question from a translator: Do you know why I am getting this error and how I can tell Paratext ... SIL PNG Language Resources Ukarumpa EHP 444 | Papua New Guinea
SIL LSS PNG 411 perguntada Fev 1, 2018
0 votos
1 resposta 32 visualizações
Sou voluntário (com experiência limitada no PT) ajudando uma equipe de tradução a preparar os Evangelhos e os Atos para ... essa mensagem de erro. Obrigado desde já pela ajuda.
mark2024 124 perguntada Ago 15, 2025
0 votos
1 resposta 35 visualizações
Estamos usando /xt nas referências cruzadas de notas de rodapé, configurado para usar o 'nome curto' do livro. Mas ... Existe um código USFM diferente que eu possa usar para isso?
Lenice 180 perguntada Out 7, 2025
+1 voto
1 resposta 198 visualizações
Vinculamos Espírito Santo (Asubane Noekene) à entrada correspondente no nosso glossário. Agora também queremos vincular santo ( ... mudar de volta. Ou haveria uma solução melhor?
Anne Stoppels 106 perguntada Set 18, 2024
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,048 perguntas
6,007 respostas
5,672 comentários
2,028 usuários