adyeths
commented
6 years ago The example config file is just that, an example. It doesn't dictate how the abbreviations are supposed to be composed, how many entries there should be, or what characters are allowed in the abbreviations. People should use whatever abbreviations they used in the text, including punctuation. So if, for example, they used Judg. for Judges, then that's what belongs in the config file for orefs. And if they used multiple abbreviations for a particular book, they should add multiple abbreviations to the config file. (Like I did for Wisdom of Solomon in the example config file.)
I would be very cautious running orefs on a text that uses a single character abbreviation! That could produce very unpredictable results. (Most likely causing many references to fail to be converted to osisRef attributes.)
DavidHaslam
The example config file lists book abbreviations that have no full-stop.
Some translations terminate abbreviations with a full-stop. Many do not.
Though this should not matter to the script, it matters to users making their own config file.
Particular care is required to avoid adding a full-stop to those shorter booknames such as
AmosandJobwhere the abbreviation is identical to the name, when that's what's used in references.It should go without saying that no two book abbreviations should be the same.
Include a reminder about this risk for the abbreviations of Judges, Judith & Jude or Philippians & Philemon.
btw. Though the example abbreviations are all 3 characters, this is not a requirement! cf. I have encountered a set of abbreviations in which the shortest was the single character
Jfor John.