Difference between revisions of "Talk:Alternate Versification"

From CrossWire Bible Society
Jump to: navigation, search
(SynodalP: :The name has been changed to '''SynodalProt'''. ~~~~)
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Go Bible Forum topic on Different Versification Systems ==
+
[[Talk:Alternate Versification/Archive]]
 +
== Front-end support for av11n ? ==
  
A topic on versification schemes has been added in the Go Bible Forum. See [http://jolon.org/vanillaforum/comments.php?DiscussionID=745]. Initial focus is for Slavic languages (e.g. Russian, Ukrainian).  I'm adding this link here in case further useful information gets posted. [[User:David Haslam|David Haslam]] 09:03, 22 November 2008 (UTC)
+
'''I have removed this content, I thgink it is now truly irrelevant as all frontends we have listed as active support av11n. In fact, I would propose delisting any frontend which does not.... '''[[User:Refdoc|refdoc]]:[[User_Talk:Refdoc|talk]] 07:41, 8 January 2018 (MST)
  
== Heading levels in wikimedia pages ==
+
In theory, there are several aspects to consider when looking at front-end application support for alternate versification:
 +
# Can the module be installed at all, without causing the application to crash?
 +
# Can an installed module with av11n be properly displayed with all of its content? Or with only some of its content?
 +
# Can the application readily navigate to books and chapters that are outside the default v11n?
 +
# For av11ns with a different book order, can the module be ''scrolled'' in the defined av11n book order?
 +
# Can the application display two or more modules with ''different'' versifications in parallel mode (or as an interlinear view) with proper alignment of the text content?
 +
Front-end support for av11n is at various stages of development. The av11n support status of some of the more popular front-ends is tabled [[Choosing a SWORD program#Module_Support|here]].
  
The general preference is that only the page title should be at top heading level. [[User:David Haslam|David Haslam]] 17:15, 29 November 2008 (UTC)
+
==1.8.1==
  
== How to identify whether an existing alternate versification scheme matches requirements? ==
+
There is no agreement to put the following versifications into the source. While there is none it should not be in the main text
  
If a new [[Module Requests|module request]] requires alternate versification, how can we help to identify whether the requirements match a scheme that already exists at CrossWire? [[User:David Haslam|David Haslam]] 16:48, 26 April 2009 (UTC)
+
:''Not yet released.''
 +
Liturgical variants<ref>See https://gitlab.com/lafricain79/LinVB/tree/master/v11n</ref> based on the Catholic liturgical translations (based itself on the neoVulgate), of which two correspond to existing Catholic versifications:
 +
* '''Catholic_lit''' &ndash; like Catholic but with significant differences, Esther with 10 chapters.
  
:New page started on this subject. [[Alternate Versification/System Identification]].  ''Thanks to Osk''. [[User:David Haslam|David Haslam]] 17:57, 29 April 2009 (UTC)
+
* '''Catholic2_lit''' &ndash; like Catholic2 but with significant differences, Esther with 16 chapters.
  
== SWORD release versions? ==
+
* '''Catholic3_lit''' &ndash; corresponding to Catholic, but where Esther's alternate versification is integrated into the current 10 chapters, to allow a better reading. This means that the verses of the chapters numbered with letters are integrated into the current 10 chapters of Esther.
 
+
The main article refers to SWORD v1.5.12 and later. Should some or all of these references be changed to SWORD v1.6.x ? [[User:David Haslam|David Haslam]] 10:35, 12 May 2009 (UTC)
+
 
+
== Numeronyms, etc ==
+
 
+
My recent edits to the page were prompted by Tonny Kohar asking what '''v11n''' meant. <br>
+
I have also been at work on Wikipedia. See [http://en.wikipedia.org/wiki/Numeronym] and [http://en.wikipedia.org/wiki/Category:Numeronyms]. [[User:David Haslam|David Haslam]] 19:11, 8 September 2009 (UTC)
+
 
+
== SWORD canon header file? ==
+
 
+
What is a SWORD [[canon header]] file? [[User:David Haslam|David Haslam]] 09:42, 26 October 2009 (UTC)
+
 
+
== JSword and av11n ? ==
+
 
+
Please add a section on the current state of the art for av11n support in JSword. [[User:David Haslam|David Haslam]] 12:39, 12 January 2010 (UTC)
+
 
+
== Bibles with more than one Versification  ==
+
 
+
I added this section because the USFM reference use the term "alternate versification" in a ''different sense'' than we have been hitherto discussing within CrossWire. It's a necessary distinction to be aware of, and perhaps one that will promote further creative thinking. [[User:David Haslam|David Haslam]] 06:43, 9 July 2011 (MDT)
+
 
+
== French Bibles ==
+
 
+
We need a versification system defining for French Bibles, so that we can properly address some of the related issues we encounter in French modules. See (for example) http://www.crosswire.org/bugs/browse/MOD-186 [[User:David Haslam|David Haslam]] 03:45, 4 January 2012 (MST)
+
 
+
:The consequences of not having one is that we all too easily fail to catch the module issues such as verses missing at the end of many Psalms. We cannot rely indefinitely on the fact that a few of us happen to know what to look for. The software tools used during module creation and testing should report such errors. [[User:David Haslam|David Haslam]] 03:48, 4 January 2012 (MST)
+
 
+
== SynodalP ==
+
 
+
The versification called '''SynodalP''' is now deprecated - it is not supported by the latest Sword utilities. [[User:David Haslam|David Haslam]] 01:44, 6 July 2012 (MDT)
+
 
+
:The name has been changed to '''SynodalProt'''.  [[User:David Haslam|David Haslam]] 04:37, 12 December 2014 (MST)
+

Latest revision as of 14:41, 8 January 2018

Talk:Alternate Versification/Archive

Front-end support for av11n ?

I have removed this content, I thgink it is now truly irrelevant as all frontends we have listed as active support av11n. In fact, I would propose delisting any frontend which does not.... refdoc:talk 07:41, 8 January 2018 (MST)

In theory, there are several aspects to consider when looking at front-end application support for alternate versification:

  1. Can the module be installed at all, without causing the application to crash?
  2. Can an installed module with av11n be properly displayed with all of its content? Or with only some of its content?
  3. Can the application readily navigate to books and chapters that are outside the default v11n?
  4. For av11ns with a different book order, can the module be scrolled in the defined av11n book order?
  5. Can the application display two or more modules with different versifications in parallel mode (or as an interlinear view) with proper alignment of the text content?

Front-end support for av11n is at various stages of development. The av11n support status of some of the more popular front-ends is tabled here.

1.8.1

There is no agreement to put the following versifications into the source. While there is none it should not be in the main text

Not yet released.

Liturgical variants[1] based on the Catholic liturgical translations (based itself on the neoVulgate), of which two correspond to existing Catholic versifications:

  • Catholic_lit – like Catholic but with significant differences, Esther with 10 chapters.
  • Catholic2_lit – like Catholic2 but with significant differences, Esther with 16 chapters.
  • Catholic3_lit – corresponding to Catholic, but where Esther's alternate versification is integrated into the current 10 chapters, to allow a better reading. This means that the verses of the chapters numbered with letters are integrated into the current 10 chapters of Esther.
  • See https://gitlab.com/lafricain79/LinVB/tree/master/v11n