Talk:Frontends:FeatureList - Revision history

David Haslam: /* Search for empty verses */ new section

2010-01-09T19:56:59Z

‎Search for empty verses: new section

David Haslam: /* The Tarshish/Tharshish example */ new section

2010-01-09T18:46:45Z

‎The Tarshish/Tharshish example: new section

David Haslam: /* Languages that don't space words? */ Line breaking becomes more difficult .....

2010-01-09T15:29:59Z

‎Languages that don't space words?: Line breaking becomes more difficult .....

David Haslam: /* Languages that don't space words? */ new section

2010-01-09T14:45:47Z

‎Languages that don't space words?: new section

David Haslam: /* Notification of superseded modules that have been replaced by a renamed module? */ new section

2010-01-09T14:19:44Z

‎Notification of superseded modules that have been replaced by a renamed module?: new section

Osk: /* Support for the OSIS transChange tag for attribute types other than "added"? */

2009-07-18T00:56:00Z

‎Support for the OSIS transChange tag for attribute types other than "added"?

David Haslam: /* Support for the OSIS transChange tag for attribute types other than "added"? */ new section

2009-07-17T12:13:18Z

‎Support for the OSIS transChange tag for attribute types other than "added"?: new section

David Haslam: /* IBT software based on SWORD technology */ new section

2009-06-17T12:34:56Z

‎IBT software based on SWORD technology: new section

Osk: /* Other */

2009-06-03T03:11:07Z

‎Other

Jmmorgan at 09:05, 31 May 2009

2009-05-31T09:05:37Z

← Older revision		Revision as of 19:56, 9 January 2010
Line 93:		Line 93:

	Of course, one can find all instances of both Tarshish and Tharshish by a search for 'arshish', but the point in citing this example is that the user may be totally unaware of the variant spelling. [[User:David Haslam\|David Haslam]] 18:46, 9 January 2010 (UTC)		Of course, one can find all instances of both Tarshish and Tharshish by a search for 'arshish', but the point in citing this example is that the user may be totally unaware of the variant spelling. [[User:David Haslam\|David Haslam]] 18:46, 9 January 2010 (UTC)
		+
		+	== Search for empty verses ==
		+
		+	Currently to do this requires the use of the separate utility, emptyvss.exe and piping the results to a text file, then editing the file to remove [say] all the OT references for a module that is NT only, then using this as a verse list file that can be opened with a front-end such as Bible Desktop. And for this to be meaningfully useful, the front-end must be capable of displaying Bible modules in parallel, so that the translation with missing verses can be compared with [say] the KJV. [[User:David Haslam\|David Haslam]] 19:56, 9 January 2010 (UTC)

