Re: [sword-devel] Chapter descriptions

Yes, the AKJV chapter indexes use the original KJV chapter index (a 1708 copy specifically,) but I wordsearched the wordlist in the AKJV appendix. But if I did it again, I'd mark them up with links (\xt ... \xt*). This tag's use in this context is new to USFM 3, and I didn't catch it until

Re: [sword-devel] Chapter descriptions

In the AKJV link you gave, line 11 is: \cd 1 Elimelech driven by famine into Moab, dies there. 4 Mahlon and Chilion, having married wives of Moab, die also. 6 Naomi returning homeward, 8 dissuades her two daughters in law from going with her, 14 Orpah leaves her, but Ruth with great constancy

Re: [sword-devel] NASB Psalm titles

Troy wrote, "No. diatheke is certainly not the gold standard for seeing anything. Diatheke has bugs of its own. I personally use word/examples/cmdline/lookup.cpp to check all info about what SWORD output from a module entry to a frontend for a particular format.

Re: [sword-devel] Chapter descriptions

Reading the list of provided tags, these chapter descriptions should be marked ".index" when they provide reference information, and ".summary" where they do not. That is, the original KJV1611 has chapter indexes. The original Douay Rheims Challoner has Chapter summaries. The recent update to

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] Chapter descriptions

On 5/9/20 2:14 AM, David Haslam wrote: > OSIS has no dedicated element specifically for a chapter description. > These are not section titles per se but they come before verse 1.  Xiphos since 4.1 renders 0:0 and n:0 material as ".introMaterial", default italic. See ESV2011, any book's chapter 1.

Re: [sword-devel] Shared format / persistence concept for tagged verse lists (originated in thread about Versification Mapping)

Live-sharing is a matter of BibleSync. .I think a common transfer format for complicated book mark trees which is designed well from bottom up and could be published similarly to BibleSync would be brilliantPeterSent from my mobile. Please forgive shortness, typos and weird autocorrects.

[sword-devel] Chapter descriptions

Discussion starter OSIS has no dedicated element specifically for a chapter description. These are not section titles per se but they come before verse 1. In printed Bibles, they are typically in italics and are never in bold. Usually centred and often contain verse numbers that could be

Re: [sword-devel] NASB Psalm titles

This is also a challenge for using USFM, let alone OSIS and SWORD front-ends. In some AV11N, the CT is sometimes only part of verse 1. There are also at least 2 Psalms where the CT extends into verse 2 and 1 Psalm where the CT actually creeps into verse 3 with a single word consisting of a

[sword-devel] Shared format / persistence concept for tagged verse lists (originated in thread about Versification Mapping)

On 5/9/20 10:08 AM, Caleb Maclennan wrote: On Sat, May 9, 2020 at 9:45 AM Tobias Klein > wrote: Something more realistic than a shared storage backend would be a shared export / import format. This I think may be worthwhile to pursue. We could simply

Re: [sword-devel] NASB Psalm titles

Hi Tom, It's very easy to create a deb with the xiphos sources. Just see the "Generating DEB Packages" in the install.md. Then you'll have the last release. Le 08/05/2020 à 19:59, Tom Sullivan a écrit : > Y'all: > > Thank you all for your interactions. I honestly have been trying to > help, not

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

I have a finding regarding the search results. Module: NASB Search term: "faith Jesus" Search type: multiWord (-2) Search boundaries: Regular (without strict flag) Among others I get Ephesians 2:7 and Ephesians 3:11 as search results. Both contain the word "Jesus". However, the respective

Re: [sword-devel] Versification Mapping

On Sat, May 9, 2020 at 9:45 AM Tobias Klein wrote: > @all: Who would be interested in this in general? We could start with tags > / topical verse lists. > I would. For my tastes and potential use cases something that split the difference between a complete live persistence and a static

Re: [sword-devel] Versification Mapping

Thanks, Troy! These numbers below look excellent! I will look into using the VerseKey-based mapping approach for Ezra Project. However, it's going to be a significant refactoring effort, so I'm probably not going to get back with implementation-based feedback any time soon. I just created an