User:Dmsmith/KJV 2.6 - Revision history

David Haslam: /* Punctuation and Strongs, Future */ :This issue is a symptom of an underlying one that was there from when Strong's markup was first added. It was done with "greedy backwards matching" - viz. The ''start'' of a '''w''' element is just after the

2023-06-22T20:08:21Z

Punctuation and Strongs, Future: :This issue is a symptom of an underlying one that was there from when Strong's markup was first added. It was done with "greedy backwards matching" - viz. The ''start'' of a '''w''' element is just after the

← Older revision		Revision as of 20:08, 22 June 2023
Line 261:		Line 261:

	This issue was also reported by email on 2015-09-10. [[User:David Haslam\|David Haslam]]		This issue was also reported by email on 2015-09-10. [[User:David Haslam\|David Haslam]]

			:This issue is a symptom of an underlying one that was there from when Strong's markup was first added. It was done with "greedy backwards matching" - viz. The ''start'' of a '''w''' element is just after the ''end'' of the ''previous'' '''w''' element in the verse text. [[User:David Haslam\|David Haslam]] ([[User talk:David Haslam\|talk]])

	== Parsing the study notes ==		== Parsing the study notes ==

David Haslam: /* Notes appertaining to Psalm titles, 2.12 (if possible) */ minor corrections

2023-05-04T10:23:56Z

Notes appertaining to Psalm titles, 2.12 (if possible): minor corrections

← Older revision		Revision as of 10:23, 4 May 2023
Line 415:		Line 415:
	== Note tag placement ==		== Note tag placement ==
	=== Notes appertaining to Psalm titles, 2.12 (if possible) ===		=== Notes appertaining to Psalm titles, 2.12 (if possible) ===
	116 Psalms have a canonical title. The file '''kjv.xml''' contains 71 lines that include <code><title.+</note></code>. Within these lines the number of note elements is 101.<ref>Preparing for 2.10 will insert a line feed before ~~the~~ the verse sID element in the XML file. This enables verse 1 for such Psalms to be processed in the same way as all other verses.</ref>		116 Psalms have a canonical title. The file '''kjv.xml''' contains 71 lines that include <code><title.+</note></code>. Within these lines the number of note elements is 101.<ref>Preparing for 2.12 will insert a line feed before the verse '''sID''' element in the XML file. This enables verse 1 for such Psalms to be processed in the same way as all other verses.</ref>

	Study notes appertaining to text within a Psalm title are currently placed at the end of verse 1, just like any other note. To prevent these notes being orphaned when headings are hidden, it is proposed to move these notes to within the title element. As some Psalms also have one or more note appertaining to text within verse 1, this change will require careful manual editing, rather than automating by a script.		Study notes appertaining to text within a Psalm title are currently placed at the end of verse 1, just like any other note. To prevent these notes being orphaned when headings are hidden, it is proposed to move these notes to within the title element. As some Psalms also have one or more note appertaining to text within verse 1, this change will require careful manual editing, rather than automating by a script.

David Haslam: /* Missing Pilcrows, 2.10 */ 2.12

2023-05-04T10:22:16Z

Missing Pilcrows, 2.10: 2.12

← Older revision		Revision as of 10:22, 4 May 2023
Line 528:		Line 528:
	Inserting a space within the Pilcrow marker has been agreed. It should be implemented before the next release. [[User:David Haslam\|David Haslam]] 14:28, 24 January 2016 (MST)		Inserting a space within the Pilcrow marker has been agreed. It should be implemented before the next release. [[User:David Haslam\|David Haslam]] 14:28, 24 January 2016 (MST)

	=== Missing Pilcrows, 2.10 ===		=== Missing Pilcrows, 2.12 ===
	In modern editions of the KJV there are no pilcrows in the NT from Romans through Revelation. The generally accepted view is that the printers ran out of moveable type and just omitted them. Based on the observation that verses with a pilcrow are the same as those that are numbered in chapter descriptions, it's feasible to restore the aforementioned missing pilcrows. The only exception to this rule is that verse 1 in a chapter never has a pilcrow, because the printed editions generally have a large drop capital on the first verse.		In modern editions of the KJV there are no pilcrows in the NT from Romans through Revelation. The generally accepted view is that the printers ran out of moveable type and just omitted them. Based on the observation that verses with a pilcrow are the same as those that are numbered in chapter descriptions, it's feasible to restore the aforementioned missing pilcrows. The only exception to this rule is that verse 1 in a chapter never has a pilcrow, because the printed editions generally have a large drop capital on the first verse.

David Haslam: /* Pilcrow signs, 2.10 */ 2.12

2023-05-04T10:21:55Z

Pilcrow signs, 2.10: 2.12

← Older revision		Revision as of 10:21, 4 May 2023
Line 506:		Line 506:
	[[User:David Haslam\|David Haslam]]		[[User:David Haslam\|David Haslam]]

	== Pilcrow signs, 2.10 ==		== Pilcrow signs, 2.12 ==
	:''This section was moved from [[User:Dmsmith/KJV2011]] – it having never been actioned''. [[User:David Haslam\|David Haslam]]		:''This section was moved from [[User:Dmsmith/KJV2011]] – it having never been actioned''. [[User:David Haslam\|David Haslam]]
	* In printed editions of the KJV, there is normally a space immediately after the ¶. When viewed with PocketSword or Xiphos, there is no such space.<BR>This is not an artifact of how the SWORD engine handles the OSIS markup. Example:		* In printed editions of the KJV, there is normally a space immediately after the ¶. When viewed with PocketSword or Xiphos, there is no such space.<BR>This is not an artifact of how the SWORD engine handles the OSIS markup. Example:

David Haslam: /* XML cosmetic */ 2.12

2023-05-04T10:21:00Z

XML cosmetic: 2.12

← Older revision		Revision as of 10:21, 4 May 2023
Line 445:		Line 445:

	== XML cosmetic ==		== XML cosmetic ==
	For version 2.10 the order of the '''osisID''' and '''sID''' attributes in verse elements will be swapped. This will improve the readability of the OSIS XML file, and conforms to the example given in [[OSIS Bibles]].		For version 2.12 the order of the '''osisID''' and '''sID''' attributes in verse elements will be swapped. This will improve the readability of the OSIS XML file, and conforms to the example given in [[OSIS Bibles]].

	Similar changes:		Similar changes:

David Haslam: /* Notes appertaining to Psalm titles, 2.10 (if possible) */ 2.12

2023-05-04T10:20:32Z

Notes appertaining to Psalm titles, 2.10 (if possible): 2.12

← Older revision		Revision as of 10:20, 4 May 2023
Line 414:		Line 414:

	== Note tag placement ==		== Note tag placement ==
	=== Notes appertaining to Psalm titles, 2.10 (if possible) ===		=== Notes appertaining to Psalm titles, 2.12 (if possible) ===
	116 Psalms have a canonical title. The file '''kjv.xml''' contains 71 lines that include <code><title.+</note></code>. Within these lines the number of note elements is 101.<ref>Preparing for 2.10 will insert a line feed before the the verse sID element in the XML file. This enables verse 1 for such Psalms to be processed in the same way as all other verses.</ref>		116 Psalms have a canonical title. The file '''kjv.xml''' contains 71 lines that include <code><title.+</note></code>. Within these lines the number of note elements is 101.<ref>Preparing for 2.10 will insert a line feed before the the verse sID element in the XML file. This enables verse 1 for such Psalms to be processed in the same way as all other verses.</ref>

David Haslam: /* Unmatched catchWord text, 2.10 (if possible) */ 2.12

2023-05-04T10:20:14Z

Unmatched catchWord text, 2.10 (if possible): 2.12

← Older revision		Revision as of 10:20, 4 May 2023
Line 342:		Line 342:
	[[User:David Haslam\|David Haslam]]		[[User:David Haslam\|David Haslam]]

	=== Unmatched catchWord text, 2.10 (if possible) ===		=== Unmatched catchWord text, 2.12 (if possible) ===
	A systematic analysis of catchWord text has enabled us to identify 10 notes where the catchWord does not properly match to the verse text. Here are the results:		A systematic analysis of catchWord text has enabled us to identify 10 notes where the catchWord does not properly match to the verse text. Here are the results:
	{\| class="wikitable"		{\| class="wikitable"

David Haslam: /* Note punctuation, 2.10 */ 2.12

2023-05-04T10:19:54Z

Note punctuation, 2.10: 2.12

← Older revision		Revision as of 10:19, 4 May 2023
Line 330:		Line 330:
	[[User:David Haslam\|David Haslam]]		[[User:David Haslam\|David Haslam]]

	=== Note punctuation, 2.10 ===		=== Note punctuation, 2.12 ===
	Every margin note in the Blayney 1769 Oxford Edition ends in a full stop. Compare this to what we have. We are missing the full stop for most notes. [[User:David Haslam\|David Haslam]]		Every margin note in the Blayney 1769 Oxford Edition ends in a full stop. Compare this to what we have. We are missing the full stop for most notes. [[User:David Haslam\|David Haslam]]

David Haslam: /* catchWord osisRef, 2.10 */ 2.12

2023-05-04T10:19:37Z

catchWord osisRef, 2.10: 2.12

← Older revision		Revision as of 10:19, 4 May 2023
Line 320:		Line 320:
	-----		-----

	=== catchWord osisRef, 2.10 ===		=== catchWord osisRef, 2.12 ===
	We might further enhance the study notes by adding a suitable '''osisRef''' to each '''catchWord''' element.<ref>Unless we can use (e.g.) <code>osisRef="Ps.40.0"</code> to point to a Psalm title, notes appertaining to such titles would need to be excluded.</ref> '''Fine grain references''' could be used to locate the catchWord text.<ref>See page 91 in the '''OSIS 2.1 User Manual'''</ref>		We might further enhance the study notes by adding a suitable '''osisRef''' to each '''catchWord''' element.<ref>Unless we can use (e.g.) <code>osisRef="Ps.40.0"</code> to point to a Psalm title, notes appertaining to such titles would need to be excluded.</ref> '''Fine grain references''' could be used to locate the catchWord text.<ref>See page 91 in the '''OSIS 2.1 User Manual'''</ref>
	* For a single keyword<ref>Including words 'hyphenated' using the en dash and words containing the right single quotation mark used as an apostrophe.</ref><ref>Care would be required when the catchWord text ends with an ellipsis and when the text includes the divineName element.</ref><ref>With some ingenuity, this could be extended to a word preceded only by the definite or indefinite article, etc.</ref>, we could use the <code>@s[word]</code> operator to search for the keyword in the verse text.<ref>This will only find the first occurrence of the word.</ref>		* For a single keyword<ref>Including words 'hyphenated' using the en dash and words containing the right single quotation mark used as an apostrophe.</ref><ref>Care would be required when the catchWord text ends with an ellipsis and when the text includes the divineName element.</ref><ref>With some ingenuity, this could be extended to a word preceded only by the definite or indefinite article, etc.</ref>, we could use the <code>@s[word]</code> operator to search for the keyword in the verse text.<ref>This will only find the first occurrence of the word.</ref>

David Haslam: /* OSIS header */ We should record file history in the OSIS header using the '''revisionDesc''' element.

2016-02-20T21:01:22Z

OSIS header: We should record file history in the OSIS header using the '''revisionDesc''' element.

← Older revision		Revision as of 21:01, 20 February 2016
Line 544:		Line 544:

	The '''description''' should explain all the '''x-prefix''' attribute values used in the body.		The '''description''' should explain all the '''x-prefix''' attribute values used in the body.

			We should record file history in the OSIS header using the '''revisionDesc''' element.

	== See also ==		== See also ==