Are there any front-end apps that have support for OSIS Glosses?
See http://crosswire.org/wiki/OSIS_Bibles#Marking_glosses
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/OSIS-Glosses-tp4654301.html
Sent from the SWORD Dev mailing list archive at Nabble.com.
I just tried an experiment using diatheke on a module that I'm currently
developing.
Here is a verse as compiled into the module using imp2vs
$$$Numbers 13:1
Et l’Éternel parla à Moïse, en disant:
NB. The w element is wrapped around a zero width space, just for the sake of
the experiment.
Thi
It's definitely the colon where the bug occurs in the gloss text, not the
number of characters.
As a colon is the delimiter within lemma attributes (eg "strong:nnn"
"robinson:xxx"),
I guess the code for lemmas was copied more or less unaltered to the code
for glosses.
In theory, there no reason w
Created http://www.crosswire.org/tracker/browse/API-179
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/OSIS-Glosses-tp4654301p4654304.html
Sent from the SWORD Dev mailing list archive at Nabble.com.
___
sword-devel mail
Quick note,
Not sure, but I thought we used optional prefixes to specify the kind of gloss
if there are multiple, e.g., gloss="en_US:18 wheeler
en_UK:articulated lorry"
On December 12, 2014 1:21:49 AM MST, David Haslam wrote:
>It's definitely the colon where the bug occurs in the gloss text, n
Gesendet: Freitag, 12. Dezember 2014 um 13:16 Uhr
Von: "Troy A. Griffitts"
> Not sure, but I thought we used optional prefixes to specify the kind of
> gloss if there are multiple, e.g., > gloss="en_US:18 wheeler
> en_UK:articulated lorry"
Should there be an option to escape colons?
> On Dec 12, 2014, at 8:26 AM, Peter Von Kaehne wrote:
>
> Gesendet: Freitag, 12. Dezember 2014 um 13:16 Uhr
> Von: "Troy A. Griffitts"
>
>> Not sure, but I thought we used optional prefixes to specify the kind of
>> gloss if there are multiple, e.g., > gloss="en_US:18 wheeler
>> en_UK:artic
It should be possible to escape any such characters with an XML entity, no?
On Dec 12, 2014 7:44 AM, "DM Smith" wrote:
>
> > On Dec 12, 2014, at 8:26 AM, Peter Von Kaehne wrote:
> >
> > Gesendet: Freitag, 12. Dezember 2014 um 13:16 Uhr
> > Von: "Troy A. Griffitts"
> >
> >> Not sure, but I thoug
Best I can recall:
Nope. An entity is merely an alternate way of specifying a character. The XML
parser is supposed to replace the entity with the corresponding code point
before the value is evaluated against the schema.
> On Dec 12, 2014, at 8:49 AM, Greg Hellings wrote:
>
> It should be pos
If that's the case, how does it handle escaping <>? I believe entity
replacement is after XML validation but before passing them to a
transformer or such.
On Dec 12, 2014 7:52 AM, "DM Smith" wrote:
> Best I can recall:
> Nope. An entity is merely an alternate way of specifying a character. The
>
Hello,
In fact, an entity can store more than a single character. It can be a string
(less
common) or a more complex structure (I've never seen it in real usage).
See
http://msdn.microsoft.com/en-US/en-en/library/ms256483%28v=vs.110%29.aspx
for examples.
To answer Greg, when you read an XML fi
Yes, that was my point. However, Sword does not use standard XML parsing
tools that operate this way and thus we might be able to handle an entity
and the raw character differently. This would still permitting the file to
validate with standard XML tools as well.
--Greg
On Dec 12, 2014 8:52 AM, "S
There are 4 standard entities that are predefined for XML. (I used to think
that it was 5 with both " and ' being defined.) XML allows decimal
entities of the form &#ddd;. Any others need to be defined in a DTD. A schema
(an xsd in the case of OSIS) does not allow for the defining of entities. (
I’ve used such long, multi-character entities before. It requires a DTD and is
defined with in the DOCTYPE statement. I’m not at all sure how to blend a
DOCTYPE and a schema. The OSIS schema does not have any.
I wish I had read your answer before I replied to Greg with the same. :)
Excellent.
Further evidence:
Replacing the colon by a full-stop was 100% successful.
Also, FYI, PocketSword can toggle Glosses. Is this the only front-end that
does?
For anyone who has PocketSword, try installing the JapMeiji module from
CrossWire Beta.
This has OSISGlosses, though the conf file uses the n
This is now fixed.
Peter
On Thu, 2014-12-11 at 13:24 -0800, David Haslam wrote:
> I just tried an experiment using diatheke on a module that I'm currently
> developing.
>
> Here is a verse as compiled into the module using imp2vs
>
> $$$Numbers 13:1
> Et l’Éternel parla à Moïse, en disant:
>
On Troy's request I have reverted the changes I made. I have left the
bug though closed as it was formulated in a fashion which did not cover
what the final discussion was about - support of an escape mechanism,
support of multiple glosses.
It seems I had not completely understood the drift of th
17 matches
Mail list logo