← Older revision		Revision as of 18:46, 9 January 2010
Line 89:		Line 89:

	:"Line breaking becomes more difficult if scripts do not have word breaks, as in Tibetan and Thai, or if the word break is represented by a character rather than a space. Ethiopic is an example of using a character rather than a space: the ''Hulet Neteb'' (፡) is used between words in place of white space, unless there is other punctuation which acts as a word break. (This is also an excellent illustration of how computers have changed a script. With the advent of computing, Ethiopic is now usually written on computer with white space between words. When handwriting, however, people typically still use the ''Hulet Neteb''.)" [http://scripts.sil.org/cms/scrIpts/page.php?site_id=nrsi&item_id=IWS-Chapter09] [[User:David Haslam\|David Haslam]] 15:29, 9 January 2010 (UTC)		:"Line breaking becomes more difficult if scripts do not have word breaks, as in Tibetan and Thai, or if the word break is represented by a character rather than a space. Ethiopic is an example of using a character rather than a space: the ''Hulet Neteb'' (፡) is used between words in place of white space, unless there is other punctuation which acts as a word break. (This is also an excellent illustration of how computers have changed a script. With the advent of computing, Ethiopic is now usually written on computer with white space between words. When handwriting, however, people typically still use the ''Hulet Neteb''.)" [http://scripts.sil.org/cms/scrIpts/page.php?site_id=nrsi&item_id=IWS-Chapter09] [[User:David Haslam\|David Haslam]] 15:29, 9 January 2010 (UTC)
		+
		+	== The Tarshish/Tharshish example ==
		+
		+	Of course, one can find all instances of both Tarshish and Tharshish by a search for 'arshish', but the point in citing this example is that the user may be totally unaware of the variant spelling. [[User:David Haslam\|David Haslam]] 18:46, 9 January 2010 (UTC)

← Older revision		Revision as of 15:29, 9 January 2010
Line 87:		Line 87:

	Q. Which [http://en.wikipedia.org/wiki/Vietnamese_language#Writing_system Vietnamese script] does this observation apply to? [[User:David Haslam\|David Haslam]] 14:45, 9 January 2010 (UTC)		Q. Which [http://en.wikipedia.org/wiki/Vietnamese_language#Writing_system Vietnamese script] does this observation apply to? [[User:David Haslam\|David Haslam]] 14:45, 9 January 2010 (UTC)
		+
		+	:"Line breaking becomes more difficult if scripts do not have word breaks, as in Tibetan and Thai, or if the word break is represented by a character rather than a space. Ethiopic is an example of using a character rather than a space: the ''Hulet Neteb'' (፡) is used between words in place of white space, unless there is other punctuation which acts as a word break. (This is also an excellent illustration of how computers have changed a script. With the advent of computing, Ethiopic is now usually written on computer with white space between words. When handwriting, however, people typically still use the ''Hulet Neteb''.)" [http://scripts.sil.org/cms/scrIpts/page.php?site_id=nrsi&item_id=IWS-Chapter09] [[User:David Haslam\|David Haslam]] 15:29, 9 January 2010 (UTC)

← Older revision		Revision as of 14:45, 9 January 2010
Line 79:		Line 79:

	The conf file has a field that can be used to identify if a module supersedes an earlier module. AFAIK, none of the front-ends pick up this automatically, in order to notify the user that he still has the superseded module (with the older name) installed. This might be a desirable feature. Please discuss. [[User:David Haslam\|David Haslam]] 14:19, 9 January 2010 (UTC)		The conf file has a field that can be used to identify if a module supersedes an earlier module. AFAIK, none of the front-ends pick up this automatically, in order to notify the user that he still has the superseded module (with the older name) installed. This might be a desirable feature. Please discuss. [[User:David Haslam\|David Haslam]] 14:19, 9 January 2010 (UTC)
		+
		+	== Languages that don't space words? ==
		+
		+	One of the search feature bullet points is as follows:
		+
		+	* N-gram searching (needed for languages that don't space words, such as Vietnamese.)
		+
		+	Q. Which [http://en.wikipedia.org/wiki/Vietnamese_language#Writing_system Vietnamese script] does this observation apply to? [[User:David Haslam\|David Haslam]] 14:45, 9 January 2010 (UTC)

← Older revision		Revision as of 14:19, 9 January 2010
Line 75:		Line 75:

	: While front ends have the option to otherwise modify the markup they receive from the engine, transformations such as this are primarily the responsibility of the engine. Front ends using the OSISRTF filter will render all types as italic. Front ends using the OSISHTMLHREF will render "added" and "supplied" (an older form of "added", no longer supported) as italic and "tenseChange" with a preceding asterisk. Practically speaking, I'm unaware of any value other than "added" having ever been employed. So adding support for additional types across the board would be trivial, but we won't do it unless there's an actual need--and then we would need to decide how precisely to render other values distinctly. --[[User:Osk\|Osk]] 00:56, 18 July 2009 (UTC)		: While front ends have the option to otherwise modify the markup they receive from the engine, transformations such as this are primarily the responsibility of the engine. Front ends using the OSISRTF filter will render all types as italic. Front ends using the OSISHTMLHREF will render "added" and "supplied" (an older form of "added", no longer supported) as italic and "tenseChange" with a preceding asterisk. Practically speaking, I'm unaware of any value other than "added" having ever been employed. So adding support for additional types across the board would be trivial, but we won't do it unless there's an actual need--and then we would need to decide how precisely to render other values distinctly. --[[User:Osk\|Osk]] 00:56, 18 July 2009 (UTC)
		+
		+	== Notification of superseded modules that have been replaced by a renamed module? ==
		+
		+	The conf file has a field that can be used to identify if a module supersedes an earlier module. AFAIK, none of the front-ends pick up this automatically, in order to notify the user that he still has the superseded module (with the older name) installed. This might be a desirable feature. Please discuss. [[User:David Haslam\|David Haslam]] 14:19, 9 January 2010 (UTC)

← Older revision		Revision as of 00:56, 18 July 2009
Line 73:		Line 73:

	Do any frontends include support for other transChange types listed above? [[User:David Haslam\|David Haslam]] 12:13, 17 July 2009 (UTC)		Do any frontends include support for other transChange types listed above? [[User:David Haslam\|David Haslam]] 12:13, 17 July 2009 (UTC)
		+
		+	: While front ends have the option to otherwise modify the markup they receive from the engine, transformations such as this are primarily the responsibility of the engine. Front ends using the OSISRTF filter will render all types as italic. Front ends using the OSISHTMLHREF will render "added" and "supplied" (an older form of "added", no longer supported) as italic and "tenseChange" with a preceding asterisk. Practically speaking, I'm unaware of any value other than "added" having ever been employed. So adding support for additional types across the board would be trivial, but we won't do it unless there's an actual need--and then we would need to decide how precisely to render other values distinctly. --[[User:Osk\|Osk]] 00:56, 18 July 2009 (UTC)

← Older revision		Revision as of 12:13, 17 July 2009
Line 59:		Line 59:

	I propose to re-instate an item about the '''MK Holy Bible''' software available from the '''Institute for Bible Translation''' (IBT) that I posted in March, under the heading '''Non-CrossWire Frontends based on SWORD Technology'''. ''There is no ban on reporting this. It is freely advertised on the IBT website, and I also have personal contact with IBT and the program developer''. [[User:David Haslam\|David Haslam]] 12:34, 17 June 2009 (UTC)		I propose to re-instate an item about the '''MK Holy Bible''' software available from the '''Institute for Bible Translation''' (IBT) that I posted in March, under the heading '''Non-CrossWire Frontends based on SWORD Technology'''. ''There is no ban on reporting this. It is freely advertised on the IBT website, and I also have personal contact with IBT and the program developer''. [[User:David Haslam\|David Haslam]] 12:34, 17 June 2009 (UTC)
		+
		+	== Support for the OSIS transChange tag for attribute types other than "added"? ==
		+
		+	In OSIS, there is a <transChange>, translation change, element to indicate a departure from a literal rendering of the source text. This happens most often when words are added to a translation to make the meaning of the text clearer or when the grammatical structures of the translation language do not offer same tenses for example, as the source language. These are entered using the type attribute. If the user encounters a change in translation that is not covered by these values, use the OSIS attribute extension mechanism, "x-" in front of the name of your value for this attribute.
		+	* '''added''' – Words added.
		+	* '''amplified''' – More than addition of words to smooth out a translation.
		+	* '''changed''' – Words are changed in the translation, such as modern spellings.
		+	* '''deleted''' – Words that appear in the original but not in the translation.
		+	* '''moved''' – Words that are moved to better represent the meaning of the text being translated from their original order.
		+	* '''tenseChange''' – Indicates a change of the tense from the original to one that occurs in the translation language.
		+
		+	Most SWORD frontends support the transChange "added" type, by rendering the added words in italics, as in the KJV.
		+
		+	Do any frontends include support for other transChange types listed above? [[User:David Haslam\|David Haslam]] 12:13, 17 July 2009 (UTC)

← Older revision		Revision as of 12:34, 17 June 2009
Line 55:		Line 55:

	Other things are very specific to a particular implementation model, whereas the ideal application might be able to completely skip that model and come up with something more useful (examples being "Users should be able to manage bookmarks in a tree list.", "Search results output to the main window, not just in the search dialog, to allow for saving search results as a "verse list" and utilizing all the features available (such as cross-references and dictionary lookup)" [some of those things can surely be achieved without going into the main window, while others won't necessarily be supported even in the main window], "Hyperlinked scripture references"). -- [[User:Jmmorgan\|Jmmorgan]] 06:39, 30 September 2008 (MDT)		Other things are very specific to a particular implementation model, whereas the ideal application might be able to completely skip that model and come up with something more useful (examples being "Users should be able to manage bookmarks in a tree list.", "Search results output to the main window, not just in the search dialog, to allow for saving search results as a "verse list" and utilizing all the features available (such as cross-references and dictionary lookup)" [some of those things can surely be achieved without going into the main window, while others won't necessarily be supported even in the main window], "Hyperlinked scripture references"). -- [[User:Jmmorgan\|Jmmorgan]] 06:39, 30 September 2008 (MDT)
		+
		+	== IBT software based on SWORD technology ==
		+
		+	I propose to re-instate an item about the '''MK Holy Bible''' software available from the '''Institute for Bible Translation''' (IBT) that I posted in March, under the heading '''Non-CrossWire Frontends based on SWORD Technology'''. ''There is no ban on reporting this. It is freely advertised on the IBT website, and I also have personal contact with IBT and the program developer''. [[User:David Haslam\|David Haslam]] 12:34, 17 June 2009 (UTC)

← Older revision		Revision as of 03:11, 3 June 2009
Line 22:		Line 22:

	::This is true, and of course any bundle must as a whole be available under the GPL v2. As I have stated before, the reason I take the position I have is because I object to other people being attacked because their conscience tells them to use an entirely legal, more permissive license for their own code (such as public domain). -- [[User:Jmmorgan\|Jmmorgan]] 09:05, 31 May 2009 (UTC)		::This is true, and of course any bundle must as a whole be available under the GPL v2. As I have stated before, the reason I take the position I have is because I object to other people being attacked because their conscience tells them to use an entirely legal, more permissive license for their own code (such as public domain). -- [[User:Jmmorgan\|Jmmorgan]] 09:05, 31 May 2009 (UTC)
		+
		+	:::This is a strawman argument. No one has criticized anyone's choice of license for their own work, including more permissive licenses, including licenses such as BSD & public domain. I've written plenty of code under more and less permissive licenses, including plenty of BSD code that I've written for CrossWire specifically. The problem comes when writing code that is not entirely one's own, as is the case with any derivative of Sword, such as any front end that makes uses of any Sword code, including headers or derivatives thereof. These are derivative works under US law and thus must obey the licensing restrictions placed upon them by virtue of their authors' choice to use a GPL component. Any code completely free of Sword code or calls to Sword code may be released under any license its author likes (assuming it is also free of other license encumberances), but that very obviously does cannot constitute a Sword front end. Therefore, all Sword front ends must be GPLv2 licensed, as this page states. --[[User:Osk\|Osk]] 03:11, 3 June 2009 (UTC)

	== Parallel commentaries ==		== Parallel commentaries ==

← Older revision		Revision as of 09:05, 31 May 2009
Line 20:		Line 20:

	:GPLv2 is required of any software using the SWORD library. The intention in picking the GPLv2 was that it was viral and did/does not allow for front-ends to be anything other than GPLv2. Even if the FSF's lawyers say that a front-end can have a license compatible with GPLv2, it does not change the intention. We can easily add such a sentence to clarify our intention. BTW, the goal in all of this is to glorify God.--[[User:Dmsmith\|Dmsmith]] 00:46, 31 May 2009 (UTC)		:GPLv2 is required of any software using the SWORD library. The intention in picking the GPLv2 was that it was viral and did/does not allow for front-ends to be anything other than GPLv2. Even if the FSF's lawyers say that a front-end can have a license compatible with GPLv2, it does not change the intention. We can easily add such a sentence to clarify our intention. BTW, the goal in all of this is to glorify God.--[[User:Dmsmith\|Dmsmith]] 00:46, 31 May 2009 (UTC)
		+
		+	::This is true, and of course any bundle must as a whole be available under the GPL v2. As I have stated before, the reason I take the position I have is because I object to other people being attacked because their conscience tells them to use an entirely legal, more permissive license for their own code (such as public domain). -- [[User:Jmmorgan\|Jmmorgan]] 09:05, 31 May 2009 (UTC)

	== Parallel commentaries ==		== Parallel commentaries ==