Re: [sword-devel] 2TGreek module (versification?)

[Karl Kleinpaste]

On 03/24/2017 05:48 PM, David Haslam wrote:
> How does this work?

2TGreek was created long before av11n, so it depends on basic KJV v11n,
as did the LXX + TischMorph modules which constitute it. Whatever was
(is) in LXX, that's what's in 2TGreek.

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Hebrew OSHB and WLC Bible modules do not fully remove all accenting/diacritics when those settings are turned off?

[Karl Kleinpaste]

On 03/24/2017 01:58 PM, TS wrote:
> as I understand it, Is. 61:1 should not contain any vowel points above the ש 
> "Shin" letters.

Not being a Hebrew reader, I can't tell if the display is fully correct.
I see points above ש but don't know if this is right or wrong. Your
opinion? I've attached with/without screenshots, both vowel points and
cantillation marks.

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] Incomplete StrongsPadding support for RawLD4

[Jaak Ristioja]

Hi!

It seems that back in 2013 SVN 2780 introduced the logic to detect
strongs numbers and add padding:

  commit d35ffd0642aadb2dfb52039cc3081e59e5f48225
  Author: scribe 
  Date:   Fri Feb 1 09:11:52 2013 +

  added ability to turn off logic to detect strongs numbers and add
padding.
  .conf entry:
  StrongsPadding=false

  git-svn-id: https://crosswire.org/svn/sword/trunk@2780
bcd7d363-81e1-0310-97ec-a550e20fc99c


But apparently this commit was incomplete, as it did not put

if (strongsPadding)

before

strongsPad(buf);

in RawLD4::getEntry() and RawLD4::getEntryForKey(). Trivial fix:
https://github.com/swordxx/swordxx/commit/8995c6a316722e0ce3d0776066be482c9df5f712


God bless!
J

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] 2TGreek module (versification?)

[David Haslam]

There is no versification entry in *2tgreek.conf* yet the OT is based on the
LXX.

How does this work?

David



--
View this message in context: 
http://sword-dev.350566.n4.nabble.com/2TGreek-module-versification-tp4657014.html
Sent from the SWORD Dev mailing list archive at Nabble.com.

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Versification for the Complete Wycliffe Bible ?

[David Haslam]

Afterthought:

I will upload my copy of *wycliffe.py* to GitHub at some stage, so that
anyone can clone it and adapt it for other Bibles on Wikisource.

It captures the text from the *Special* download pages and converts each of
them to USFM.

Acknowledgements to Chris Little (more than three years ago).

David



--
View this message in context: 
http://sword-dev.350566.n4.nabble.com/Versification-for-the-Complete-Wycliffe-Bible-tp4657012p4657013.html
Sent from the SWORD Dev mailing list archive at Nabble.com.

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] Versification for the Complete Wycliffe Bible ?

[David Haslam]

The complete 76 book text for the *Wycliffe Bible* is available on Wikisource
at https:\\en.wikisource.org\wiki\Bible_(Wycliffe)

I have already converted the text to USFM and thence to OSIS XML.

The text had not been altered since I previously captured the text in
January 2014.
Back then I merely stopped at USFM and never proceeded to the next stages.

I'm using a modified copy of *wycliffe.py* that Chris created. 
My copy uses the file numbers from the *Identification* page in the *USFM
User Reference*.

We may have got a couple of book names wrong, but before I change anything
at this stage, I am wondering how on earth we can make a module if we don't
have a proper *versification* scheme for this work?

Although Wycliffe's Bible was largely a translation from the Vulgate, using
*Vulg* as the v11n with osis2mod gives far too many errors.

It doesn't recognise these 3 books as valid osisIDs:
* *EsthGr* (16 chapters)
* *EpJer*  (1 chapter)
* *DanGr* (14 chapters)

On top of that, there are 147 Appending entries in the log file.

*EpJer* could be reversified as *Baruch 6*, but that still leaves the other
two unrecognised books.

Do we require a completely new *versification* and therefore must await a
future SWORD release to proceed any further?

If anyone would like to collaborate with me on this, you know how to contact
me.

If we could make a success of this together, it would supersede these two
modules:

* *Wycliffe* in CrossWire Main repo
* *Wycliffe* in eBible.org repo (engWycliffe1395eb)

Both of these have only the Pentateuch and Gospels.

Best regards,

David





--
View this message in context: 
http://sword-dev.350566.n4.nabble.com/Versification-for-the-Complete-Wycliffe-Bible-tp4657012.html
Sent from the SWORD Dev mailing list archive at Nabble.com.

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] OSISVariants & SWORD

[David Haslam]

Tim wrote, "It seems though that if one is viewing the 2TGreek module at the
time of the setting change, it requires changing the Bible being used to a
different one and then back again in order to refresh the display of the
text and have the accents shown."

Got it!

And unlike other filter switches in PocketSword , diacritics are not toggled
by clicking a suitable letter in the module info footer UI.

You have to visit *Preferences*, *Settings*, *Module settings* for each
module in PocketSword to access these controls.

Ah well, you learn something new each day. Thanks Tim.

And now that I can show Greek accents, I confirm that PocketSword displays
the *Secondary reading* in TischMorph in verses such as Luke 3:35.


David

PS. If anyone wishes to look at all the variant readings in this module,
here's a tabbed list.

Luke 3:35   Ραγαῦ
Luke 3:35   Ῥαγαῦ
Luke 5:36   ἀπο
Luke 5:36   ἀπὸ
Luke 10:11  τον
Luke 10:11  τὸν
Luke 12:5   ὑποδειξω
Luke 12:5   ὑποδείξω
Luke 24:2   λιθον
Luke 24:2   λίθον
I Corinthians 2:9   γεγραπται·
I Corinthians 2:9   γέγραπται·
I Corinthians 15:56 ἁμαρτια,
I Corinthians 15:56 ἁμαρτία,
II Corinthians 12:11ἐγω
II Corinthians 12:11ἐγὼ
Revelation of John 8:1  την
Revelation of John 8:1  τὴν
Revelation of John 12:5 ἕτεκεν
Revelation of John 12:5 ἔτεκεν
Revelation of John 14:18τοὶς
Revelation of John 14:18τοὺς






--
View this message in context: 
http://sword-dev.350566.n4.nabble.com/OSISVariants-SWORD-tp4656983p4657011.html
Sent from the SWORD Dev mailing list archive at Nabble.com.

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Hebrew OSHB and WLC Bible modules do not fully remove all accenting/diacritics when those settings are turned off?

[David Haslam]

Afterthought

If Bible students using SWORd front-ends wish to have a further option
filter to hide *Sin Dot* and *Shin Dot*, then technically that's feasible,
but I doubt that SWORD developers will be in a hurry to make this, and
front-end developers may have to wait for a long time.

David



--
View this message in context: 
http://sword-dev.350566.n4.nabble.com/Hebrew-OSHB-and-WLC-Bible-modules-do-not-fully-remove-all-accenting-diacritics-when-those-settings-a-tp4657002p4657010.html
Sent from the SWORD Dev mailing list archive at Nabble.com.

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Hebrew OSHB and WLC Bible modules do not fully remove all accenting/diacritics when those settings are turned off?

[David Haslam]

Tim is correct in his observation as regards the two diacritics on the Hebrew
letter SHIN in modules such as  OSHB.

They are not hidden when the module options are selected to hide them.

Neither the SIN DOT nor the SIN DOT are hidden.

However, his conclusion is unwarranted.

This is not a bug in the filters *UTF8HebrewVowels* or *UTF8Cantillation*.

These diacritics are not Hebrew vowels, neither are they cantillation marks.

*Sin and Shin dot*

שׁ שׂ‎
IPA s, ʃ
Transliteration s, sh
English example sought, shot
Sin Dot
יִשְׂרָאֵל ‎
The word Israel in Hebrew, Yisrael. The upper left hand dot on the Sin is a
Sin dot.
Shin Dot
יֵשׁ ‎
The Hebrew word yesh, there is. The upper right hand dot on the Shin is a
Shin dot.

The Hebrew letter represents two different phonemes: a sibilant /s/, like
English sour, and a /ʃ/, like English shoe. The two are distinguished by a
dot above the left-hand side of the letter for /s/ and above the right-hand
side for /ʃ/. In the biblical name Issachar (Hebrew: יִשָּׂשכָר‎) only, the
second sin/shin letter is always written without any dot, even in fully
vocalized texts. This is because the second sin/shin is always silent.

From https://en.wikipedia.org/wiki/Shin_(letter)#Sin_and_Shin_Dot

Best regards,

David





--
View this message in context: 
http://sword-dev.350566.n4.nabble.com/Hebrew-OSHB-and-WLC-Bible-modules-do-not-fully-remove-all-accenting-diacritics-when-those-settings-a-tp4657002p4657009.html
Sent from the SWORD Dev mailing list archive at Nabble.com.

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Hebrew OSHB and WLC Bible modules do not fully remove all accenting/diacritics when those settings are turned off?

[David Haslam]

The Aleppo module (as is) has no Hebrew diacritics at all.

