Re: [sword-devel] Suggestion for markup of Romans 3:26 in module KJV

David and I’ll look at this soon. We’ll try to figure out how this happened and whether the problem is bigger than this. — DM Smith > On Apr 3, 2021, at 5:40 PM, David Haslam wrote: > >  > Hi Troy, > > I will discuss the reported issue with DM as and when I have e

Re: [sword-devel] How to fix book names in Ukrainian/Russian

I had though about this, but it won’t work as expected. The user should be able to type in such a reference and have it recognized. They’ll expect to type what they think that character should be. For JSword, we try three parsings of the input. First as an osisID (or osisRef). If that fails

Re: [sword-devel] Suggestion for markup of Romans 3:26 in module KJV

Troy, Again, thank you for the emergency fix. My apologies for the error. It’s my bad. It has taken some effort to find when and how it happened. The problem was introduced Feb 2013 by my hand edit to merge empty tags having G3588 with the appropriate having the following position.

Re: [sword-devel] The OSIS abbr element & SWORD ?

JSword shows it with a tooltip of the expansion if provided. In Him, DM > On Apr 9, 2021, at 3:27 AM, David Haslam wrote: > > Does SWORD have a means to show the expansion of an abbreviation for words > marked using the OSIS abbr element? > > If so, does any front-end have UI support

Re: [sword-devel] strongMorph definitions

idl wrote: > > We have Strong's numbers in the OSHB. I assembled the books into a single > file and put the lemmas in SWORD format. I could send it to you, if you want. > It is 3.76 MB zipped. > > David > > On 4/6/2021 10:25 AM, DM Smith wrote: >> That was the ba

Re: [sword-devel] strongMorph definitions

rphologyCodes.html>, that are > applied in the OSHB module and interpreted by the OSHM module. Those could > certainly be applied to the KJVA. > > David > > On 4/5/2021 10:19 AM, DM Smith wrote: >> These are coded to Thayer’s. These have no corresponding module. I’ve had &

Re: [sword-devel] strongMorph definitions

These are coded to Thayer’s. These have no corresponding module. I’ve had discussions with David Instone-Brewer about creating a morphology for Hebrew and mapping them to Thayer's so that we can replace the one with the other. That was years ago and hasn’t come to fruition. DM Smith > On

Re: [sword-devel] Suggestion for markup of Romans 3:26 in module KJV

e/greeknt>. I still have the TR download and the scripts from that change. So with some effort David and I can figure it out. DM > On Apr 3, 2021, at 8:31 PM, DM Smith wrote: > > David and I’ll look at this soon. We’ll try to figure out how this happened > and whether th

Re: [sword-devel] Suggestion for markup of Romans 3:26 in module KJV

David and I’ll look at this soon. We’ll try to figure out how this happened and whether the problem is bigger than this. — DM Smith > On Apr 3, 2021, at 5:40 PM, David Haslam wrote: > > Hi Troy, > > I will discuss the reported issue with DM as and when I have enough free &

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

Yes. SWORD is 2.0 only. JSword is 2.0 or later. > On Jun 6, 2020, at 7:11 AM, ref...@gmx.net wrote: > > I think it is strictly. > > Sent from my mobile. Please forgive shortness, typos and weird autocorrects. > > > Original Message > Subject: [sword-devel] License of SWORD

Re: [sword-devel] Chapter descriptions

%5DAKJV2018%5BPD%5D08-RUT.p.sfm > > <https://github.com/BibleCorps/ENG-B-AKJV2018-pd-PSFM/blob/master/p.sfm/ENG%5BB%5DAKJV2018%5BPD%5D08-RUT.p.sfm> > > > On Sat, May 9, 2020 at 10:51 AM DM Smith <mailto:dmsm...@crosswire.org>> wrote: > See the wiki!!! >

Re: [sword-devel] Chapter descriptions

See the wiki!!! https://wiki.crosswire.org/Osis2mod#Handling_of_Introductions.2C_Titles_and_Inter-Verse_Material DM > On May 9, 2020, at 2:14 AM, David Haslam wrote: > > Discussion starter >

Re: [sword-devel] NASB Psalm titles

