Response still awaited. Anyone?
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/Diatheke-support-for-Ruby-tp3020078p3023453.html
Sent from the SWORD Dev mailing list archive at Nabble.com.
___
sword-devel mailing list:
Good point, David. I was thinking only of Diatheke's ability to
transform the xlit attribute to a rendering format (because it will use
updated OSISHTML(HREF)). I wasn't thinking of the ability to toggle Ruby
(via OSISRuby), which still requires handling in Diatheke.
--Chris
On 10/30/10 5:08
Thanks Chris,
I recall reading somewhere that you viewed xlit as more appropriate than
gloss as the XML attribute to mark Ruby. Yet the fact remains that the
existing Japanese beta modules use the latter. I suppose they could all be
remade after an attribute search and replace in the OSIS source
Ruby markup, as exemplified by the Japanese modules in our beta repository,
uses the following syntax:
$$$Genesis 1:1
はじめにw gloss=かみ神/wはw gloss=てん天/wとw gloss=ち地/wとをw
gloss=そうぞう創造/wされた。
Does diatheke support the w gloss=./w markup?
i.e. If one chooses HTML as the output encoding.
If not,
On 10/30/2010 12:59 AM, David Haslam wrote:
Ruby markup, as exemplified by the Japanese modules in our beta repository,
uses the following syntax:
$$$Genesis 1:1
はじめにw gloss=かみ神/wはw gloss=てん天/wとw gloss=ち地/wとをw
gloss=そうぞう創造/wされた。
Does diatheke support thew gloss=./w markup?
i.e. If one
Thanks Chris,
Your reply prompts a further question.
What command line option filter should be used?
Gloss is not mentioned in Valid option_filters values are: n (Strong's
numbers),
f (Footnotes), m (Morphology), h (Section Headings),
c (Cantillation), v (Hebrew Vowels), a (Greek Accents),
