0 वोट
200 व्यूज़

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.

पुराना पोस्ट - इसकी मूल भाषा में दिखाया जा रहा है
Paratext में द्वारा (934 अंक)
फिर से दिखाया गया | 200 व्यूज़

1 उत्तर

+1 मत
सर्वोत्तम उत्तर

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.

पुराना पोस्ट - इसकी मूल भाषा में दिखाया जा रहा है
द्वारा (9.9k अंक)

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.

पुराना पोस्ट - इसकी मूल भाषा में दिखाया जा रहा है

संबंधित प्रश्न

0 वोट
3 उत्तर 498 व्यूज़
मुझे एक मूल जाँच (basic checks) त्रुटि मिल रही है: REV 11:3 Invalid medial punctuation: (1 260). यह त्रुटि इस पाठ के कारण ... में कुछ छूट रहा हूँ, या क्या यह Paratext की एक बग है?
jeffh 1.4k पूछा गया सितंबर 1, 2020
0 वोट
2 उत्तर 356 व्यूज़
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 पूछा गया फ़रवरी 1, 2018
0 वोट
1 उत्तर 32 व्यूज़
मैं एक स्वयंसेवक हूँ (PT के साथ सीमित अनुभव) जो एक अनुवाद टीम को DBL में अपलोड करने के लिए सुसमाचार और ... त्रुटि संदेश क्यों मिल रहा है। आपकी सहायता के लिए अग्रिम धन्यवाद।
mark2024 124 पूछा गया अगस्त 15, 2025
Paratext में
0 वोट
1 उत्तर 35 व्यूज़
हम फुटनोट क्रॉस-रिफरेंस में /xt का उपयोग कर रहे हैं, जिसे पुस्तक के 'छोटे नाम' का उपयोग करने के लिए सेट किया गया है। ... इसके लिए कोई अलग USFM कोड है जिसका मैं उपयोग कर सकता हूँ?
Lenice 180 पूछा गया अक्टूबर 7, 2025
+1 मत
1 उत्तर 198 व्यूज़
हमने पवित्र आत्मा (Asubane Noekene) को हमारी ग्लॉसरी में संबंधित प्रविष्टि से लिंक कर दिया है। अब हम पवित्र (noekene) को ... फिर इसे वापस बदल दें। या क्या कोई बेहतर समाधान होगा?
Anne Stoppels 106 पूछा गया सितंबर 18, 2024
Welcome to Support Bible, where you can ask questions and receive answers from other members of the community.
And let us consider how we may spur one another on toward love and good deeds, not giving up meeting together, as some are in the habit of doing, but encouraging one another—and all the more as you see the Day approaching.
Hebrews 10:24-25
3,048 प्रश्न
6,007 उत्तर
5,672 टिप्पणियाँ
2,028 उपयोगकर्ता