While the OSIS spec has one definition of canonical, being part of the published text. Regarding Bibles, Troy pointed out, we use it in the theological sense for Bible modules. There are many versifications that have the canonical titles as verse 1. and what we have as verse 1 to n in verse 2

Re: [sword-devel] NASB Psalm titles

The pre-verse div is a construct by osis2mod. These are milestoned to mark the beginning and end of pre-verse material. DM > On May 8, 2020, at 8:55 AM, David Haslam wrote: > > Is this simply because the OSIS file used for module build made use of the > milestone form of the div element ? >

Re: [sword-devel] NASB Psalm titles

osis2mod preserves properly marked Psalm titles before verse 1 as part of that verse. Other titles (and other pre-verse content) will either be put in verse 0 or in verse 1 based on other considerations. This is documented in the wiki for osis2mod. In Him, DM > On May 8, 2020, at

Re: [sword-devel] SWORD search issue / search type multi Word

With the underlying lucene mechanism you can set the connector to OR or to AND. I believe that OR is the default. With ranked search this works well. In Him, DM > On May 4, 2020, at 4:15 PM, Tobias Klein wrote: > > Hi, > > I have the impression that the SWORD multi word search is

Re: [sword-devel] Status of OSIS?

Can you clarify what you mean by “I’m encoding the entire spec for storage in a source form….”? What has happened so far is that we’ve been responding with the 2006 2.1.1 version of the OSIS Spec. We host the file at https://crosswire.org/osis/OSIS%202.1.1%20User%20Manual%2006March2006.pdf

Re: [sword-devel] Question about backwards compatibility and search index download-ability, especially in relation to low-cost, low-power computers (such as might be in developing countries?)

I maintain JSword. We try to maintain backward compatibility with the lowest common denominator version of Java on devices that are up to 10 years old for computers and 5 years for mobiles. The OS version needs to be vendor supported. Android at this point is our boat anchor. For me the most

Re: [sword-devel] Osis Psalms canonical titles

In the Bible, some translations the Psalm titles stand before verse 1. This is how the KJV does it. Other translations have it as verse 1. osis2mod tries to identify whether a title that stands before verse 1 should be a chapter title (i.e. verse 0) or should be a verse title (i.e. verse 1).

Re: [sword-devel] Question regarding special markup in Psalms and SWModule::stripText

oped a bespoke TextPipe filter > to Restore the IMP file to the original v11n. > > Yet to try it as an input for imp2vs to see which v11n gives the best match. > > Best regards, > > David > > Sent from ProtonMail Mobile > > > On Mon, Mar 18, 2019 at 13:

Re: [sword-devel] Question regarding special markup in Psalms and SWModule::stripText

I took a look at the GBF Plain filter. It does recognize these and is specifically handling them. Basically the plain filter has a little bit of markup: New lines for (this is a hack), , . It will put notes stuff between this is a note, Hebrew Strongs Numbers and Tense become . Everything

Re: [sword-devel] Question regarding special markup in Psalms and SWModule::stripText

Plain GBFPlain is probably not the filter that PocketSword uses. Probably GBFHtmlHRef or GBFHtml. No reason to expect that these independent pieces of software would work the same. In Him, DM > On Mar 18, 2019, at 8:58 AM, David Haslam wrote: > > Hi Troy, > > That does not seem

Re: [sword-devel] Color in osis

> On Mar 17, 2019, at 10:07 AM, Karl Kleinpaste wrote: > > However, for this purpose, the deeper problem is that Sword erroneously > generates self-closing tags, which do not work. Search "html > self-closing div" and discover all the conflicting noise over it. My solution > in Xiphos was

Re: [sword-devel] XHTML vs HTML (was: Color in osis)

> On Mar 17, 2019, at 8:48 PM, Nathan Phillip Brink > wrote: > > Hi Karl, > > On Sun, Mar 17, 2019 at 07:47:22PM -0400, Karl Kleinpaste wrote: >> On 3/17/19 2:44 PM, Nathan Phillip Brink wrote: >>> It sounds like you’re trying to render XHTML using an HTML parser. >> If there is a way to

Re: [sword-devel] Color in osis

