Re: [sword-devel] Bishop for Android and iOS / JavaScript bindings

Dear Michael, Thanks for the feedback and encouragement. On 03/22/2018 05:54 AM, Michael Johnson wrote: > For what its worth, I tested on 4 platforms: > > * Acer tablet with Android 4.4.2 > * Motorola phone with Android 7.1.1 > * Apple iPad Pro with iOS 11.2.6 > * Apple iPhone 7 plus

Re: [sword-devel] Normalize the search string (comparing front-end apps)

Re case sensitivity, it was just a very simple example of the principle. If it doesn’t find all then the search request and the index were not normalized the same. NFC and NFD are different normalizations. Note, stripping diacritics may be an appropriate normalization. JSword doesn’t properly

[sword-devel] WebAssembly ?

Has anyone any ideas whether SWORD might make good use of WebAssembly ? e.g. In The Bible Tool (aka swordweb)... Best regards, David Sent with [ProtonMail](https://protonmail.com) Secure Email.___ sword-devel mailing list: sword-devel@crosswire.org

Re: [sword-devel] Diatheke ?

No - that makes no difference, neither did using osis2mod version $3431 Salmo de David, cuando huía de delante de Absalom su hijo. Jehová, ¡cuánto se han multiplicado mis enemigos! muchos se levantan contra mí. Muchos dicen de mi alma: No hay para él salud en Dios. Selah. However, examining

Re: [sword-devel] Diatheke ?

On Thu, Mar 22, 2018 at 8:51 AM, David Haslam wrote: > Greg, > > Thanks for the comparison between *KJV* and *SpaRV1909*. > > It seems therefore that I assumed *incorrectly* that the "extra space" > problem was more general, and that *any* module with Psalm titles could >

Re: [sword-devel] Diatheke ?

Greg, Thanks for the comparison between KJV and SpaRV1909. It seems therefore that I assumed incorrectly that the "extra space" problem was more general, and that any module with Psalm titles could be used illustrate it. FYI. Test module SpaRV1865 only exists so far in the text development

Re: [sword-devel] Normalize the search string (comparing front-end apps)

Thanks, DM. My question was not about case-sensitivity, but about Unicode normalization. The main issue is composition vs decomposition and the canonical ordering of diacritics in each glyph. e.g. Suppose the module contains 181 instances of the name "Efraím" which has 6 characters. Suppose a

Re: [sword-devel] Diatheke ?

On Thu, Mar 22, 2018 at 4:01 AM, David Haslam wrote: > Hi Greg, > > With *Plain* output format, there's a minor side effect in the way the > Psalm title was output in the wrong place. > Verse 2 of the same Psalm was output with a *leading space* before the > Reference. > >

Re: [sword-devel] Normalize the search string (comparing front-end apps)

It doesn’t matter that a search doesn’t use Lucene. The principle is the same. The search request has to be normalized to the same form as the searched text. For example a case insensitive search normalizes both to a single case. If it isn’t done, even on the fly, then search will fail at

Re: [sword-devel] Bishop for Android and iOS / JavaScript bindings

For what its worth, I tested on 4 platforms: * Acer tablet with Android 4.4.2 * Motorola phone with Android 7.1.1 * Apple iPad Pro with iOS 11.2.6 * Apple iPhone 7 plus with iOS 11.2.6 Observations: * Search works consistently with eBible.org modules (unlike PocketSword). * Poetry

Re: [sword-devel] Normalize the search string (comparing front-end apps)

Thanks DM, Not all searches make use of the Lucene index ! e.g. In Xiphos, the advanced search panel gives the user a choice of which type of search. Lucene is only one of these mutually exclusive options. btw. Where is it documented that the creation of a Lucene search index normalizes the

Re: [sword-devel] Normalize the search string (comparing front-end apps)

The requirement is not that the search is normalized to nfc but rather that it is normalized the same as the index. This should not be a front end issue. Btw it doesn’t matter how Hebrew is stored in the module. Indexing should normalize it to a form that is internal to the engine. — DM Smith

[sword-devel] Normalize the search string (comparing front-end apps)

Dear all, Not all front-ends automatically normalize the search string to Unicode NFC. e.g. - Eloquent does - Xiphos does not The data is incomplete for this feature in the table in our wiki page. https://wiki.crosswire.org/Choosing_a_SWORD_program#Search_and_Dictionary Please would other

Re: [sword-devel] Diatheke ?

Hi Greg, With Plain output format, there's a minor side effect in the way the Psalm title was output in the wrong place. Verse 2 of the same Psalm was output with a leading space before the Reference. https://www.dropbox.com/s/uz1amnrp7ez0b4y/Screenshot%202018-03-22%2008.37.42.png?dl=0 This