Von: Chris Little chris...@crosswire.org
I hope I've fixed this now. (I haven't tested that it functions
correctly, but the error was fairly obvious from the traceback below.)
Hi Chris,
Sorry, while the crash has gone, the function is not correct - at all.
\cp is meant to give a printed
G'day Karl,
On Fri, Oct 12, 2012 at 2:11 PM, Karl Kleinpaste k...@kleinpaste.orgwrote:
Is the foreign element passed through the engine? If so, do I need
to file bugs with front-ends to encourage support of foreign?
Having just looked, the string foreign does not appear in Sword's
source
foreign is the xml way of indicating a language other than the
language of the document. So you surround Hebrew text with foreign
xml:lang=heb. Judging from Ben's more recent email, even BPBible does
not support it. Regardless of the menthod, the effect is great.
I use Linux Libertine all the
On 10/12/2012 5:44 AM, Daniel Owens wrote:
foreign is the xml way of indicating a language other than the
language of the document. So you surround Hebrew text with foreign
xml:lang=heb.
A small sidenote, since you do encoding: heb is not a legal value for
xml:lang. This must be he or hbo if
On 10/12/2012 4:00 AM, Peter von Kaehne wrote:
Sorry, while the crash has gone, the function is not correct - at
all.
\cp is meant to give a printed chapter number which has no influence
on the underlying counting of verses and chapters. How exactly to
represent it in OSIS, we would need to
Gary Holmlund and I are working on a problem related to the Westminster
Hebrew Morphology (WHM) module. We need a consensus on markup practices
for OSIS lemma.
I was having a problem getting natural Hebrew lemma to look up an entry
and display it in the mag window. Gary discovered that if H
On 10/12/2012 03:23 PM, Chris Little wrote:
On 10/12/2012 5:44 AM, Daniel Owens wrote:
foreign is the xml way of indicating a language other than the
language of the document. So you surround Hebrew text with foreign
xml:lang=heb.
A small sidenote, since you do encoding: heb is not a legal
On 10/12/2012 1:40 PM, Daniel Owens wrote:
Gary Holmlund and I are working on a problem related to the Westminster
Hebrew Morphology (WHM) module. We need a consensus on markup practices
for OSIS lemma.
I was having a problem getting natural Hebrew lemma to look up an entry
and display it in
On 12/10/12 16:43, luke wrote:
In recent correspondence with Karl Kleinpaste of the Xiphos project about
display issues with our project's module. He recommended that I try sword's
latest -r2741 because it has recent changes regarding osis headings. I do not
have access to this version of
Osis2mod is not affected by any of the recent changes. If you built your module
with an earlier, it'd be a good idea to build it with the most recent to test
your content. I believe that the utility lookup will give you a view into how
verses are stored and rendered.
In Him,
DM
On Oct
Apologies, some mis-sorted email caused me not to notice this until now.
I had thought the problem you were seeing was a display issue, in which
case recent engine updates had some good effects, which is why I
suggested a more recent version...not realizing that you're a Win32
user, so all you've
On 10/12/2012 03:16 PM, Chris Little wrote:
On 10/12/2012 1:40 PM, Daniel Owens wrote:
Gary Holmlund and I are working on a problem related to the Westminster
Hebrew Morphology (WHM) module. We need a consensus on markup practices
for OSIS lemma.
I was having a problem getting natural Hebrew
Chris Little wrote:
This is certainly bad OSIS encoding. It is also not a Sword
convention. If anything is implemented that requires a language prefix
like this, it represents a bug, whether in Sword or in BibleTime.
Well...this is how SWModule has done this since forever.
Gary Holmlund
On 10/12/2012 07:23 PM, Karl Kleinpaste wrote:
Chris Little wrote:
This is certainly bad OSIS encoding. It is also not a Sword
convention. If anything is implemented that requires a language prefix
like this, it represents a bug, whether in Sword or in BibleTime.
Well...this is how SWModule
On 10/11/2012 6:39 PM, Daniel Owens wrote:
I am still working on the Abbott-Smith markup project (over 300 entries
and counting). We have four contributors right now, so the pace is
picking up. Creating a module is another story. Chris made a lexicon
module after the first release, but . . .
I
On 10/12/2012 7:23 PM, Karl Kleinpaste wrote:
Chris Little wrote:
This is certainly bad OSIS encoding. It is also not a Sword
convention. If anything is implemented that requires a language prefix
like this, it represents a bug, whether in Sword or in BibleTime.
Well...this is how SWModule
Von: Chris Little chris...@crosswire.org
\cp (like \vp) is a workaround for a limitation in Paratext.
Thanks, this was me being confused.
You should look into \ca or \cl as alternatives.
Thanks. \cl is probably what I looked for. WIll see.
Thanks, even more so, for fixing the bug/crash!
Currently usfm2osis.py does not produce complete cross references.
a) It translates the in the \xo tag contained origin reference as a reference
type=annotateRef
The probably better way in OSIS would be to tack the origin ref as an osisRef
argument into the surrounding note tag.
Having said
18 matches
Mail list logo
