Frontends:Diatheke - Revision history

Refdoc: /* Release history */ This is superfluous here.. The absence of a release version history seems spurious too - the version of the diatheke is the version of the engine.

2018-04-13T17:14:41Z

Release history: This is superfluous here.. The absence of a release version history seems spurious too - the version of the diatheke is the version of the engine.

← Older revision		Revision as of 17:14, 13 April 2018
Line 12:		Line 12:
	* ActiveDiatheke: an ActiveX control (.OCX) interface to SWORD		* ActiveDiatheke: an ActiveX control (.OCX) interface to SWORD
	''The above four are no longer under active development and may even be no longer available''.		''The above four are no longer under active development and may even be no longer available''.

	~~=== Release history ===~~
	~~:''This section needs expanding''.~~
	* Version 4.6 was released during 2013.
	* Version 4.7 was released on Aug 30 2015.
	* Several updates to diatheke have since been made, but the version number was not incremented each time.

	=== How do I get diatheke? ===		=== How do I get diatheke? ===

Refdoc: removed bug reports - this is not the appropriate location and virtually guarantees that the text will again be stale in no time.

2018-04-13T17:13:11Z

removed bug reports - this is not the appropriate location and virtually guarantees that the text will again be stale in no time.

@@ Line 225: / Line 225: @@
 '''Notes:'''
 <references />
 == Tools that use Diatheke ==

Refdoc: /* Redirecting the output */ removed superfluous text - output redirection is not diatheke specific.

2018-04-13T17:11:58Z

Redirecting the output: removed superfluous text - output redirection is not diatheke specific.

← Older revision		Revision as of 17:11, 13 April 2018
Line 222:		Line 222:
	=== Output encodings ===		=== Output encodings ===
	Valid output_encoding values are: Latin1, UTF8 (default), UTF16, HTML, and RTF.<ref>Output encodings determine how any printable non-ASCII characters in the output are encoded.</ref><ref>There is no hyphen in UTF8 or UTF16 even though a hyphen might be expected.</ref>		Valid output_encoding values are: Latin1, UTF8 (default), UTF16, HTML, and RTF.<ref>Output encodings determine how any printable non-ASCII characters in the output are encoded.</ref><ref>There is no hyphen in UTF8 or UTF16 even though a hyphen might be expected.</ref>

	~~=== Redirecting the output ===~~
	It being a command line utility, the output from diatheke can be readily redirected to a file using the normal features of the command shell<ref>Diatheke syntax help may be redirected to a file instead of the '''stderr''' device. In Windows, this redirect uses "2>" instead of ">" or "1>".</ref>. This may be especially useful for (e.g.) a search that has a large number of results.<ref>When using diatheke to search, the results are all output as a single line without any breaks.</ref><ref>Diatheke search results contain only the verse references where the pattern is matched (if any).</ref>

	'''Notes:'''		'''Notes:'''

David Haslam: /* Both editions (Linux & Windows) */ s

2018-04-10T20:12:36Z

Both editions (Linux & Windows): s