JSword has a different mechanism than SWORD to produce HTML. JSword has a bug that prevents it from reading a CSS file, but JSword supplies the mechanism to read the CSS. For SWORD, the different renderers produce different output. Unless all the frontends have settled on the same renderer,

Re: [sword-devel] Platform for the distribution of non-free Sword Modules

For the parser built into Java, the schema (BTW, a nitpick, it’s not a DTD) needs to be local. It will not go across the network to retrieve it. DM Smith > On Mar 15, 2019, at 10:36 AM, David Haslam wrote: > > Ah - but you do have to somewhere have an accessible copy of the

Re: [sword-devel] CrossWire repos?

nMail Mobile > > > On Fri, Mar 1, 2019 at 13:43, DM Smith <mailto:dmsm...@crosswire.org>> wrote: >> >> I’ll look at the server this weekend to see if I can see a problem there. >> >> It’s not the certificate. >> >> — DM Smith >>

Re: [sword-devel] CrossWire repos?

I’ll look at the server this weekend to see if I can see a problem there. It’s not the certificate. — DM Smith From my phone. Brief. Weird autocorrections. > On Mar 1, 2019, at 6:35 AM, David Haslam wrote: > > Not just one device. > > My wife & I each have a

Re: [sword-devel] InstallSize

PM, David Haslam wrote: > > Typo correction. > > Both separators should have been keyed as a comma. > >> InstallSize=1,744,408 > > > Sent from ProtonMail Mobile > > > On Sat, Feb 23, 2019 at 19:21, DM Smith <mailto:dmsm...@crosswire.org&g

Re: [sword-devel] InstallSize

JSword would. It uses a parser to convert it from a string to an integer and it doesn’t understand that format. > On Feb 23, 2019, at 10:00 AM, David Haslam wrote: > > Would SWORD baulk if the InstallSize key contained commas as thousands > separators? e.g. > > InstallSize=1,744.408 > >

Re: [sword-devel] OSIS files with Tables and Nesting warnings from osis2mod

t; > As you approach 'tables' in OSIS, I think you'll find that you won't have a > problem if you consider this the same way, each row is it's own table. > > On Mon, Feb 18, 2019 at 4:54 PM DM Smith <mailto:dmsm...@crosswire.org>> wrote: > When ever a non-milestonable constru

Re: [sword-devel] OSIS files with Tables and Nesting warnings from osis2mod

l with things as they are; not with how we’d like them to be. > > And the tables markup is in the USFM. > > David > > Sent from ProtonMail Mobile > > > On Mon, Feb 18, 2019 at 22:04, DM Smith <mailto:dmsm...@crosswire.org>> wrote: >> >> Don

Re: [sword-devel] OSIS files with Tables and Nesting warnings from osis2mod

Don’t do it. Tables are often used for presentation when they shouldn’t. Tables should be used for tabular data. Basically, nothing should start or end within a verse that is not milestoned or able to be converted to a milestone. In Him, DM > On Feb 18, 2019, at 10:39 AM, David Haslam

Re: [sword-devel] Orphaned verse tags in SWORD modules

osis2mod does not understand the CDATA construct nor does the SWORD parser. The OSIS schema (xsd) defines text as xs:string, not xs:normalizeString. So spaces, tabs and newlines are not to be collapsed or replaced. I think CDATA and #PCDATA is an SGML construct, not an XML one. However,

Re: [sword-devel] XML whitespace - significant and insignificant?

I’d also add that using XSLT can introduce unwanted white space. — DM Smith > On Feb 9, 2019, at 9:41 AM, DM Smith wrote: > > There are several things in play wrt to whitespace in an OSIS document as it > pertains to a CrossWire module rendered by SWORD or JSword to a f

Re: [sword-devel] XML whitespace - significant and insignificant?

whitespace. This poses a problem w RTF renderers when markers are not shown as it show 2 spaces at that point. It’ll be fine in most HTML contexts. If CSS merely hides the marker then it’d may show 2 spaces. — DM Smith > On Feb 9, 2019, at 9:56 AM, David Haslam wrote: > > Thanks DM. > &g

Re: [sword-devel] XML whitespace - significant and insignificant?

