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 make WebKit /*not*/ operate in an XHTML mode, I'm
> not aware of it.
Sorry, I
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 make WebKit /*not*/ operate in an XHTML mode, I'm
not aware of it.
___
sword-devel mailing list:
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
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"
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
On Sun, Mar 17, 2019 at 10:07:29AM -0400, 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
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 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
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
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
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)
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
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
On 3/17/19 6:23 AM, ref...@gmx.net wrote:
> Xiphos then adds a few further standard (for Xiphos) CSS styles to the
> mix.
Not exactly.
Xiphos uses exactly one nonstandard CSS control, .introMaterial,
specifically because OSIS tools and Sword processing do not generate a
distinct display class for
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,
I found the solution
We need to use "subsectionNUMBER" and after modify the css like that:
.subSection1 { -webkit-column-count: 1 ; background-color:Yellow ;
color:violet ; text-align: center; }
.subSection2 { -webkit-column-count: 1 ; background-color:Yellow ;
color:white ; text-align:
The order of precedence is from low to high libsword, front-end, module, so you can in principle override anything you want. Titles are given attributes by the engine instead of hard coded h1/h2/h3 etc, so you can play around with these by way of CSS quite specificallyPeterSent from my mobile.
Is the CSS directive for CONF clearly described in our wiki page?
David
Sent from ProtonMail Mobile
On Sun, Mar 17, 2019 at 10:23, ref...@gmx.net wrote:
> All OSIS is translated by the engine into XHTML, and a standard CSS style
> sheet is sent along.
>
> You can see that sheet when you ask
All OSIS is translated by the engine into XHTML, and a standard CSS style sheet is sent along. You can see that sheet when you ask the diatheke to put out any random biblical text as XHTML. Xiphos then adds a few further standard (for Xiphos) CSS styles to the mix. That is hard coded into Xiphos
Suggest you approach Karl directly for further help.
I’m not an expert on CSS.
David
Sent from ProtonMail Mobile
On Sun, Mar 17, 2019 at 09:06, Cyrille wrote:
> Il 17/03/2019 09:58, David Haslam ha scritto:
>
>> The usual way to implement different colours and other styles of text would
>>
Il 17/03/2019 09:58, David Haslam ha scritto:
> The usual way to implement different colours and other styles of text
> would be to provide an ancillary CSS file for use by the rendering
> engine.
>
> In the past, Karl has provided a few examples for how this can be done
> with Xiphos.
He I
The usual way to implement different colours and other styles of text would be
to provide an ancillary CSS file for use by the rendering engine.
In the past, Karl has provided a few examples for how this can be done with
Xiphos.
Red letters for words of Jesus are part of how the SWORD engine
Hello,
I'm working on a devotional catholic calendar. I would like to use
colour for some words or for titles. Is it possible? The only way I
found is to use for the read ;)
I would like also to know if it is possible to use different style of
titles like title 1 or title 2...
Thank you for
25 matches
Mail list logo