Of course, the actual codex should have them, but the module was made from a
digital source that lacked them.

If a better digital source became available, and had diacritics, then we
should rebuild the module.

David



--
View this message in context: 
http://sword-dev.350566.n4.nabble.com/Hebrew-OSHB-and-WLC-Bible-modules-do-not-fully-remove-all-accenting-diacritics-when-those-settings-a-tp4657002p4657008.html
Sent from the SWORD Dev mailing list archive at Nabble.com.

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] OSISVariants & SWORD

[David Haslam]

Whatever one might think as a textual critic about the presence or absence of
diacritical marks in the original Hebrew of the Tanach, there's a strong
sense that such consideration should not come into this technical
discussion.

The simple truth is that each SWORD module aims to reproduce a clearly
specified source text.

So for example, if the WLC, OSHB and MapM modules were made from a source
with vowels and cantillation, so be it, that's what SWORD should have.

The fact that PocketSword doesn't yet have a UI option to hide these
diacritics is not a controlling factor in deciding what the back-end should
be doing.

If you want PocketSword to be able to hide Hebrew vowels and cantillation,
then add these features to the UI.

Likewise, please don't strip the Greek accents from any module merely due to
not yet having the UI option for modules.

Best regards,

David






--
View this message in context: 
http://sword-dev.350566.n4.nabble.com/OSISVariants-SWORD-tp4656983p4657006.html
Sent from the SWORD Dev mailing list archive at Nabble.com.

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] diatheke search type regex and the dot ?

[Jaak Ristioja]

Another possibility is to use Boost.Xpressive [1], which I think
supports the Perl regular expressions at runtime, and also static
regular expressions using C++ syntax:

using namespace boost::xpressive;
// sregex rex = sregex::compile( "(\\w+) (\\w+)!" );
sregex rex = (s1= +_w) >> ' ' >> (s2= +_w) >> '!';

But I suppose you don't want to introduce Boost as a dependency.

J


[1]: http://www.boost.org/doc/libs/1_63_0/doc/html/xpressive.html

On 07.03.2017 03:17, Troy A. Griffitts wrote:
> Yeah, so this page shows that c11x regex is still mostly unsupported in gcc:
> 
> http://gcc.gnu.org/onlinedocs/libstdc++/manual/status.html#status.iso.tr1
> 
> (see section 7)
> 
> And the old school gnu regex we use otherwise I don't think knows
> anything about wide chars.  It simply compares bytes and does have a
> clue if some should be considered part of the same byte.  I suspect that
> because nowhere do we tell it that we're giving it UTF-8.
> 
> Ultimately my hope is that gcc will improve eventually and solve our
> problem for us.  We could use
> 
> We could add an option to use ICU RegexMatcher, but I'm still holding
> out for our compiler.
> 
> Troy
> 
> 
> On 03/06/2017 05:52 PM, Karl Kleinpaste wrote:
>> On 03/06/2017 05:25 PM, Greg Hellings wrote:
>>> being off by 2 would seem strange to me
>> I don't understand this question at all.
>>
>> 0xE2 = 226 = 0342
>> 0x80 = 128 = 0200
>> 0x93 = 147 = 0223
>>
>> There's no off-by error at all.
>>
>> "od" is the "octal dump" tool; given -c, it tries to dump characters,
>> but outside 7-bit ASCII, it still dumps octal.
>>
>> For those familiar with dc(1), this will make sense
>> $ dc
>> 8o
>> 226p
>> 342
>> 128p
>> 200
>> 147p
>> 223
>> 16i
>> 0XE2p
>> 342
>> 0X80p
>> 200
>> 0X93p
>> 223
>>
>> The interesting questions are why C++11 regex can't find /en dash/,
>> and why non-C++11 regex doesn't understand multibyte.
>>
>>
>> ___
>> sword-devel mailing list: sword-devel@crosswire.org
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>> Instructions to unsubscribe/change your settings at above page
> 
> 
> 
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
> 


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] "Search" related problems with regards to accent/diacritic marks in the Hebrew OSHB and WLC

[TS]

I was curious to see if I could use the accent/diacritic marks to my advantage 
to find words with the same markings. I used PocketSword. Clucene is the search 
engine it uses. When I have all the markings turned on in OSHB, copy a word, 
and then try and find the word, I get zero results. If I turn them all off and 
do the same thing, it'll also fail if I have fuzzy search enabled. Since the 
word I chose seemed to have a vowel point on the Shin character (despite the 
markings being turned off) I chose a different word without any markings. 
Searching with that word copied and pasted in kept giving me the same two 
results despite changing different search settings. The verse that I copied it 
from did not appear in the results either. It seemed to only find occurrences 
of the Hebrew word when there was a footnote link right next to the word. 

 With  WLC module: Tried different combinations of fuzzy search, all words, or 