There are several things in play wrt to whitespace in an OSIS document as it pertains to a CrossWire module rendered by SWORD or JSword to a frontend. 1) osis2mod’s handling of whitespace. 1a) The parser that osis2mod uses to read the OSIS document is not a validating parser. This means that

Re: [sword-devel] LXX Strongs & Morphology

rphology, whereas TR does. > > John > > > — DM Smith > > From my phone. Brief. Weird autocorrections. > > > > > On Feb 7, 2019, at 3:26 PM, pierre amadio wrote: > > > > > > Hi there ! > > > > > > I find it strange that the LXX module

Re: [sword-devel] LXX Strongs & Morphology

JSword allows the setting of a Greek Mophology module. It doesn’t use the work given in the morph or lemma attributes. Forked XST can provide a different mechanism. — DM Smith From my phone. Brief. Weird autocorrections. > On Feb 7, 2019, at 3:26 PM, pierre amadio wrote: >

Re: [sword-devel] LXX Strongs & Morphology

. It makes assumptions about what is proper in a SWORD module. — DM Smith From my phone. Brief. Weird autocorrections. > On Feb 7, 2019, at 2:39 PM, Dudeck, John wrote: > > Further info: > > I dumped the LXX and TR modules using mod2imp. > > 1) I see that the LXX morphology us

Re: [sword-devel] Q re search indexes

Yes, indexes created can be copied to another device having AndBible. You can contact the current developer of AndBible on how to automate the creation of the indexes using JSword. It will be faster. AndBible has recently changed hands and the creation of AndBible’s Lucene indexes on the

Re: [sword-devel] Q re search indexes

I think AndBible has committed a change to make creation of search indexes be the new mechanism. DM > On Feb 4, 2019, at 7:10 PM, Troy A. Griffitts wrote: > > Ah, read more closely... You are asking about creating search indices for > DOWNLOAD. > > There is no good answer to this. We don't

Re: [sword-devel] Q re repository access ftp or https

AndBible needs Http(s). — DM Smith. > On Feb 4, 2019, at 6:37 PM, Dudeck, John wrote: > > Another question: > > Does a repository need to have http/https access or is ftp sufficient? > > Do the various front end module managers do http/https? > > Thanks. &g

Re: [sword-devel] Mobile JiM - Client for Atlassian JIRA

Sure. That’s me. I’ll first have to update Jira to the latest-and-greatest. I’ll announce when that’s done and then you can remind me of that and any others that you’ve mentioned before such as git integration. DM > On Feb 2, 2019, at 2:04 PM, David Haslam wrote: > > Please would our Jira

Re: [sword-devel] Kjva v11n

Yes it is correct. The prayer has no verse numbers in the printed 1st edition. In Him, DM Smith > On Jan 31, 2019, at 5:08 AM, Cyrille wrote: > > Hello, > Is the number "1" right in the kjva v11n for the Prayer of Manasses? > > > > _

Re: [sword-devel] Markdown?

Changes need to be added to the engine first. No sense having a module that would otherwise work on an earlier version of the engine be blocked by having such a change in the conf. Then the question of which markdown and of that what subset. We’ve had support for other compression types for

Re: [sword-devel] [sword-support] oshb 2.0 module: bug tracker

Thanks for giving the page with the broken url. It has been many years since it was at that url. It was moved to crosswire.org/tracker and a redirect from bugs went there. When we changed the url to tracker.crosswire.org we put a redirect from the prior and removed the older redirect. — DM

Re: [sword-devel] Second versions, Scottish Metric Psalter

from a single xml doc using a filter (e.g. XSLT) to produce subsets. Examples, with Apocrypha, without such, long s variant, . I already have a couple of XSLT filters that others requested: no notes or Strong’s numbers; Plaintext. In Him, DM Smith > On Jan 12, 2019, at 7:38 AM, Da

Re: [sword-devel] PocketSword search indices

I think I’ve narrowed down the problem. More later. — DM Smith From my phone. Brief. Weird autocorrections. > On Jan 6, 2019, at 10:05 AM, DM Smith wrote: > > Nic is in the process of moving and that might affect his availability. > > I’ve PocketSword and access to the

Re: [sword-devel] Remarks before [ModuleName] ?

