New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Corner case usage for \va_#\va* (or even \vp_#\vp*) #79

Open
DavidHaslam opened this Issue Jan 7, 2019 · 1 comment

Comments

Projects
None yet
1 participant
@DavidHaslam
Copy link

DavidHaslam commented Jan 7, 2019

One of the lines describing \va_#\va* is as follows:

The content within the marker pair should only contain the alternate verse number, and not include any formatting/presentation characters (e.g. brackets or parentheses)

However, some Bible translations present a need for an alternative verse reference for a verse that actually is in the next or previous chapter.

An example is the versification in Hosea for some Spanish Bibles.

Chapter 13 verse 16 becomes chapter 14 verse 1, with all the subsequent verses in chapter 14 being incremented accordingly.

To record this the translator (or transcriber of a historic Bible) might wish to have:

\v 16 \va 14:1\va* Samaria será asolada porque se rebeló contra su Dios: caerán a cuchillo: sus niños serán estrellados, y sus preñadas serán abiertas.

But the use of "14:1" as the content within the marker pair goes against the strict advice in the USFM User Reference.

What is the official policy for marking such a corner case?

@DavidHaslam

This comment has been minimized.

Copy link

DavidHaslam commented Jan 7, 2019

The same translation has a similar case in Jonah.

Chapter 1 verse 17 becomes chapter 2 verse 1, etc.

\v 17 \va 2:1\va* Mas Jehová había aparejado un gran pez, que tragase a Jonás; y estuvo Jonás en el vientre del pez tres días y tres noches.

NB. Even if the versification was done the other way round, the need to record the alternate verse reference for a verse that "jumps chapters" would still exist.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment