Re: [sword-devel] Creating a "SWORD-over-network" protocol for remote SWORD repo access?

about the possibility of generating all assets (e.g. entries/verses, and possibly multiple different versions thereof) on the server-side statically? Best regards, Jaak Ristioja ___ sword-devel mailing list: sword-devel@crosswire.org http://cro

Re: [sword-devel] Creating a "SWORD-over-network" protocol for remote SWORD repo access?

Hello, +1, however this is not a small feat. Having also considered this, I would like to share some toughts on this topic which I hope you find useful. As far as I understand libsword, it tries to support both FTP and HTTP(S) repositories. * Libsword seems to include a hand-written parser

Re: [sword-devel] Building 1.9.0 against ICU 75

Hi, On 17.06.24 22:29, David "Judah's Shadow" Blue wrote: So my distro (openSUSE Tumbleweed) upgraded to ICU v75.1, this gave me all sorts of linking errors when trying to link BIBISH against sword 1.9.0. So I figured I'd rebuild the library, but now I'm getting compile errors from sword. I'm

Re: [sword-devel] RTF in conf files

When I tried to write a similar parser some years ago (or rewrite the libsword parser(s) in Sword++), I discovered to my dismay that the wiki page is quite insufficient. The lack of a formal specification for the configuration format leads to various serious ambiguities or questions when

Re: [sword-devel] Licensing audit of SWORD for Fedora - sharing results with upstream

there too.) On Fri, Oct 6, 2023 at 1:42 AM Jaak Ristioja wrote: Hi, On 05.10.23 20:59, Aaron Rainbolt wrote: Thanks! If all of the comaintainers for Xiphos and BibleTime are also no longer available or interested, I think it would be helpful if you could go into https://src.fedoraproject.org

Re: [sword-devel] Licensing audit of SWORD for Fedora - sharing results with upstream

.) On Fri, Oct 6, 2023 at 1:42 AM Jaak Ristioja wrote: Hi, On 05.10.23 20:59, Aaron Rainbolt wrote: Thanks! If all of the comaintainers for Xiphos and BibleTime are also no longer available or interested, I think it would be helpful if you could go into https://src.fedoraproject.org/rpms/xiphos

Re: [sword-devel] Licensing audit of SWORD for Fedora - sharing results with upstream

Hi, On 05.10.23 20:59, Aaron Rainbolt wrote: Thanks! If all of the comaintainers for Xiphos and BibleTime are also no longer available or interested, I think it would be helpful if you could go into https://src.fedoraproject.org/rpms/xiphos and https://src.fedoraproject.org/rpms/bibletime and

Re: [sword-devel] failing to install LXX with installmgr

Hi, Hopefully adding something like the following to your ~/.sword/sword.conf might help: [General] TimeoutMillis=1000 Besides myself also having experienced this issue, we've had at least two BibleTime users report the same issue. So if you're interested in more details, please

Re: [sword-devel] About estonian bible

Hello, For copyright questions on the most recent translations you would probably need to contact Eesti Piibliselts (Estonian Bible Society). Maybe they were on vacation during summer. Please see [1] and [2] for contact information. Best regards, J [1]: https://piibliselts.ee/kontakt [2]:

[sword-devel] Parallel display mappings from an UI perspective (was: Module release: LXX)

Hi, Thank you for the background info, Troy! Getting the mappings right is a very difficult problem (at minimum) and I admire all you experts on this. I'm not one, and my connection with versifications and mappings is more from the perspective of a programmer. As multiple parallel display

Re: [sword-devel] #bibletime is now on irc.oftc.net

On 19.05.21 21:39, Jaak Ristioja wrote: Hello! Due to the recent changes at Freenode [1] we have moved the #bibletime IRC channel to the OFTC IRC network. Please see https://www.oftc.net/ for connection details. Best regards, J [1]: https://lwn.net/Articles/856543

[sword-devel] #bibletime is now on irc.oftc.net

Hello! Due to the recent changes at Freenode [1] we have moved the #bibletime IRC channel to the OFTC IRC network. Please see https://www.oftc.net/ for connection details. Best regards, J [1]: https://lwn.net/Articles/856543/ ___ sword-devel

[sword-devel] Memory leak caused by InstallMgr::refreshRemoteSourceConfiguration()

Hello! Valgrind detects a memory leak in Sword 1.9.0 which can be reproduced by running `installmgr -sc` when no "${HOME}/.sword" exists. The bug seems to be caused by the refreshRemoteSourceConfiguration() method of InstallMgr which overwrites sources[is->caption] without freeing the

Re: [sword-devel] Sword for the Blind

Thank you for the offer, but unfortunately we don't currently have the developers or time to do this. -- Best regards, J On 12.02.21 23:52, Don Elbourne wrote: Here is some good info on making Qt programs accessible to the blind https://doc.qt.io/qt-5/accessible.html If interested, one of

Re: [sword-devel] CMake: Sword SVN trunk fails to configure without SVN

d to break the built-in support for skipping problems when not within an svn working directory. Greg, any input on this one? Troy On February 16, 2021 7:07:47 AM MST, Jaak Ristioja wrote: Hello, If changes/fixes to the CMake build system is in queue, please consider taking a look at this Bible

Re: [sword-devel] CMake: Sword SVN trunk fails to configure without SVN

Hello, If changes/fixes to the CMake build system is in queue, please consider taking a look at this BibleTime issue as well. Thanks! Best regards, J On 08.01.21 01:49, Jaak Ristioja wrote: Hello! The capricious CI for BibleTime again fails to build the latest SVN trunk version of Sword

Re: [sword-devel] Questions about input format

Hello, Any info about the crash in BibleTime or info which would help us to reproduce this crash might be very helpful in debugging this crash. I would much appreciate this information and would take a look to see if there's something we could fix in BibleTime. Thanks! Best regards, J On

[sword-devel] CMake: Sword SVN trunk fails to configure without SVN

Hello! The capricious CI for BibleTime again fails to build the latest SVN trunk version of Sword with CMake: -- Found Subversion: /usr/bin/svn (found version "1.9.7") CMake Error at /usr/local/cmake-3.12.4/share/cmake-3.12/Modules/FindSubversion.cmake:99 (message): Command

[sword-devel] Sword SVN trunk fails to build using CMake

Hello and Merry Christmas! :) Today the BibleTime CI system started getting the following errors from CMake when trying to build Sword: CMake Error at cmake/options.cmake:75 (PROCESS_VERSION): PROCESS_VERSION Macro invoked with incorrect arguments for macro named:

Re: [sword-devel] Minor memory leak in diatheke

, but he's been gone now for a while.  Happy for a new owner if you'd like to take it up. On 10/19/20 1:24 PM, Jaak Ristioja wrote: Hello! There is a minor memory leak in utilities/diatheke/diatheke.cpp related to the following allocation when parsing the query key (-k option):     ref

[sword-devel] Missed optimization oppurtunity in FileMgr::getDirList() for WIN32

Hello, The includeSize and includeIsDirectory arguments for FileMgr::getDirList() are not used in the WIN32 implementation, although at least includeSize would be useful, I think. Might this have been an oversight since the introduction of the function in SVN 3760? Best regards, J PS:

Re: [sword-devel] Accidental removal of code in SVN 3754?

Nevermind, I saw you already applied the change. J On 19.10.20 17:35, Jaak Ristioja wrote: Hmm, interesting. It seems that the diff pasted was generated by passing --ignore-space-change and --ignore-all-space to "git show" (e.g. "git show -w -b") which resulted in the ou

Re: [sword-devel] Accidental removal of code in SVN 3754?

of trouble following this code, but certainly a check of len before setting *len seems appropriate.  I will commit it with the patch from your next email. On 10/19/20 2:46 PM, Jaak Ristioja wrote: Hi! It seems that SVN 3754 might accidentally have removed a line of code together with t

[sword-devel] Unused mode argument of FileMgr::hasAccess()

Hello again, and sorry for being a bother! The FileMgr::hasAccess(const char *path, int mode) method does not seem to use the mode parameter passed to it. I suspect it thou. Best regards, J ___ sword-devel mailing list: sword-devel@crosswire.org

[sword-devel] Accidental removal of code in SVN 3754?

Hi! It seems that SVN 3754 might accidentally have removed a line of code together with the preceding comment in SWCompress::setUncompressedBuf(): if (!buf) { buf = (char *)calloc(1,1); // be sure we at least allocate an empty buf for return; direct =

[sword-devel] Minor memory leak in diatheke

Hello! There is a minor memory leak in utilities/diatheke/diatheke.cpp related to the following allocation when parsing the query key (-k option): ref = new char[key.length() + 1]; strcpy (ref, key.c_str()); if (strlen(ref))

Re: [sword-devel] SVN 3813 makes compilation of Sword fail

On 19.10.20 10:22, Jaak Ristioja wrote: Ah indeed, thanks for correcting my incorrect reasoning I did late last night! But you are still relying on implementation-defined behavior here which might not work for every platform, and there might not even be an explicit guarantee it will continue

Re: [sword-devel] SVN 3813 makes compilation of Sword fail

. I had to first cast the pointer to a size_t and then to an int to avoid the compiler error. On October 19, 2020 1:07:48 AM GMT+02:00, Jaak Ristioja wrote: "Added extra cast (int)(size_t) to avoid stupid clang error that doesn't like void * being cast (int) directly to an int." UH-OH

Re: [sword-devel] SVN 3813 makes compilation of Sword fail

tion error.  The Android port uses FTPLib and I just built there successfully with the committed I just pushed.  Thank you Jaak. Troy On 10/18/20 11:57 PM, Jaak Ristioja wrote: Hello! The commit "A bit more work on making it easier to use SWORD in a threadsafe manner." makes compilation

[sword-devel] SVN 3813 makes compilation of Sword fail

Hello! The commit "A bit more work on making it easier to use SWORD in a threadsafe manner." makes compilation of Sword fail: src/mgr/ftplibftpt.cpp: In function ‘int sword::{anonymous}::my_filewriter(netbuf*, void*, size_t, void*)’: src/mgr/ftplibftpt.cpp:52:21: error: cast from ‘void*’ to

Re: [sword-devel] Cross references with Sword 1.9.0RC3

downstream as well. J On 18.10.20 16:40, Jaak Ristioja wrote: Hi! The respective change in Sword is SVN 3753:   https://github.com/bibletime/crosswire-sword-mirror/commit/b684b6f099 It seems that this time we were not lucky to have a SWDEPRECATED alias for the old function name, silently breaking

Re: [sword-devel] Cross references with Sword 1.9.0RC3

Hi! The respective change in Sword is SVN 3753: https://github.com/bibletime/crosswire-sword-mirror/commit/b684b6f099 It seems that this time we were not lucky to have a SWDEPRECATED alias for the old function name, silently breaking API, and hence BibleTime. In theory this silent error

Re: [sword-devel] Abort module installation via API + Custom network timeouts

Thank you, Troy! You wrote in the comment: /** Request nicely to terminate an ongoing transfer. * If threading is a concern, consider calling terminate() from your status reporters * as they are typically the link between the transfer thread and your UI. */ However, if the

Re: [sword-devel] Abort module installation via API + Custom network timeouts

On 08.08.20 10:30, Tobias Klein wrote: > Is there a way to abort a module installation via the SWORD API? > I saw in InstallMgr::installModule that there is some handling for when > the user aborted the process. But it doesn't seem like this is > controlled via the API. "Yes" - see the bool term

Re: [sword-devel] TEI Question

I think what we are seeing in BibleTime can in part also be reproduced by diatheke, for example the output of diatheke -b Cawdrey -f HTMLHREF -k abricot also contains abricotabricot which renders visually as a single bold word "abricotabricot" (without spacing between). For more context,

Re: [sword-devel] Bishop 1.4.0 and SWORD Utility Modules

On 21.03.20 12:37, Cyrille wrote: > @Troy, we have to figure out how to automate the translation with Pootle > or something else like transifex (nice tool but not free). According to the FAQ at the end of https://www.transifex.com/pricing/ Transifex is free for open source projects which "have no

Re: [sword-devel] NA28 shows no verses

On 02.06.20 03:22, Greg Hellings wrote: > On Mon, Jun 1, 2020 at 3:57 PM Troy A. Griffitts > wrote: >> Some of this delay is my fault. The "unique per user" key recognition was >> added to SWORD about 8 months or so and we haven't released a new official >> stable branch yet. trunk is pretty

Re: [sword-devel] [PATCH] Use C++ 11 instead of __{s, u}* typedefs

On 20.06.20 19:56, Adrian Bunk wrote: > Names like __u32 do not pollute the POSIX namespace, > but the Linux kernel uses exactly the same names. > > On some Linux architectures the kernel definitions are different, > e.g. http://tracker.crosswire.org/browse/API-178 Additionally, according to the

[sword-devel] License of SWORD (and BibleTime)

Hello! We're having a small confusion about the license of BibleTime on GitHub: https://github.com/bibletime/bibletime/issues/249 To sum up we are uncertain whether the BibleTime source code is GPL-2.0 only or GPL-2.0 "or later version". I'm writing here to clarify the license of SWORD: Is

[sword-devel] Incorrect FinBiblia encoding?

Hello! A BibleTime user reported an encoding issue when using the FinBiblia module [1]. Seems to be broken for at least BibleTime and Xiphos. When I remove the Encocding=UTF-8 line from ~/.sword/mods.d/finbiblia.conf it seems to work properly. So it seems that it is indeed using a ISO-8859

Re: [sword-devel] Packaging (was: I give up)

On 14.05.20 01:54, Troy A. Griffitts wrote: > Has anyone tried any of the packaging tools based on containers, like > flatpak? BibleTime has. Unfortunately not yet with the latest 3.0 RC 1, but 3.0 beta 2 has them available. Details:

Re: [sword-devel] Sword for the Blind

Hello, On 24.02.20 23:08, Don Elbourne wrote: > Have any of the Sword front-ends been tested to see how well they do > with screen readers, used by the blind and visually impaired? Being involved with the BibleTime frontend, I can say that to my knowledge BibleTime has not been tested. There is

Re: [sword-devel] Using Git for Sword development?

Hi, I believe using submodules for the purpose of protecting parts of a git repository from certain contributors is not a good option. Git submodules seem like a nice concept when observed at a distance, but in my experience submodules have proven to be not versatile at all, working well only in

Re: [sword-devel] How to validate a Sword module unlock key?

Hi! On 12.01.20 20:53, Greg Hellings wrote: > On Sun, Jan 12, 2020 at 10:32 AM Tobias Klein wrote: > >> Hi, >> >> I'm adding Sword module unlock support to Ezra Project and I've been >> wondering how you would validate a given unlock key? >> >> Basically the dialog for entering the unlock key

Re: [sword-devel] Engine personal cipher support / Nestle - Aland 28th ed. German Bible Society

On 31.10.19 01:30, Troy A. Griffitts wrote: Thank you for pointing out one problematic input condition which passes the validation checks already in the code. Your statement that there is no validation on input is incorrect.  There is validation on input.  You found one case which passed those

Re: [sword-devel] Engine personal cipher support / Nestle - Aland 28th ed. German Bible Society

Hello! On 29.10.19 23:42, Troy A. Griffitts wrote: #1 was included as an update to our engine with this commit: commit f4ac4caeacd762c90c2b2cef5755bf745e3a6d58 Author: scribe Date:   Sat Dec 29 21:23:25 2018 +     Added personalization mechanism for cipher keys     git-svn-id:

Re: [sword-devel] ppc64le build error

ply it wholesale to > the Sword engine without some input from people who know more about the > code than I do. It should, however, be workable if Troy doesn't have a more > permanent fix in mind. > > --Greg > > On Wed, Jul 17, 2019 at 4:52 PM Jaak Ristioja wrote: >

Re: [sword-devel] ppc64le build error

In Sword++ we fixed [1] this by using the fixed-width integer types provided by . Note also that some certain names containing underscores are reserved to the C++ implementation [2], e.g. names beginning with underscores and names containing adjacent underscores. Best regards, Jaak [1]: Feel

[sword-devel] RawGenBook KeyType=VerseKey status

Hello, Are there any RawGenBook modules with KeyType=VerseKey around? The CrossWire wiki states that KeyType=VerseKey is "not yet supported and is being developed" [1] but this does not seem to be true, as the VerseTreeKey code has not had any significant changes since 2009. Are there any plans

Re: [sword-devel] Sword front-ends, the clipboard and social media

I'd suggest using CSS with custom element attributes instead, for example: Hallelujah! :) span::before { content: attr(verse-id); vertical-align: super; font-size: 50%; margin: 0 0.4em 0 0; } Christ is risen! Online example: https://jsfiddle.net/23z5n9dc/ Best regards, J

Re: [sword-devel] CrossWire repos?

Have you considered using special index files instead of parsing the Apache directory listings? One example for such an approach are APT repositories. This way Sword repositories could be hosted on any web server, and such breakage can be avoided. J On 08.03.19 03:20, Troy A. Griffitts wrote: >

[sword-devel] RTFHTML filter not escaping HTML entities

ied, wherease they should instead be escaped using , and similar entities. This could allow arbitrary HTML injection from the RTF. J On 30.12.18 23:03, Jaak Ristioja wrote: > Btw, grepping my ~/.sword/mods.d/*.conf shows that tags are used > elsewhere as well, e.g. in About= and Distribu

Re: [sword-devel] UnlockInfo .conf entry

Haslam wrote: > Wouldn’t the points about HTML apply just as equally to the existing > ShortPromo key ? > > Some front-ends already jump to the URL specified in the href, and can open a > browser to do so. > > David > > Sent from ProtonMail Mobile > > On Sun, Dec

Re: [sword-devel] UnlockInfo .conf entry

I like the idea, because it is useful information for the users. Here are some of the thoughts I gathered for this: https://en.wikipedia.org/wiki/Brainstorming;> Why can't the About= entry contain this information? I'm unsure whether "UnlockInfo" is the best name. Is it safe to assume that

Re: [sword-devel] Module version numbers

her adverse effects besides just returning an undefined value. J On 25.09.2018 12:56, Jaak Ristioja wrote: >> Aside: Are there any limits to the number of dot separators in the > Version value, or to the number of digits in total or in any part? >> Would SWORD crash with a bu

Re: [sword-devel] Module version numbers

formance to what should be in the Version key. > > Aside: Are there any limits to the number of dot separators in the Version > value, or to the number of digits in total or in any part? > Would SWORD crash with a buffer overflow were it to encounter an inordinately > long Ver

[sword-devel] Module version numbers

Hello! Most modules include version numbers matching the regular expression ^[0-9]+(\.[0-9]+)*$ However, looking at the .conf files, there are version fields with values also containing dashes: ~/.sword/mods.d $ grep -E 'Version=.*-' * 2tgreek.conf:Version=2.7-120109

Re: [sword-devel] Difference of linkEntry() method between RawCom and RawCom4 classes

Ping. On 17.04.2018 01:13, Jaak Ristioja wrote: > Hello! > > In yet another effort to deduplicate some code in Sword++, I stumbled > upon the following difference between the RawCom and RawCom4 classes: > > -void RawCom::linkEntry(const SWKey *inkey) { > +void RawCom4::

[sword-devel] Difference of linkEntry() method between RawCom and RawCom4 classes

Hello! In yet another effort to deduplicate some code in Sword++, I stumbled upon the following difference between the RawCom and RawCom4 classes: -void RawCom::linkEntry(const SWKey *inkey) { +void RawCom4::linkEntry(const SWKey *inkey) { VerseKey *destkey = (); const VerseKey

Re: [sword-devel] Fixes to versification/av11n.py script in sword-tools repo

On 09.04.2018 08:08, Matěj Cepl wrote: > On 2018-04-08, 16:52 GMT, Jaak Ristioja wrote: >> Sword++ development. This is meant to be an unofficial >> read-only mirror, so please don't submit pull requests. If >> there are any problems with that mirror, please contact me.

Re: [sword-devel] Fixes to versification/av11n.py script in sword-tools repo

On 05.04.2018 11:45, Matěj Cepl wrote: > On 2018-04-05, 02:34 GMT, Greg Hellings wrote: >> Feel free to submit future revisions directly through git. > > ??? There is some git? I thought > https://github.com/refdoc/sword/ could be alive, but > https://github.com/refdoc/sword/pull/1 persuaded

[sword-devel] imp2vs -r command line flag missing usage description

Hello! SVN 3567 with commit message "added new option to imp2vs to allow augmenting a module but replacing entries (-r) instead of appending to end of existing entries" implemented the command line flag -r, but did not introduce a description of this flag in the usage() function. Please add the

Re: [sword-devel] Wiki writers - attention

On 08.01.2018 10:08, Peter von Kaehne wrote: > Please help by keeping contact details etc up date - for your own > projects in particular (Project website, mailing lists, source, covered > platforms) When will the wiki registration be open again? I think I've lost access to my old account,

Re: [sword-devel] Crosswire wiki user account registration

> Subject: [sword-devel] Crosswire wiki user account registration > From: Jaak Ristioja > To: SWORD Developers' Collaboration Forum > CC: > > > Happy new year! > > Since the wiki has been mentioned quite a few times on this mailing > list, I attempted to

Re: [sword-devel] Huge commits in SVN+ possible bug in 1.8.0

On 21.12.2017 15:08, Troy A. Griffitts wrote: > Regarding the for lg, an empty div usually is rendered with > no height but does induce a line break, by default. I didn't want to > force additional vertical whitespace, in the event there was already a > new line. Specifically in this case, this

[sword-devel] Huge commits in SVN+ possible bug in 1.8.0

Hello! The last commit to SVN trunk (3547) on December 10 was a large one. The commit message stated 7 different changes, one of which was "Fixed a ton of initialization bugs in filters". Really nice bug finds! But it was a terrible commit to try to understand. While trying to keep Sword++ in

[sword-devel] crosswire.org HTTPS certificate is expired

..again: Error validating server certificate for 'https://crosswire.org:443': - The certificate has expired. Certificate information: - Hostname: crosswire.org - Valid: from Jul 17 23:58:00 2017 GMT until Oct 15 23:58:00 2017 GMT - Issuer: Let's Encrypt Authority X3, Let's Encrypt, US -

[sword-devel] [PATCH] filters: Fixed a number of buffer overflows due to buffers being too short for sprintf.

Hello! A recent version of GCC discovered a number of exploitable buffer overflows in Sword++. Find as attachment a patch ported for Sword master. J commit 0a78609a1993d1a4a3bf3eebcc1eab3fd30d77e9 Author: Jaak Ristioja <j...@ristioja.ee> Date: Thu Sep 28 08:24:58 2017 +0300 filters:

[sword-devel] SVN 3489 "added describe function to installmgr"

Hi! In function remoteDescribeModule, the second if-statement should probably read: if (!m) { instead of duplicating the first one: if (source == installMgr->sources.end()) { Best regards, J ___ sword-devel mailing list:

Re: [sword-devel] Self signed certs during module install [was: SWORD 1.8.0RC3]

On 26.06.2017 12:38, Troy A. Griffitts wrote: > I'm certainly willing to add a compile flag to enable/disable > self-signed certs. I'm also willing to make this a runtime option for > the client of the library. Beware that the user prompt you added to utilities/installmgr.cpp in SVN 3485 ("Added

Re: [sword-devel] SWORD 1.8.0RC3

r user interaction. > >> Gesendet: Montag, 26. Juni 2017 um 10:04 Uhr >> Von: "Jaak Ristioja" <j...@ristioja.ee> >> An: sword-devel@crosswire.org >> Betreff: Re: [sword-devel] SWORD 1.8.0RC3 >> >> Overriding this setting was never possible

Re: [sword-devel] SWORD 1.8.0RC3

autocorrects. > > > Original Message > Subject: Re: [sword-devel] SWORD 1.8.0RC3 > From: Jaak Ristioja > To: sword-devel@crosswire.org > CC: > > > Sure! Verifying TLS certificates is explicitly disabled the file > > src/mgr/curlhttp

Re: [sword-devel] SWORD 1.8.0RC3

. I would encourage any Debian and/or Ubuntu users to > file bugs against Sword packaging in their environments (if their > maintainer isn't here) and the same for any other distribution users. > > --Greg > > On Sun, Jun 25, 2017 at 6:56 PM, Jaak Ristioja <j...@ristioja.ee >

Re: [sword-devel] SWORD 1.8.0RC3

WMgr instances per thread. But thank you for offering. > Troy > > On June 25, 2017 8:33:53 PM GMT+02:00, Jaak Ristioja <j...@ristioja.ee> > wrote: > > Hi Troy! > > It seems that no fixes from Sword++ were considered for inclusion in SVN > t

Re: [sword-devel] SWORD 1.8.0RC3

Hi Troy! It seems that no fixes from Sword++ were considered for inclusion in SVN trunk, not even the two I explicitly proposed on this list in response to the RC2 announcement: one fixing hangs in front ends and the other fixing a pure security negligence which rendered SSL/TLS susceptible to

Re: [sword-devel] SWORD 1.8.0RC2

Hi! You might want to consider scanning the Sword++ git logs to cherry-pick some fixes back into Sword. For example Sword not verifying TLS certificates with Curl, enabling MiTM attacks [1] (not good to have in persecuted countries), a thread safety issue leading to hangs in front-ends [2],

Re: [sword-devel] Lucene++

On 20.05.2017 21:28, David Haslam wrote: > *Lucene++* is an up to date C++ port of the popular Java Lucene library, a > high-performance, full-featured text search engine. According to GitHub the latest commit was 6aec070 on 25 Mar 2016, and their issue tracker seems to be abandoned by the

[sword-devel] Incomplete StrongsPadding support for RawLD4

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

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

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) >> ' '

Re: [sword-devel] Magic testament numbers in Sword

hapter 1, verse 1. > > If you have a single testament, the module introduction is in that testament. > > But I’ve never seen an example of module or testament intros working. > > DM > >> On Mar 19, 2017, at 5:33 PM, Jaak Ristioja <j...@ristioja.ee> wrote: >

[sword-devel] Difference between RawText::isLinked() and RawText4::isLinked()

Hello! Why does RawText::isLinked() have the line: if (!size1 || !size2) return false; but RawText4::isLinked() doesn't? Best regards, J -bool RawText::isLinked(const SWKey *k1, const SWKey *k2) const { +bool RawText4::isLinked(const SWKey *k1, const SWKey *k2) const { long

[sword-devel] Magic testament numbers in Sword

Hello! I have a question about a magic number in the zVerse, zVerse4, RawVerse and RawVerse4 classes. More precisely, some of their methods take as argument a variable "testmt" of type char. For some methods the code comments states: testmt- testament to find (0 - Bible/module

Re: [sword-devel] Architecture and issues reporting

On 19.02.2017 17:28, David Haslam wrote: > Many of the front-end developers get frustrated when users report software or > module issues that are not caused by any fault in the front-end program. > > Here in this mailing list, most of us are very familiar with the back-end / > front-end

Re: [sword-devel] File sharing website

On 18.02.2017 01:47, ref...@gmx.net wrote: > If you look at the content of the site you link to there is massive > copyright infringement going on. How would you plan to avoid this? As a sidenote, I do hope that this copyright is not a hindrance to the spread of the Gospel and to the kingdom of

Re: [sword-devel] Strange option filters

in > filter is used with the Duke Databank of Papyri as a LocalOptionFilter > (not added to the list of global options presented to the user to > toggle, but can still be toggled programmatically). Hope this helps. > > Troy > > > On 11/30/2016 03:03 PM, Jaak Ristioja w

Re: [sword-devel] Strange option filters

On 27.10.2016 22:54, Jaak Ristioja wrote: > Hi! > > While refactoring some option filters code for Sword++ I found two > strange option filters, GreekLexAttribs and PapyriPlain which inherit > from SWOptionFilter and use SWOptionFilter::SWOptionFilter(). This > behavior was intr

Re: [sword-devel] Are the code libraries which come with the SWORD library such as clucene, zlib, etc. the same as from the source or are they modified?

Hello, TS! On 24.11.2016 04:25, TS wrote: > PS - I remember that Sword++ was switched to being dependent on certain > libraries which I think included clucene and zlib. So, I'm offhand curious as > to how he/they are treating this situation since Linux should be using the > same 64 bit

Re: [sword-devel] #include in xzcomprs.cpp - is this a bug or ?

os, IBT and eBible. I am convinced they will say the same. > > It is unlikely that anyone else has done so, but who knows? I would not worry > about it. > > Peter > > Sent from my phone. Apologies for brevity and typos.On 3 Nov 2016 07:31, Jaak > Ristioja <j...@ristio

Re: [sword-devel] #include in xzcomprs.cpp - is this a bug or ?

I just tried `./configure && make` Sword 1.7.4 and it did compile in xzcomprs.cpp. So I guess the stable releases DO include the experimental code. Usually it helps when experimental features have their own feature branches or similar. This not being a common practice in the Sword project, is

[sword-devel] Strange option filters

Hi! While refactoring some option filters code for Sword++ I found two strange option filters, GreekLexAttribs and PapyriPlain which inherit from SWOptionFilter and use SWOptionFilter::SWOptionFilter(). This behavior was introduced in SVN 1864: commit bdc81675088ca687338ca29acef6c384710b6bcf

Re: [sword-devel] Confusing semantics for FileMgr::existsFile() and FileMgr::existsDir()

> On 10/21/2016 12:56 PM, Jaak Ristioja wrote: >> Hi! >> >> In reality, the FileMgr::existsFile() and FileMgr::existsDir() static >> methods not only check whether a file exists (or is visible to the >> calling process), but also whether the given file is readable

[sword-devel] Confusing semantics for FileMgr::existsFile() and FileMgr::existsDir()

Hi! In reality, the FileMgr::existsFile() and FileMgr::existsDir() static methods not only check whether a file exists (or is visible to the calling process), but also whether the given file is readable, because internally, it uses the ::access system call with mode set to 04 which is R_OK.

Re: [sword-devel] Confusing semantics for SWModule postfix ++/-- operators?

On 19.10.2016 10:43, Peter Von Kaehne wrote: >> Von: "Jaak Ristioja" <j...@ristioja.ee> > >> It seems that the postfix ++/-- operators defined in SWMODULE_OPERATORS >> have prefix ++/-- semantics, > > Can you put this into the bug tracker, too? S

Re: [sword-devel] Infinite loop in SWModule multilemma window search

On 19.10.2016 10:37, Peter Von Kaehne wrote: >> Von: "Jaak Ristioja" <j...@ristioja.ee> >> >> I found an infinite loop in SWModule::search() > > could you please put this onto the bug tracker? Here you go: https://www

[sword-devel] Confusing semantics for SWModule postfix ++/-- operators?

Hello! It seems that the postfix ++/-- operators defined in SWMODULE_OPERATORS have prefix ++/-- semantics, i.e. (module++) is equivalent to (module.increment(1), module). This is probably not the intended behavior. Blessings, J ___ sword-devel

[sword-devel] Infinite loop in SWModule multilemma window search

Hello! I found an infinite loop in SWModule::search() if given argument searchType with magic value of -5. Looking at the commit history, it seems that this "new" search type was added by commit 2214 in December 2008 but the implementation was actually never finished? Blessings, J

Re: [sword-devel] How do you make the Sword framework work in 64bit mode? (My compiler is giving me hundreds of warnings.)

As much as I've personally dealt with these and similar warnings in Sword++, many of them are not trivial to fix and point to several architectural issues. Blessings, J On 14.10.2016 14:15, Manfred Bergmann wrote: > I’m also having tons of warnings when compiling SWORD in Xcode for 64 bit. > The

Re: [sword-devel] swld.cpp at line 111 - is this a bug?

On 12.10.2016 10:02, Manfred Bergmann wrote: > >> Am 12.10.2016 um 08:57 schrieb Jaak Ristioja <j...@ristioja.ee>: >> >> On 12.10.2016 09:37, Manfred Bergmann wrote: >>>> On 12.10.2016 01:08, TS wrote: >>>>> Xcode was warning me that in Poc

Re: [sword-devel] swld.cpp at line 111 - is this a bug?

On 12.10.2016 09:37, Manfred Bergmann wrote: >> On 12.10.2016 01:08, TS wrote: >>> Xcode was warning me that in PocketSword's Sword framework, swld.cpp at >>> line 111 with >>> >>> "delete buf;" >>> may be wrong and it should perhaps be >>> >>> "delete[] buf;" >>> instead. Is this correct? I

Re: [sword-devel] swld.cpp at line 111 - is this a bug?

Hi! On 12.10.2016 01:08, TS wrote: > Xcode was warning me that in PocketSword's Sword framework, swld.cpp at > line 111 with > > "delete buf;" > may be wrong and it should perhaps be > > "delete[] buf;" > instead. Is this correct? I looked at the code and I think Xcode is > correct in that the

  1   2   3   >