users. — DM Smith From my phone. Brief. Weird autocorrections. > On Jan 7, 2019, at 3:30 AM, David Haslam wrote: > > Thanks Greg, > > DM - does the same hold for JSword ? > > Background: .conf file for module FreBDM1707 has lots of remark lines, with 3 > at th

Re: [sword-devel] PocketSword search indices

Nic is in the process of moving and that might affect his availability. I’ve PocketSword and access to the logs. I’ll look to see what I can figure out. Yesterday Peter, Troy and I worked on fixing the server module issues. I’m certain there’s more we will discover. Like this. — DM Smith From

Re: [sword-devel] Module upload: JapDenmo

Peter and I spent some time on this today. More to do. Let me know if the vlsJoNT is visible now. BTW, the extraneous emails regarding a new module were part of testing fixes. DM > On Jan 5, 2019, at 9:43 AM, DM Smith wrote: > > I appreciate your eagerness and your service. >

Re: [sword-devel] Module upload: JapDenmo

as it changes ownership. DM > On Jan 5, 2019, at 12:00 PM, Peter von Kaehne wrote: > > On Sat, 2019-01-05 at 10:38 -0500, DM Smith wrote: >> Thanks for the info. That’s very helpful. >> >> I’ve a script ~dmsmith/bin/packageModules.sh which will examine a >> repository for

Re: [sword-devel] Module upload: JapDenmo

:10 AM, Peter von Kaehne wrote: > > On Sat, 2019-01-05 at 09:07 -0500, DM Smith wrote: >> There are several parts to this: >> The email is published the moment that the module is put in mods.d >> and module. > > No. It is published on conclusion of a bunch

Re: [sword-devel] Module upload: JapDenmo

nverse > of "crying wolf". > > Best regards, > > David > > Sent with ProtonMail Secure Email. > > ‐‐‐ Original Message ‐‐‐ > On Saturday, 5 January 2019 14:07, DM Smith wrote: > >> I’m very encourage that there’s lots of interest in the mod

Re: [sword-devel] Module upload: JapDenmo

I’m very encourage that there’s lots of interest in the module making process. If I can help maintain that momentum, I will. I’ve privately asked Peter, in response to his lament about the problem, for specific things he wants fixed. I have not heard back from him. It is now early morning for

Re: [sword-devel] Short/Long Bible & Commentary Modules

earlier). > I never compile any programs from source. > > Best regards, > > David > > Sent with ProtonMail <https://protonmail.com/> Secure Email. > > ‐‐‐ Original Message ‐‐‐ > On Wednesday, 2 January 2019 13:47, DM Smith wrote: > >> Whe

Re: [sword-devel] Short/Long Bible & Commentary Modules

> NB. I do not understand how there can be any "extra verses" in a module if > there were no APPEND warnings from osis2mod. > > > Best regards, > > David > > Sent with ProtonMail <https://protonmail.com/> Secure Email. > > ‐‐‐ Original Message

[sword-devel] Short/Long Bible & Commentary Modules

I’ve found an oddness in some Bible and commentary modules. (They share the same storage mechanism). For each module there’s an index file for the OT and for the NT. Even many single testament modules have an index file for the other testament. The index file has a slot for every verse in the

Re: [sword-devel] RTFHTML filter not escaping HTML entities

What is the likelihood/risk of an untrustworthy conf? — DM Smith From my phone. Brief. Weird autocorrections. On Dec 30, 2018, at 4:14 PM, Jaak Ristioja wrote: >> It looks like BibleTime, too, is guilty of not properly escaping those. > > Actually it seems that the RTFHTML fil

Re: [sword-devel] UnlockInfo .conf entry

JSword only allows in the fields as documented in the wiki. In other fields it escapes the HTML. The CrossWire repo should not have spurious HTML. — DM Smith From my phone. Brief. Weird autocorrections. > On Dec 30, 2018, at 4:03 PM, Jaak Ristioja wrote: > > Btw, grepping my

Re: [sword-devel] Is there a server outage?

Everything should be working now. > On Dec 18, 2018, at 9:13 AM, DM Smith wrote: > > I’m on my way to work. I’ll see if I can get a moment to look once there. > Those two are different web servers. > > — DM Smith > From my phone. Brief. Weird autocorrections. > >

Re: [sword-devel] Is there a server outage?

I’m on my way to work. I’ll see if I can get a moment to look once there. Those two are different web servers. — DM Smith From my phone. Brief. Weird autocorrections. > On Dec 18, 2018, at 8:13 AM, Tuomas Airaksinen > wrote: > > My observations: > > tracker.crosswire.or

Re: [sword-devel] Modules, Tracker - some remarks

The Internet Wayback Machine is useful for dead URLs. I’ve used it to find resources no longer available and to make contact w people. — DM Smith From my phone. Brief. Weird autocorrections. > On Dec 2, 2018, at 10:47 AM, "ref...@gmx.net" wrote: > > Regarding how to find

Re: [sword-devel] Issue in AraNav (New arabic version)

The website is mis-configured. It should result in a 404 NOT FOUND. bugs.crosswire.org has never been an URL for the bugs/tracker. DM > On Dec 1, 2018, at 7:56 AM, Karl Kleinpaste wrote: > > On 12/1/18 4:24 AM, Tuomas Airaksinen wrote: >> where is bug tracker? >

Re: [sword-devel] Issue in AraNav (New arabic version)

RL for our issues tracker is now > https://tracker.crosswire.org/ <https://tracker.crosswire.org/> > > I'm sure DM Smith can confirm this, as it was he that made the change from > the tracker being on a directory under crosswire.org/ > After he made this change, I

Re: [sword-devel] Problem with verse range linking osis2mod Windows v3431

The 32-bit was an earlier version. I don’t think the bit-ness matters. — DM Smith > On Nov 24, 2018, at 6:23 AM, David Haslam wrote: > > So the reported bug arises only from the 64 bit compilation of osis2mod.exe > for Windows? > > Have I got this right? > > AFA

Re: [sword-devel] Problem with verse range linking osis2mod Windows v3431

I’m on holiday and won’t be able to look at this for a while. I don’t know if someone else can sooner. Either way having your minimal test file would help. — DM Smith From my phone. Brief. Weird autocorrections. > On Nov 21, 2018, at 8:03 PM, Dudeck, John wrote: > > Greetings, &g

Re: [sword-devel] How are linked verses encoded in our modules?

And for an arbitrary reference you may have to check the previous verses, too. — DM Smith > On Nov 15, 2018, at 9:05 AM, Greg Hellings wrote: > > In the olden days this was detected by incrementing to the next verse, > calling renderText(), and doing a string compar

Re: [sword-devel] Search error in PocketSword for ancient Greek text

The SimpleAnalyzer does not “fold” these to the same value. If the text has a mix of upper and lower Greek, it uses latin to_upper to convert, which won’t. For JSword, we pick an analyzer based upon the text’s script/language. In Him, DM > On Nov 1, 2018, at 5:21 PM, Tom Sullivan

Re: [sword-devel] Does the CLucene indexing work for non-English texts?

From memory, SWORD uses SimpleAnalyzer. This analyzer works well for Western European languages. It won’t for non-latinate texts. It may work in part. The basic rule of thumb is that both the index has to be created with an analyzer and the search request has to be analyzed the same.

Re: [sword-devel] SWORD search index creation for Khmer, Thai and other languages with no space between words?

I don’t know what SWORD does. JSword uses a Thai word break algorithm that’s part of Lucene. So to do a search, you have to know Thai well enough to know where words break or do an OR search. Don’t remember if JSword does Khmer. Don’t think so. The other technique that is available in Lucene

Re: [sword-devel] Versification test modules in CrossWire Experimental ...

There’s also the need for v11n mapping to the KJV. In Him, DM > On Sep 29, 2018, at 1:09 PM, Andrew T. wrote: > > Is this just a matter of creating the canon_xxx.h files or is there more to > it? I've been playing around with alternate versifications (creating > canon_xxx.h files

Re: [sword-devel] Module version numbers

