Re: [sword-devel] GlobalOptionFilter=UTF8GreekAccents and non-Greek modules

The one thing that the Module Team did that should not be done was to use the filter UTF8GreekAccents to detect change and mistakenly conclude that a module being prepared for release contained Greek. This is a simple thing to stop doing, now that we understand in part why the logic is flawed.

Re: [sword-devel] Fwd: Re: NASB status

On Tue, Feb 21, 2017 at 10:09 PM, Matt Zabojnik wrote: > Troy, thank you for that. Quite a bit of thought has gone into this module > before me. > > I have a quick question, not in the form of a challenge, but rather a > humble request for understanding. For your three points,

Re: [sword-devel] Fwd: Re: NASB status

Troy, thank you for that. Quite a bit of thought has gone into this module before me. I have a quick question, not in the form of a challenge, but rather a humble request for understanding. For your three points, why is 1. important? Why is a scripted, reproducible method for transforming the

Re: [sword-devel] GlobalOptionFilter=UTF8GreekAccents and non-Greek modules

On 2017-02-21, 01:47 GMT, Troy A. Griffitts wrote: > I would be concerned first that the module was properly encoded UTF-8. It is properly encoded UTF-8. Sources are available at https://gitlab.com/bible_sword/CzeKMS Matěj -- https://matej.ceplovi.cz/blog/, Jabber: mc...@ceplovi.cz GPG

[sword-devel] Fwd: Re: NASB status

Reposting the below message from the last time we visited this. If you wish to see the conversation around this, have a look at the mailman archives here: http://www.crosswire.org/pipermail/sword-devel/2016-January/thread.html Forwarded Message Subject:Re:

Re: [sword-devel] NASB

Thanks for the info, I'm going to labor to convert stuff, and I'm using S3 as my repository for now. I'm completely unaware of any politics surrounding Crosswire/SWORD and any other module format, I just chose Zefania as an example, though I could have mentioned e-sword, kindle, nook, pdf, etc.

Re: [sword-devel] GlobalOptionFilter=UTF8GreekAccents and non-Greek modules

Well, hypothetically, we might be able to make a reasonable attempt to teach the filter when to strip by determine which adjacent character an accent might be modifying and conditionally strip or not strip, but pragmatically, this filter is used to remove Greek accents while searching Greek

Re: [sword-devel] Release Wrapup

On 02/21/2017 02:23 PM, Greg Hellings wrote: > Karl? I feel like he prefers C I write C++ literally every day. But you interact with me only re: Xiphos, which is half C++, half C, and the boundary is unclean. ___ sword-devel mailing list:

Re: [sword-devel] GlobalOptionFilter=UTF8GreekAccents and non-Greek modules

Hypothetical: What about mixed language texts such as a Greek/French lexicon? DM > On Feb 21, 2017, at 4:56 PM, Troy A. Griffitts wrote: > > > Simply don't use the UTF-8 Greek Accent filter on non-Greek texts. As you > have discovered there are accents used in Greek

Re: [sword-devel] NASB

On Tue, Feb 21, 2017 at 3:59 PM, Matt Zabojnik wrote: > The reasons are deep and political. Those who need to know them, already >> know them. > > I appreciate your discretion in your answer. Conversion difficulties was > what I was primarily concerned with, so this is, in a

Re: [sword-devel] NASB

> > The reasons are deep and political. Those who need to know them, already > know them. I appreciate your discretion in your answer. Conversion difficulties was what I was primarily concerned with, so this is, in a sense, good news. The text is under Copyright by Lockman. Distributing the

Re: [sword-devel] GlobalOptionFilter=UTF8GreekAccents and non-Greek modules

Simply don't use the UTF-8 Greek Accent filter on non-Greek texts. As you have discovered there are accents used in Greek which are also used in other languages and adverse effects will be seen for these languages. The bottom line is simple. Only use the UTF-8 Greek Accents filter on UTF-8

Re: [sword-devel] GlobalOptionFilter=UTF8GreekAccents and non-Greek modules

These are the principal diacritics found in Biblical Greek that have to be removed with a UTF8GreekAccents filter. The first five are general accents, not particular to Greek. It's on account of these that the filter should not be applied to non-Greek text. U+0300 ̀ COMBINING GRAVE ACCENT