exact phrase and none would give me results from a word with its 
accent/diacritic marks in the text with them. With the marks turned off, with 
fuzzy search set to off and using the  "all words" setting, this does work or 
at least I get results, but I don't offhand know if it's finding all the words 
that it should. If I do the same using a different word without a leftover Shin 
point, then I get zero results no matter what I set it to. In the other module 
I seem to get results which had a footnote link next to them, but I guess this 
module doesn't have footnotes and so nothing was found?

In specific, I had the app opened at Is. 61:1. The words that I used, in order 
were:
לְבַשֵּׂ֣ר
לבשׂר
 ענוים

Do any other frontends have this problem?

-TS

--Sent from phone--
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] Hebrew OSHB and WLC Bible modules do not fully remove all accenting/diacritics when those settings are turned off?

[TS]

I have this problem when using PocketSword. The Aleppo module seems correct 
though. Does anybody else have this problem with any other frontends ? 


For example, as I understand it, Is. 61:1 should not contain any vowel points 
above the ש "Shin" letters. 

-TS

--Sent from phone--
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] OSISVariants & SWORD

[Timothy Shen-McCullough]

It seems that you are correct regarding the rendering of Tisch on PocketSword, 
however if one uses the 2TGreek module which includes Tisch., it does have the 
option to show the Greek accents. It seems though that if one is viewing the 
2TGreek module at the time of the setting change, it requires changing the 
Bible being used to a different one and then back again in order to refresh the 
display of the text and have the accents shown. Both the TR and WHNU modules do 
not seem to have the option to turn on accents. 

Regarding the Hebrew text 2 out of the 3 Bibles that I have loaded, do have the 
options to show the accenting/diacritics type marks as well. The text does not 
need a refresh though like the Tisch. module seems to need. Also, it seems ( 
initially at least) that you are correct in that the default is to not show 
them. 

However, I think I prefer the texts without the accenting/diacritics by 
default, at least on PocketSword. There's a lot of reasons and I currently 
don't have the time to get into them. However, the lack of accents, I think was 
one of the things that attracted me to PocketSword. 

Regarding the Hebrew, unless something has changed relatively recently, the 
iPhone can display the accenting, but, by default, does not have the ability to 
have it inputed. One would need to buy a specialized keyboard from the AppStore 
in order to do that. This is one of the reasons why I think that the default 
should be without the diacritics because if one can't turn them off or the idea 
that it's possible to turn them off does not occur to a user, then they become 
stuck being unable to search the text by entering in Hebrew letters/words. 

Also, unless I'm mistaken, the original Hebrew texts did not have 
diacritics/accents. 

The Hebrew diacritics also introduce other problems as well. If I were to have 
them and not be able to get rid of them, they would interfere with the 
linguistics research/testing that I do and they would interfere with the New 
Testament research that I do. 

I think I'd better end my reply here. I've started to not really be replying to 
the previous post(s), but be writing in general on the matter. I might perhaps 
write more on this matter elsewhere. This subject just happen to hit on a lot 
of things that I have an interest in such as user interface design/appearance, 
language, the Bible, and PocketSword. 

In general, I don't think that I'm disagreeing with David regarding that the 
Sword engine should do properly what the instructions say it should do. It 
should of course do what its documentation says. I think though that some 
discussion should be done regarding details of the matter. 
For example, I think it's possible that Hebrew Old Testament text should by 
default be without accenting/diacritics because it's more faithful to the 
original texts, but for the Greek New Testament it may have originally had 
accenting marks so the opposite in a sense would be true for it's default. This 
is just an example (There's is also different editions and/or versions of texts 
which by their own default may include or not include accents and etc.). I'm 
not right now advocating one or the other. My point though is that in this 
example, the presence of accenting marks would be opposite to  each other. 
Accents are a variant to the Hebrew, but not to the Greek. I think this may be 
reiterating David's question or something implied from it which I think poses 
the question of what is "default", or is there a default? or what system should 
be used? Should all accenting be considered variants? etc. Perhaps even the 
term "variants" should be changed since it may be introducing confusion. 
 I know that for myself my brain keeps getting confused on how can accenting be 
a variant for one thing, but not to the other? Especially I'm confused when 
thinking about it in a computer programming sense because I would expect 
consistency in the meaning of the values being assigned and used. 

