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

Add additional examples of use of \xt markup in documentation #34

Closed
klassenjm opened this Issue Sep 23, 2016 · 4 comments

Comments

Projects
None yet
2 participants
@klassenjm
Contributor

klassenjm commented Sep 23, 2016

Proposal

  • Where references exist outside of cross-reference text in the text examples provided in the USFM documentation, include \xt ...\xt* where possible, to highlight it's usage.

@klassenjm klassenjm added this to the 3.0.rc2 milestone Sep 23, 2016

@klassenjm klassenjm modified the milestones: 3.0.rc2, 3.0.0 Oct 27, 2017

@DavidHaslam

This comment has been minimized.

Show comment
Hide comment
@DavidHaslam

DavidHaslam Dec 7, 2017

This requirement has become more urgent, as noted in the email correspondence today with myself and Dieter. It's also prompted some further questions about how to deal with chapterless verse references.

DavidHaslam commented Dec 7, 2017

This requirement has become more urgent, as noted in the email correspondence today with myself and Dieter. It's also prompted some further questions about how to deal with chapterless verse references.

@klassenjm

This comment has been minimized.

Show comment
Hide comment
@klassenjm

klassenjm Dec 7, 2017

Contributor

Noted. I expect an updated version of all docs and schema / stylesheets for USFM and USX in early January.

Contributor

klassenjm commented Dec 7, 2017

Noted. I expect an updated version of all docs and schema / stylesheets for USFM and USX in early January.

@DavidHaslam

This comment has been minimized.

Show comment
Hide comment
@DavidHaslam

DavidHaslam Dec 8, 2017

This reminds me of something I observed earlier this year while processing references for a Polish Bible translation.

Chapter-less verse references were prefixed with either "w. " for a single verse or "ww. " for a verse range or sequence. e.g.

\x + \xt ww. 13-22.\x*
\x + \xt w. 1.\x*
\x + \xt ww. 13.19.28; Ps 50,15; Oz 5,15. \x*

Notes

  1. This underscores the fact that the potential syntactical verse prefix is language specific, and therefore should be specified in the locale for the translation language.
  2. Likewise, whether the translators use a period and a space after these two Polish abbreviations (equivalent in meaning to "verse" and "verses") is also a matter of choice!
  3. That the punctuation for a sequence of verses can be the period rather than the usual comma was also a challenge!
  4. How Scripture references are punctuated varies from language to language, and sometimes even between Bible versions in the same language!

DavidHaslam commented Dec 8, 2017

This reminds me of something I observed earlier this year while processing references for a Polish Bible translation.

Chapter-less verse references were prefixed with either "w. " for a single verse or "ww. " for a verse range or sequence. e.g.

\x + \xt ww. 13-22.\x*
\x + \xt w. 1.\x*
\x + \xt ww. 13.19.28; Ps 50,15; Oz 5,15. \x*

Notes

  1. This underscores the fact that the potential syntactical verse prefix is language specific, and therefore should be specified in the locale for the translation language.
  2. Likewise, whether the translators use a period and a space after these two Polish abbreviations (equivalent in meaning to "verse" and "verses") is also a matter of choice!
  3. That the punctuation for a sequence of verses can be the period rather than the usual comma was also a challenge!
  4. How Scripture references are punctuated varies from language to language, and sometimes even between Bible versions in the same language!
@DavidHaslam

This comment has been minimized.

Show comment
Hide comment
@DavidHaslam

DavidHaslam Dec 8, 2017

See also issue #41

DavidHaslam commented Dec 8, 2017

See also issue #41

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