Re: [sword-devel] NASB

On Tue, Feb 21, 2017 at 2:45 PM, Matt Zabojnik wrote: > Thanks for the info! > > Would you mind explaining in different terms your reason for aborting the > project? I didn't fully understand. Delivering to Lockman wasn't going to > work for some reason? > The reasons are deep

Re: [sword-devel] NASB

Thanks for the info! Would you mind explaining in different terms your reason for aborting the project? I didn't fully understand. Delivering to Lockman wasn't going to work for some reason? I haven't yet started working on this module, but the intent will be mass distribution rather than

Re: [sword-devel] Lucene Complaint

There is another port - lucene++ - that I've read is the reason CLucene was abandoned. It targets compatibility with Lucene 3 vs CLucene's targeting of Lucene 2. It's on github, and its last commit was ~9 months ago. At least it's better than 2013! There's also Apache Lucy, which is a "loose C"

Re: [sword-devel] Lucene Complaint

When I contributed to Lucene (Java version) there were folks there who lurked on the mailing lists that were part of the C port. Anyway, I mention it as searching those lists or signing up and asking questions might give appropriate insight. DM > On Feb 21, 2017, at 12:25 PM, Greg Hellings

Re: [sword-devel] Release Wrapup

> There are a few others of us who know it, and can - in a pinch - make some fixes to it. There are some others in the broader community who are in the C++ world (Jaak, Gary, etc) but none of them are active on the engine for myriad reasons I d be happy if it would be possible to be more active

Re: [sword-devel] Lucene Complaint

On 02/21/2017 03:10 PM, Greg Hellings wrote: > The version currently packaged in Fedora is 1.2.24. Scratch other response -- got confused between mentions of clucene and xapian. Duh. ___ sword-devel mailing list: sword-devel@crosswire.org

Re: [sword-devel] Lucene Complaint

On 02/21/2017 03:10 PM, Greg Hellings wrote: > The version currently packaged in Fedora is 1.2.24. Something is confused. 2.3.3.4 here, along with retro 0.9.21b. $ egrep '^(|mingw.*)clucene' /var/log/rpmpkgs clucene09-core-0.9.21b-16.fc24.i686.rpm clucene09-core-0.9.21b-16.fc24.x86_64.rpm

Re: [sword-devel] Release Wrapup

Regarding SWORD and python, I'll just leave this here: https://gitlab.com/tgc-dk/pysword No, it is *not* backed by anyone but me. And no, it does not implement all the features of libSword, nor is it meant to. Best regards, Tomas Den 21/02/2017 20:52 skrev "Greg Hellings"

Re: [sword-devel] NASB

The Tyndale STEP (the JSword based app) team will be releasing a Tyndale House edition of the NASB as a SWORD module. Dr David Instone-Brewer has let me have a prerelease copy of the module. Here's a line from the .conf file. About=The Holy Bible, New American Standard Version. Copyright 1995

Re: [sword-devel] Lucene Complaint

If memory serves, that was back in pre-1.0 days. The version currently packaged in Fedora is 1.2.24. --Greg On Tue, Feb 21, 2017 at 2:06 PM, Karl Kleinpaste wrote: > On 02/21/2017 02:54 PM, Peter von Kaehne wrote: > > Xapian is the new default at svn head > > I

Re: [sword-devel] Lucene Complaint

On 02/21/2017 02:54 PM, Peter von Kaehne wrote: > Xapian is the new default at svn head I experimented with Xapian in Xiphos a couple years ago. The indices it creates are of horrifyingly monstrous size. ___ sword-devel mailing list:

Re: [sword-devel] Lucene Complaint

On 02/21/2017 12:25 PM, Greg Hellings wrote: > This is going to necessitate dropping the package from the MinGW > builds of Sword that I maintain for Fedora which will make future > releases of Xiphos for Windows incapable of offering Lucene based > searching. I will keep using "outdated" MinGW

Re: [sword-devel] Release Wrapup