sting of 1 to 4 parts. * * * Here is the grammar for version strings: * * * version ::= major('.'minor('.'micro('.'nano)?)?)? * major ::= [0-9]+ * minor ::= [0-9]+ * micro ::= [0-9]+ * nano ::= [0-9]+ * * * @see gnu.lgpl.License The GNU Lesser General Public License for details. *

Re: [sword-devel] milestone element, osisRef attribute

Semantics: osisID marks the address of the current item. osisRef points the address of a different item that the current item references. I think that the osis manual gives a suggested mechanism for two v11ns in the same document. My computer is in the shop and I cannot check. — DM Smith From

Re: [sword-devel] Introductory material in OSIS (osis2mod)

is the author but he is unable to work on it. Volunteers are welcome. — DM Smith From my phone. Brief. Weird autocorrections. > On Jun 15, 2018, at 4:19 PM, John Dudeck wrote: > > Ok. I think I just realized where my problem lies. > > In Xiphos, the Introductory material is dis

Re: [sword-devel] Introductory material in OSIS (osis2mod)

I’ll see if I can explain from memory. I’m the most recent contributor to osis2mod. Below “first” means the first encountered. For a complete Bible it is as you’d think, but if there is only one testament or an incomplete testament, first may not refer to Genesis or Matthew. Also, if a book or

Re: [sword-devel] Module upload: FreLXX

JSword doesn’t show/hide “accents”. This is a deliberate design decision. — DM Smith > On Jun 11, 2018, at 7:46 AM, David Haslam wrote: > > Has anything similar been done for the equivalent JSword filter? ___ sword-devel mailing list: sw

Re: [sword-devel] Module upload: FreLXX

I think it is a bug in the SWORD engine if single right quotation mark is seen as a Greek diacritic. Will look later to verify. If it is then the module should not have the option. — DM Smith > On Jun 7, 2018, at 8:54 AM, "ref...@gmx.net" wrote: > > If a Greek accent is

Re: [sword-devel] CrossWire site certificate expired on 4 May

