Eliminating orphaned verse tags can be done by tweaking the OSIS input file.
The workaround involves moving some verse eID milestones such that there are no
other OSIS elements before the next verse sID milestone.
Except, of course, at a chapter boundary.
The fact that I enquired about XML
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,
Are we sure that this is a problem with the OSIS and not just an issue with
the render filters? All consecutive strings of whitespace characters in XML
cdata segments is supposed to be collapsed to a single space character upon
processing. If we've got newlines showing up in places that a newline
That's a good point to include!
Best regards,
David
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Saturday, 9 February 2019 15:40, DM Smith wrote:
> I’d also add that using XSLT can introduce unwanted white space.
>
> — DM Smith
>
> > On Feb 9, 2019, at 9:41 AM, DM
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 frontend.
> 1)
Regarding ws and notes, it depends. Some modules put the marker before the item
so don’t follow that w a space but precede with one if appropriate. Most follow
the item and then don’t precede with one but follow if appropriate.
In the print 1769 KJV many have markers with surrounding
Hi DM,
Please write this up in our wiki.
Let’s help module developers to avoid making any related mistakes.
David.
Sent from ProtonMail Mobile
On Sat, Feb 9, 2019 at 14:41, DM Smith wrote:
> There are several things in play wrt to whitespace in an OSIS document as it
> pertains to a
Hi Tom,
IIRC, There may also be font issues for the Xiphos Preview pane in modules that
need a special Unicode font.
The font selected in module options does not seem to extend its scope to the
Preview pane.
Displayed search results can be particularly bad in this scenario.
David
Sent from
Thanks DM.
Very helpful.
Any thoughts about XML ws before or after a note element ?
Clearly, a space just after a note should never be inadvertently removed.
And equally so, a space should never be inadvertently inserted just before a
note.
I suspect some XML prettifiers may break one or
Y'all:
An aside: Re: SBL Hebrew: thanks to this list sometime back, that font
solved a lot of problems for me instead of using other fonts with UTF-8.
When I select SBL Hebrew and some font size in Xiphos or BibleTime, the
change shows in OSHB. But it does NOT show in the text or note of a
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
Issue added:
https://github.com/adyeths/u2o/issues/82
Best regards,
David
Sent with [ProtonMail](https://protonmail.com) Secure Email.
‐‐‐ Original Message ‐‐‐
On Saturday, 9 February 2019 11:17, David Haslam wrote:
> Thanks Ryan,
>
> I will add an issue.
>
> Aside: Are we all
Thanks Ryan,
I will add an issue.
Aside: Are we all certain that this isn’t due to a bug in the SWORD API ?
David
Sent from ProtonMail Mobile
On Fri, Feb 8, 2019 at 22:36, Ryan V wrote:
> A special utility isn't needed. This is a bug in the usfm to osis converter
> being used.
>
> If this
Is there someone capable of implementing Reader View for all the pages on our
main site?
Several years ago there was a splurge of activity to improve the pages, but we
are now in the age of mobile phones.
Best regards
David
Sent from ProtonMail
14 matches
Mail list logo