On Sun, Feb 19, 2017 at 1:52 PM, Matt Zabojnik wrote: > I don't mean to derail this in any way. I've previously only had > experience with HTML/PHP/SQL, and I'm now learning Python (in order to > develop a SWORD-related Android app) > > Would it be beneficial to port the whole

Re: [sword-devel] Lucene Complaint

Really? I know there had been some conversations around Xapian and a brief start on a proof of concept, but I was unaware that it had made it into HEAD or even into living code at all. --Greg On Tue, Feb 21, 2017 at 1:54 PM, Peter von Kaehne wrote: > On Tue, 2017-02-21 at 11:25

Re: [sword-devel] Lucene Complaint

On Tue, 2017-02-21 at 11:25 -0600, Greg Hellings wrote: > > Is there any whiff of hope that we might be willing to move off of > depending on CLucene for advanced search support and onto a project > that has any amount of vitality? > I thought we had? Xapian is the new default at svn head

Re: [sword-devel] Release Wrapup

On Sun, Feb 19, 2017 at 12:06 PM, David Haslam wrote: > Are we any closer to a release of SWORD v1.8 ? > No. I don't think there's been a single commit to the engine since that time. At least, I don't recall seeing any messages float across my desk. > > cf. Troy started

Re: [sword-devel] NASB

Eons ago, Crosswire received permission from Lockman to begin work on an NSAB module that they could commercially deliver to users who paid for it. Many people have tackled the work of performing the conversions from Lockman's internal, proprietary markup to a Sword module. Each one has, for

Re: [sword-devel] GlobalOptionFilter=UTF8GreekAccents and non-Greek modules

A further idiosyncrasy of the UTF8GreekAccents filter that proves to be an interesting clue: It changes U+00BE VULGAR FRACTION THREE QUARTERS ¾ to ordinary 3/4. Vulgar fractions are about as far as you can get from Koine Greek, nicht wahr? This is what I think this proves: It must first

[sword-devel] NASB

What's the status on the NASB module? I saw it mentioned in the dictionary message. This is the first I've heard of it, being new to sword devel. I'm currently working to convert NASB with strongs, footnotes and references, but I need to learn OSIS and RegEx better first. Who here is the

[sword-devel] Lucene Complaint

I know it's been mentioned and hinted at in the past, but I wanted to - again - lodge a complaint regarding the inertia of CLucene use in the engine. CLucene's last release, and last git commit on SourceForge was in 2013. It has had none of the language-specific updates that Lucene has generated

Re: [sword-devel] CrossWire Beta | Updates | English | (Easton, Smith, StrongsGreek, StrongsHebrew) ?

On 02/21/2017 08:36 AM, David Haslam wrote: > he dictionary modules StrongsRealGreek and StrongsRealHebrew in > the Xiphos repository are each what one might call a "superset" of > StrongsGreek and StrongsHebrew ? I have no idea of the provenance or content of Strongs{Greek,Hebrew}. My

Re: [sword-devel] CrossWire Beta | Updates | English | (Easton, Smith, StrongsGreek, StrongsHebrew) ?

Karl, Presumably, the dictionary modules StrongsRealGreek and StrongsRealHebrew in the Xiphos repository are each what one might call a "superset" of StrongsGreek and StrongsHebrew ? I don't know whether our good friends at Tyndale House have spotted these yet. Best regards, David -- View

Re: [sword-devel] CrossWire Beta | Updates | English | (Easton, Smith, StrongsGreek, StrongsHebrew) ?

But with the difference that Greg took it upon himself to be the NASB custodian when a certain coder went AWOL. Notwithstanding, it should be feasible to compare each of the four beta modules with the one it's intended to replace. And I suppose, we could enlist help from the experts at Tyndale

Re: [sword-devel] GlobalOptionFilter=UTF8GreekAccents and non-Greek modules

Further proof (specially for Peter) As far as I know, Luther wasn't Greek. A similar experiment with module GerLut1545 showed that all the umlauts are removed by the UTF8GreekAccents filter. diff B S:/Export/GerLut1545/2014-01-17/GerLut1545.diatheke.character.frequency.txt

Re: [sword-devel] CrossWire Beta | Updates | English | (Easton, Smith, StrongsGreek, StrongsHebrew) ?

Oh, indeed.   Von: "Karl Kleinpaste" On 02/21/2017 07:14 AM, Peter Von Kaehne wrote: I suppose we could simply move them over and see who complains. That novel attitude could be applied as well to NASB, and has been suggested exactly as such repeatedly in the past.

Re: [sword-devel] CrossWire Beta | Updates | English | (Easton, Smith, StrongsGreek, StrongsHebrew) ?

On 02/21/2017 07:14 AM, Peter Von Kaehne wrote: > I suppose we could simply move them over and see who complains. That novel attitude could be applied as well to NASB, and has been suggested exactly as such repeatedly in the past. But the naysayers have prevailed every time the matter has come

Re: [sword-devel] CrossWire Beta | Updates | English | (Easton, Smith, StrongsGreek, StrongsHebrew) ?

They were the brainchild of Chris and I would not even know what to look for in terms of testing them. I suppose we could simply move them over and see who complains. Peter > Gesendet: Dienstag, 21. Februar 2017 um 12:04 Uhr > Von: "David Haslam" > An:

[sword-devel] CrossWire Beta | Updates | English | (Easton, Smith, StrongsGreek, StrongsHebrew) ?

Is there any reason why these four dictionary modules may not be moved from CrossWire Beta to CrossWire Main ? CrossWire Beta | Dictionary | English | (Easton, Smith, StrongsGreek, StrongsHebrew) ? Best regards, David -- View this message in context:

Re: [sword-devel] GlobalOptionFilter=UTF8GreekAccents and non-Greek modules

Let's hear it from some of the coders, please. I'd be way out of my depth if I dived into C++ at my age. My IT skills are better devoted to testing and reporting issues. Best regards, David -- View this message in context:

Re: [sword-devel] GlobalOptionFilter=UTF8GreekAccents and non-Greek modules

The filter is located in sword/src/modules/filters and is actually reasonably straightforward to read IIRC. Having said this, IU have stared at it many times in the past and never saw what was wrong. Peter > Gesendet: Dienstag, 21. Februar 2017 um 10:40 Uhr > Von: "David Haslam"

Re: [sword-devel] GlobalOptionFilter=UTF8GreekAccents and non-Greek modules

Hi Peter, I'm sure that your method should work correctly for the UTF-8 Arabic and Hebrew filters, since AFAIK, and as per my limited amount of testing yesterday, those filters are well behaved and have restricted scope. If there'd been nothing wrong with UTF8GreekAccents as a filter, then your

Re: [sword-devel] Module upload: CzeCEP

Just installed. This fixes the spurious Greek Accents filter issue in the conf file. NB. There are now two lines with SwordVersionDate= The older one should be removed asap. btw. It may take time for the InstallSize= line to be added by the server. David Screenshot_2017-02-21_10.png

Re: [sword-devel] GlobalOptionFilter=UTF8GreekAccents and non-Greek modules

Thanks David and Troy, What is happening is - my script tests for presence of Greek accents by doing a before-and-after comparison using a Greek accent strip filter. This works beautifully for the Hebrew stuff - vowels and breathing marks. It should work for the Greek accent filter. It does

Re: [sword-devel] GlobalOptionFilter=UTF8GreekAccents and non-Greek modules

Further proof if this were even needed: I temporarily added the Greek Accents filter to the conf file for the French Bible module FreBBB. Then I ran diatheke on the module. (i.e. default, without any option "-oa" that would include Greek Accents). It removed all Latin character diacritics:

[sword-devel] Module upload: CzeCEP

Dear All, This is to announce that we have just now uploaded CzeCEP. This is is an updated version of CzeCEP. Many thanks to Matej for the hard work. yours The Module Team P.S.: This email is sent automatically on upload of a new/updated module ___

Re: [sword-devel] GlobalOptionFilter=UTF8GreekAccents and non-Greek modules

Hi Troy, Surely there's no doubt the module source text was correctly encoded as UTF-8 and normalised to NFC? We can examine the output of mod2imp and see that it is. Or am I missing something? mod2imp doesn't change the normalisation form, and I assume it doesn't change the encoding either.