I have made an OSIS file from the 1951 Schlachter Bible module
using the versification derived from the GBF tags
I then repeatedly built an eXperimental module using osis2mod trying with
different v11n.
None of our supported v11n gave an exact fit.
The best fit was (surprisingly) Segond. This
FYI.
I have found two GBF markup errors in the GerSch module.
* One pair of … that is a typo for …
* One unpaired “ “ where there should simply be “)”.
I also discovered today that the Perl script imp2osis.pl makes a mess of
accented letters.
At least - that’s when I used it with Perl within th
I should add that the syntax help for utils64\imp2vs.exe does include the 3 new
French av11n names.
I’ve just tried a build with -v German
but there are 71 empty verses.
NB. Verses outside the specified v11n are not simply appended by imp2vs as they
are by osis2mod.
Aside: It’s conceivable tha
The GerSch module was made from a GBF source text in October 2006 and rebuilt
with corrected module encoding in August 2013.
I do not have the original GBF file.
NB. It may not have had “GBF” as part of the filename or extension.
Does anyone active in this list still have it?
If Chris Little d
Well, the av11n required for GerSch original is not Luther. !!!
So, the copyright owner being the Geneva Bible Society, I thought “Let’s try
with -v Calvin”. After all, ;)
However, “Geneva, we have a problem.”
imp2vs never terminates when this is specified.
I am using the Windows utiliti
The filters don’t care that the tags are repurposed. The GBFPlain documents
as tense.
That they were and that you know what they mean is perhaps helpful.
In Him,
DM
> On Mar 18, 2019, at 10:56 AM, David Haslam wrote:
>
> The GBF tags in GerSch that we’re discussing have nothing whats
The GBF tags in GerSch that we’re discussing have nothing whatsoever to do with
Strongs or Tense.
They are quite clearly all used for recording the original references before
the text was squished in 2006 to the only v11n that SWORD supported at the
beginning.
To satisfy my own curiosity, I ha
I don't read every thing in this post and maybe someone propose already
my solution : convert gbf to osis or to usfm with
gbf2OSIS.exe/gbf2usfm.exe (need mono on linux) it works fine! I use it
with jpdenmo.
Il 18/03/2019 13:51, Troy A. Griffitts ha scritto:
> This likely means that our GBFPlain fi
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 el
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 consi
Hi Troy,
That does not seem consistent with the observation that PocketSword v 1.4.8
renders them suitably. See my earlier reply.
Unless maybe a new bug has occurred in SWORD since PS 1.4.8 was released and
that was made with SWORD 1.7.x
Or perhaps if different compiler directives were in play
This likely means that our GBFPlain filter doesn't recognize these GBF tags and
ignores them this should be a simple fix in the filter.
http://crosswire.org/svn/sword/trunk/src/modules/filters/gbfplain.cpp
On March 18, 2019 12:12:59 AM MST, Tobias Klein wrote:
>I tried to initialize my SWMgr
I tried to initialize my SWMgr object like this:
mgr = new SWMgr(new MarkupFilterMgr(FMT_PLAIN));
Yet the results are still the same for the GerSch module as described
earlier.
Best regards,
Tobias
On 17.03.19 19:46, Troy A. Griffitts wrote:
Hi Tobias. SWORD renders these tags for you if the
A question about the 1951 edition of the Schlachter Bible.
These and tags - can we assume that these only exist
because the 2006 module version 1 had to forced to fit the KJV versification ?
If so, the corrective action should be to rebuild the module against the proper
alternative versificat
Thanks for the support on this, Troy. I appreciate it!
I'll have a look asap and see how far I get.
Best regards,
Tobias
On 17.03.19 19:46, Troy A. Griffitts wrote:
Hi Tobias. SWORD renders these tags for you if the planets are
aligned. When you create your SWMgr, you tell it what "Render" mark
Hi Tobias. SWORD renders these tags for you if the planets are aligned. When
you create your SWMgr, you tell it what "Render" markup you would like. We
highly recommend XHTML. This will tell the SWMgr factory class to construct
SWModule oblects with all the necessary filters added to produce you
On 17.03.19 18:38, Greg Hellings wrote:
You might need to add an instance of the GBFPlain class to the filter
set before calling for stripText. It is specifically crafted to strip
the tags you're talking about.
In general, you'll want to add a Plain object to the filter
set for any module you
You might need to add an instance of the GBFPlain class to the filter set
before calling for stripText. It is specifically crafted to strip the tags
you're talking about.
In general, you'll want to add a Plain object to the filter set for
any module you're processing to plain text, where can be p
On 17.03.19 18:05, David Haslam wrote:
Aside: Which front-end doesn’t render these tags ?
My own frontend: Ezra Project.
Where are these tags documented?
I found this: https://ebible.org/bible/gbf.htm
But there I didn't find any documentation for the tags I encountered.
Best regards,
Tobias
It’s not just Psalms that has these tags.
They are found also in Job, Ecclesiastes, Song, Isaiah, Jeremiah, Ezekiel,
Daniel, Hosea, Joel, Jonah, Micah, Nahum, Zechariah, Malachi
David
Sent from ProtonMail Mobile
On Sun, Mar 17, 2019 at 17:05, David Haslam wrote:
> Hi Tobias,
>
> GBF is an ol
Hi Tobias,
GBF is an old Bible markup format.
We now don’t accept it for new modules.
Have you found an authentic online source text?
Can you obtain a better one direct from the GBS ?
CrossWire doesn’t normally rebuild a module from text exported from a module.
In this case, that would only be
Further observation.
The actual GBF markup is like this example.
PocketSword renders these as italics superscript (3-2) within parentheses.
David
Sent from ProtonMail Mobile
On Sun, Mar 17, 2019 at 16:30, Tobias Klein wrote:
> Hi,
>
> when working with the German Schlachter Bibel (1951) [G
Ok, thanks David!
So that means unless there's an updated module I would have to apply my
own "search / replace" to get rid of these tags, huh?
Are there other modules with the same "issue"?
Best regards,
Tobias
On 17.03.19 17:46, David Haslam wrote:
The GerSch module was made from an input
The GerSch module was made from an input file that had GBF markup.
It’s not OSIS.
These H tags record the verse references for the original av11n.
The module was made in 2013.
But the source text was from much earlier, 2006.
It might be suitable for rebuilding if we can still obtain the 1951 so
Hi,
when working with the German Schlachter Bibel (1951) [GerSch] I noticed
that there's some special markup in the Psalms:
Ein Psalm Davids, als er vor seinem Sohne Absalom floh.
Ach, HERR, wie zahlreich sind meine Feinde! Viele stehen wider
mich auf;
viele sagen von meiner Seele: «Sie hat
25 matches
Mail list logo