← Older revision		Revision as of 20:12, 10 April 2018
Line 239:		Line 239:
	Currently, diatheke does not distinguish different '''highlight types''' in the OSIS '''hi''' element. It treats all such styles as if they were bold by wrapping the text between two asterisks.		Currently, diatheke does not distinguish different '''highlight types''' in the OSIS '''hi''' element. It treats all such styles as if they were bold by wrapping the text between two asterisks.

	Currently, diatheke outputs '''canonical Psalm titles''' ''after'' verse 1 rather than ''before'' verse 1 of the Psalm.<ref>For modules in which Psalms have a translators' ~~decriptive~~ heading as well as the canonical title, this too is output ''after'' verse 1.</ref><ref>This issue is with SWORD and has already been fixed in SVN.</ref>		Currently, diatheke outputs '''canonical Psalm titles''' ''after'' verse 1 rather than ''before'' verse 1 of the Psalm.<ref>For modules in which Psalms have a translators' descriptive heading as well as the canonical title, this too is output ''after'' verse 1.</ref><ref>This issue is with SWORD and has already been fixed in SVN.</ref>

	Search type '''regex''' does not yet properly support UTF-8 encoded text. (See above).		Search type '''regex''' does not yet properly support UTF-8 encoded text. (See above).

David Haslam: /* Both editions (Linux & Windows) */ This issue is with SWORD and has already been fixed in SVN.

2018-04-10T20:10:55Z

Both editions (Linux & Windows): <ref>This issue is with SWORD and has already been fixed in SVN.</ref>

← Older revision		Revision as of 20:10, 10 April 2018
Line 239:		Line 239:
	Currently, diatheke does not distinguish different '''highlight types''' in the OSIS '''hi''' element. It treats all such styles as if they were bold by wrapping the text between two asterisks.		Currently, diatheke does not distinguish different '''highlight types''' in the OSIS '''hi''' element. It treats all such styles as if they were bold by wrapping the text between two asterisks.

	Currently, diatheke outputs '''canonical Psalm titles''' ''after'' verse 1 rather than ''before'' verse 1 of the Psalm.<ref>For modules in which Psalms have a translators' decriptive heading as well as the canonical title, this too is output ''after'' verse 1.</ref>		Currently, diatheke outputs '''canonical Psalm titles''' ''after'' verse 1 rather than ''before'' verse 1 of the Psalm.<ref>For modules in which Psalms have a translators' decriptive heading as well as the canonical title, this too is output ''after'' verse 1.</ref><ref>This issue is with SWORD and has already been fixed in SVN.</ref>

	Search type '''regex''' does not yet properly support UTF-8 encoded text. (See above).		Search type '''regex''' does not yet properly support UTF-8 encoded text. (See above).

David Haslam: /* Both editions (Linux & Windows) */ '''Notes:'''

2018-04-10T20:09:24Z

Both editions (Linux & Windows): '''Notes:''' <references />

← Older revision		Revision as of 20:09, 10 April 2018
Line 242:		Line 242:

	Search type '''regex''' does not yet properly support UTF-8 encoded text. (See above).		Search type '''regex''' does not yet properly support UTF-8 encoded text. (See above).

			'''Notes:'''
			<references />

	==== Bugs ====		==== Bugs ====

David Haslam: /* Both editions (Linux & Windows) */ Currently, diatheke outputs '''canonical Psalm titles''' ''after'' verse 1 rather than ''before'' verse 1 of the Psalm.For modules in which Psalms have a translators' decriptive heading as well as the canonical t

2018-04-10T20:08:26Z

Both editions (Linux & Windows): Currently, diatheke outputs '''canonical Psalm titles''' ''after'' verse 1 rather than ''before'' verse 1 of the Psalm.<ref>For modules in which Psalms have a translators' decriptive heading as well as the canonical t

← Older revision		Revision as of 20:08, 10 April 2018
Line 238:		Line 238:
	* Any '''footnote text''' with the option filter '''-o f''' for footnotes; only a pair of brackets <tt>[]</tt> is output at the location of each note tag.		* Any '''footnote text''' with the option filter '''-o f''' for footnotes; only a pair of brackets <tt>[]</tt> is output at the location of each note tag.
	Currently, diatheke does not distinguish different '''highlight types''' in the OSIS '''hi''' element. It treats all such styles as if they were bold by wrapping the text between two asterisks.		Currently, diatheke does not distinguish different '''highlight types''' in the OSIS '''hi''' element. It treats all such styles as if they were bold by wrapping the text between two asterisks.

			Currently, diatheke outputs '''canonical Psalm titles''' ''after'' verse 1 rather than ''before'' verse 1 of the Psalm.<ref>For modules in which Psalms have a translators' decriptive heading as well as the canonical title, this too is output ''after'' verse 1.</ref>

	Search type '''regex''' does not yet properly support UTF-8 encoded text. (See above).		Search type '''regex''' does not yet properly support UTF-8 encoded text. (See above).

David Haslam: /* Both editions (Linux & Windows) / cut " Any '''canonical Psalm titles''' even with the option filter '''-o h''' for section headings."

2018-04-10T20:04:56Z

Both editions (Linux & Windows): cut "* Any '''canonical Psalm titles''' even with the option filter '''-o h''' for section headings."

← Older revision		Revision as of 20:04, 10 April 2018
Line 234:		Line 234:

	Currently, diatheke does not output:		Currently, diatheke does not output:
	* Any '''canonical Psalm titles''' even with the option filter '''-o h''' for section headings.
	* Any '''pilcrow symbols''' in the KJV Bible or similar modules where these are encoded as a marker attribute in the OSIS '''milestone''' element.		* Any '''pilcrow symbols''' in the KJV Bible or similar modules where these are encoded as a marker attribute in the OSIS '''milestone''' element.
	* Any '''quotation marks''' in modules where these are encoded as a marker attribute in the OSIS '''q''' element.		* Any '''quotation marks''' in modules where these are encoded as a marker attribute in the OSIS '''q''' element.

David Haslam: /* Output formats */ Changed and moved note

2018-04-09T16:58:24Z

Output formats: Changed and moved note

← Older revision		Revision as of 16:58, 9 April 2018
Line 218:		Line 218:

	=== Output formats ===		=== Output formats ===
	Valid output_format values are: CGI, GBF, HTML, HTMLHREF, LaTeX<ref>Only after diatheke version 4.7 – The option LaTeX will produce a compilable document, but may well require tweaking to be usable.</ref>, OSIS, RTF<ref>The output does not include any header lines that would facilitate the output including (e.g.) a font colour table, were the output to be redirected to a Rich Text File. Thus using the output filter '''-o w''' (Red Words of Christ) would require such a header to be added by the user in order to ensure the red letter text can be viewed as such.</ref>, ThML, XHTML, and ~~plain~~<ref>The word ''~~'plain'~~'' here is merely a ''handle'' to distinguish the default from the other '''output formats'''.<BR>It does not imply that the output ''encoding'' is restricted in any way.</ref>~~, and internal (default)~~<ref>The default previously was plain text output.</ref>.		Valid output_format values are: CGI, GBF, HTML, HTMLHREF, LaTeX<ref>Only after diatheke version 4.7 – The option LaTeX will produce a compilable document, but may well require tweaking to be usable.</ref>, OSIS, RTF<ref>The output does not include any header lines that would facilitate the output including (e.g.) a font colour table, were the output to be redirected to a Rich Text File. Thus using the output filter '''-o w''' (Red Words of Christ) would require such a header to be added by the user in order to ensure the red letter text can be viewed as such.</ref>, ThML, XHTML, '''plain''', and ''internal'' (default)<ref>The word ''internal'' here is merely a ''handle'' to distinguish the default from the other '''output formats'''.<BR>It does not imply that the output ''encoding'' is restricted in any way.</ref><ref>The default previously was '''plain''' text output.</ref>.

	=== Output encodings ===		=== Output encodings ===

David Haslam: /* Release history / Several updates to diatheke have since been made, but the version number was not incremented each time.

2018-04-08T16:59:00Z

Release history: * Several updates to diatheke have since been made, but the version number was not incremented each time.

← Older revision		Revision as of 16:59, 8 April 2018
Line 17:		Line 17:
	* Version 4.6 was released during 2013.		* Version 4.6 was released during 2013.
	* Version 4.7 was released on Aug 30 2015.		* Version 4.7 was released on Aug 30 2015.
			* Several updates to diatheke have since been made, but the version number was not incremented each time.

	=== How do I get diatheke? ===		=== How do I get diatheke? ===