Which url? I thought I got them all earlier today. — DM Smith From my phone. Brief. Weird autocorrections. > On May 30, 2018, at 7:07 AM, David Haslam wrote: > > Modern browsers will not let me connect via HTTPS to the CrossWire wiki (and > other places on the ser

Re: [sword-devel] osisID for merged verses

XML doesn’t allow for an attribute to be listed twice. It will either error or use one. — DM Smith From my phone. Brief. Weird autocorrections. > On May 17, 2018, at 6:10 PM, Michael H <cma...@gmail.com> wrote: > > This is a question: > > Is there anything in

Re: [sword-devel] osisID for merged verses

Yes. Osis2mod should accept a range. — DM Smith From my phone. Brief. Weird autocorrections. > On May 17, 2018, at 3:06 PM, Troy A. Griffitts <scr...@crosswire.org> wrote: > > Hi John, > > Yes, an osisID does not allow a range. I believe our import tool osis2mod >

Re: [sword-devel] osisID for merged verses

osisID doesn’t allow for ranges. Just a space separated list. — DM Smith From my phone. Brief. Weird autocorrections. > On May 17, 2018, at 2:59 PM, John Dudeck <john.dud...@sim.org> wrote: > > Greetings, > > I am trying to create a module for a Bible (French Parole de V

Re: [sword-devel] Android common module storage location

Apparently Troy found a way to search for repositories and use them. AndBible requests a standard storage location from the Android API and uses that. The path is specific to AndBible. I’ll check w Troy to see what he has done. Martin is unable by current job to work on AndBible. I’m trying to

Re: [sword-devel] intro material CSS

I’ll look into updating Osis2mod to not create self-closing divs. — DM Smith From my phone. Brief. Weird autocorrections. > On Apr 9, 2018, at 8:30 AM, Karl Kleinpaste <k...@kleinpaste.org> wrote: > >> On 04/08/2018 02:57 PM, Karl Kleinpaste wrote: >> Anyway... I can

Re: [sword-devel] Front-ends in which search can find words in the canonical Psalm headings?

JSword indexes canonical titles as verse text. — DM Smith From my phone. Brief. Weird autocorrections. > On Apr 4, 2018, at 8:56 AM, David Haslam <dfh...@protonmail.com> wrote: > > I suppose STEP Bible was going to be one most likely to succeed, seeing as > it's whole UI is

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

handle Unicode either. — DM Smith From my phone. Brief. Weird autocorrections. > On Mar 22, 2018, at 9:30 AM, David Haslam <dfh...@protonmail.com> wrote: > > Thanks, DM. > > My question was not about case-sensitivity, but about Unicode normalization. > The main

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

his would occur irrespective of whether > normalization was suppressed during module build? > i.e. With osis2mod option -Ndo not convert UTF-8 or normalize UTF-8 > to NFC > > > Best regards, > > David > > Sent with ProtonMail <https://protonmail.com/&g

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

Re: [sword-devel] The OSIS element inscription ?

iptions > turn up in searches, while they would not otherwise, unless one searches for > capitalized text. > > Sent from my mobile. Please forgive shortness, typos and weird autocorrects. > > > Original Message > Subject: Re: [sword-devel] The OSIS elem

Re: [sword-devel] The OSIS element inscription ?

>> Peter >> >> Sent from my mobile. Please forgive shortness, typos and weird autocorrects. >> >> >> Original Message >> Subject: Re: [sword-devel] The OSIS element inscription ? >> From: DM Smith >> To: David Haslam ,SWORD Developers' Coll

Re: [sword-devel] The OSIS element inscription ?

JSword -> Yes > On Mar 20, 2018, at 11:46 AM, David Haslam wrote: > > No - I was just wondering whether we already did something in either SWORD or > JSword. > > The likelihood is low, and a yes/no answer would suffice. > > cf. Examples of an inscription in Scripture

Re: [sword-devel] osis2mod

the case the module won’t work. Also if you are on a modern version of Windows, you might not have permission to write to c:\Program Files (x86)\CrossWire\The SWORD Project\modules\texts\ztext\ts2009 Hope this helps, DM Smith > On Mar 11, 2018, at 10:00 AM, Johan <joh

Re: [sword-devel] osis2mod

Johan, Please tell us your entire command line. We can then answer your question. — DM Smith > On Mar 11, 2018, at 7:43 AM, Johan <johan.mar...@messianic.co.za> wrote: > > Good day, > > I created a bible module (osis.xml) which I want to convert into a Sword > bibl

Re: [sword-devel] Using Multiple Front-ends

JSword tries to discover all local repositories to present their modules to the user. It will install only to one location. By default, it will use ~/.sword on Un*x. I forget where on modern windows, but it is different than Xiphos. And on Mac it will ~/Library/Application Support/Sword. Just

Re: [sword-devel] Using Multiple Front-ends

As reported earlier, Bishop and And Bible use the same module location on the one device. If you install on one it will be available on the other. I don’t know if a restart is needed by the other app. On Un*x, they are all stored at ~/.sword by default. In Him, DM > On Mar 4, 2018, at

Re: [sword-devel] Using Multiple Front-ends

Correction. Not SWORD_HOME but SWORD_PATH. (Thx Karl. My memory was faulty.) > On Mar 4, 2018, at 8:41 PM, DM Smith <dmsm...@crosswire.org> wrote: > > Depends. iOS requires sandboxing of it’s resources. The desktop applications > use the standard locations which has changed ov

Re: [sword-devel] Using Multiple Front-ends

and modules that all will play well together. You may need to merge different local repos to that new location. In Him, DM Smith > On Mar 4, 2018, at 8:36 PM, bschroe...@internode.on.net wrote: > > > When installing multiple front-ends on a phone or computer, how do I

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

David, I’ve installed it on my iPhone 6. Will do my iPad 2 later today. I don’t think the iOS app store supports 32-bit only any more, but they might allow dual 32/64. I have an old iPhone 5 on which I can test. I don’t have a 32-bit iPad like yours. It’s not something you’ll be willing to do.

Re: [sword-devel] Error reading ulCompOffset

Great. If you can isolate the problem in a small test file, we’d like to improve Osis2mod. In Him, DM Smith > On Feb 20, 2018, at 5:26 PM, Andrew T. <thules...@gmail.com> wrote: > > I was able to make progress on this problem. > > To share the resolution - I us

  1   2   3   4   5   6   7   8   9   10   >