Sorry, for any confusion or issues that this email may cause. I'm writing it on 
my phone and so I may not have written this as clearly or as well structured as 
I think I have. 

--Sent from phone--
-TS

--Sent from phone--
> On Mar 24, 2017, at 4:57 AM, David Haslam  wrote:
> 
> Yep, *PocketSword* hides both Hebrew vowels and cantillation. :(
> 
> And then there's *UTF8ArabicPoints*.
> 
> Yet strangely enough, *PocketSword* does show the points in (say) the
> *AraNAV* module.
> There's a strange inconsistency within this topic.
> I suppose this came to the scene later than Greek & Hebrew, and was
> implemented in SWORD more logically as a /subtractive/ filter.
> 
> I've yet to test what diatheke does with option filter *-o p* 
> And I don't suppose anyone has ever tested it on an Arabic/Persian module
> with option *-o r* for Arabic Shaping
> cf. Does any front-end have a UI option to toggle Arabic Shaping?
> 
> As for more than two variants, perhaps we 

Re: [sword-devel] SWORD defaults for subtractive filters

[David Haslam]

One of the /subtractive/ filters is undocumented apart from being mentioned
in *diatheke* CL help.

I have therefore posted a question in this talk page:

https://crosswire.org/wiki/Talk:DevTools:conf_Files#GlobalOptionFilter.3DUTF8ArabicShaping_.3F

David



--
View this message in context: 
http://sword-dev.350566.n4.nabble.com/SWORD-defaults-for-subtractive-filters-tp4656999p4657000.html
Sent from the SWORD Dev mailing list archive at Nabble.com.

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] SWORD defaults for subtractive filters

[David Haslam]

Further to the later part of our discussion about OSIS variants, I have just
added an issue about how SWORD handles subtractive filters in terms of
defaults.

http://tracker.crosswire.org/browse/API-202

Best regards,

David



--
View this message in context: 
http://sword-dev.350566.n4.nabble.com/SWORD-defaults-for-subtractive-filters-tp4656999.html
Sent from the SWORD Dev mailing list archive at Nabble.com.

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] OSISVariants & SWORD

[David Haslam]

Yep, *PocketSword* hides both Hebrew vowels and cantillation. :(

And then there's *UTF8ArabicPoints*.

Yet strangely enough, *PocketSword* does show the points in (say) the
*AraNAV* module.
There's a strange inconsistency within this topic.
I suppose this came to the scene later than Greek & Hebrew, and was
implemented in SWORD more logically as a /subtractive/ filter.

I've yet to test what diatheke does with option filter *-o p* 
And I don't suppose anyone has ever tested it on an Arabic/Persian module
with option *-o r* for Arabic Shaping
cf. Does any front-end have a UI option to toggle Arabic Shaping?

As for more than two variants, perhaps we need to mock up a module with a
third variant just to test what SWORD does.

David



--
View this message in context: 
http://sword-dev.350566.n4.nabble.com/OSISVariants-SWORD-tp4656983p4656998.html
Sent from the SWORD Dev mailing list archive at Nabble.com.

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] OSISVariants & SWORD

[Karl Kleinpaste]

On 03/24/2017 06:25 AM, David Haslam wrote:
> e.g. *For UTF8GreekAccents*, the /default/ ought to be to *show* them,

Also Hebrew vowel points and cantillation.

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] OSISVariants & SWORD

[David Haslam]

Even with only two variants supported by SWORD, it manages to get things
wrong!

e.g. Xiphos has module options for selecting variants:

* Primary reading
* Secondary reading
* All readings

Yet when the user selects *Primary*, the *Secondary* reading is displayed,
and /vice versa/!

This is not a Xiphos issue, but rather a SWORD issue that's "been around
since the start of Net.Time".

I suspect that this is possibly part of a wider topic of what the *defaults*
should be for various option filters.

e.g. *For UTF8GreekAccents*, the /default/ ought to be to *show* them,
especially if a front-end hasn't yet got the UI option to toggle them off
and on.

*PocketSword* is like that! It displays *TischMorph* without accents, so I
can't even tell whether it's displaying primary or secondary variant.

Likewise for *diatheke*, the option filter *-o a* shouldn't be needed except
when the user wishes to *strip* the Greek accents. 

The reason being is that UTF8GreekAccents (like a few similar) is a
*subtractive* filter, unlike Strongs and Morph, etc, which are *additive*.

Please comment.

Best regards,

David




--
View this message in context: 
http://sword-dev.350566.n4.nabble.com/OSISVariants-SWORD-tp4656983p4656996.html
Sent from the SWORD Dev mailing list archive at Nabble.com.

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page