The OSIS 2.1.1 spec permits a seg element within a seg element.
Does the SWORD API make adequate provision for nesting of seg elements that
have different type attribute values?
This technical question relates to my earlier message of today.
A negative answer might go some way to accounting for
iptions
> turn up in searches, while they would not otherwise, unless one searches for
> capitalized text.
>
> Sent from my mobile. Please forgive shortness, typos and weird autocorrects.
>
>
> ---- Original Message ----
> Subject: Re: [sword-devel] The OSIS elem
"
An: "David Haslam" , "SWORD Developers' Collaboration Forum"
Cc: "ref...@gmx.net"
Betreff: Re: [sword-devel] The OSIS element inscription ?
Corrigendum
I should have written type="small-caps" for the hi element.
btw. The testing of this i
turn up in searches, while they would not otherwise, unless one searches for
>> capitalized text.
>>
>> Sent from my mobile. Please forgive shortness, typos and weird autocorrects.
>>
>> Original Message
>> Subject: Re: [sword-devel] The OSIS
entation is capitalisation. Or better
>>>> small caps. Only to work the actual presentation needs to be taken out of
>>>> the text as it stands. Right now KJV inscriptions are both tagged and
>>>> capitalised. Can I ask for this being corrected?
>>>&
: [sword-devel] The OSIS element inscription ?From: DM Smith To: David Haslam ,SWORD Developers' Collaboration Forum CC: In the KJV, these are IN ALL CAPITAL LETTERS. I think that we are both marking it semantically and having the text as given. I think this is correct.I can see about renderi
to work the actual presentation needs to be taken out of
>> the text as it stands. Right now KJV inscriptions are both tagged and
>> capitalised. Can I ask for this being corrected?
>>
>> Thanks
>>
>> Peter
>>
>> Sent from my mobile. Please f
this being corrected?
>
> Thanks
>
> Peter
>
> Sent from my mobile. Please forgive shortness, typos and weird autocorrects.
>
> ---- Original Message
> Subject: Re: [sword-devel] The OSIS element inscription ?
> From: DM Smith
> To: David Haslam ,SWORD
nt from my mobile. Please forgive shortness, typos and weird autocorrects. Original Message Subject: Re: [sword-devel] The OSIS element inscription ?From: DM Smith To: David Haslam ,SWORD Developers' Collaboration Forum CC: JSword -> YesOn Mar 20, 2018, at 11:46 AM,
Original Message ‐‐‐
> On 17 March 2018 2:31 PM, ref...@gmx.net wrote:
>
>> Easily done with CSS, I would do little else.
>>
>> Do you have a list of occasions this could be used at?
>>
>> Sent from my mobile. Please forgive shortness, typos and weird autocorrects.
used at?
>
> Sent from my mobile. Please forgive shortness, typos and weird autocorrects.
>
> Original Message --------
> Subject: [sword-devel] The OSIS element inscription ?
> From: David Haslam
> To: sword-devel mailing list
> CC:
>
>> Does SWORD
Easily done with CSS, I would do little else. Do you have a list of occasions this could be used at?Sent from my mobile. Please forgive shortness, typos and weird autocorrects. Original Message Subject: [sword-devel] The OSIS element inscription ?From: David Haslam To: sword-devel
Does SWORD contain any code to render text wrapped by the OSIS inscription
element ?
Best regards,
David
Sent from ProtonMail Mobile___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructi
speaker and q are not equivalent. speech and q are. (according to the OSIS
manual.) Speaker is meant to surround the one who is speaking. E.g. David said: …..
— DM
> On Jan 24, 2015, at 3:49 PM, David Haslam wrote:
>
> Making a one to one equivalence between USFM marker \sp and OSIS element
>
That makes good sense, but it will fall to the ground if the USFM to OSIS
conversion ignores this workaround.
As long as it converts the \sp marker to the element, and the OSIS
validates, most module makers will not even realise that there is a serious
underlying problem.
David
--
View this m
Making a one to one equivalence between USFM marker \sp and OSIS element
is a questionable assumption for several reasons.
1. The translator may have used the \sp marker for non-canonical purposes.
2. In such a context, it would be better OSIS practice to use
3. Yet unless the SWORD back-end
The common example of using speaker to identify Man/Woman (He/She) in Psalms is
not recommended by the OSIS manual. Since it is added text (i.e. not in the
Hebrew), the OSIS manual recommends:
woman
The OSIS manual recommends using speaker for canonical text. However, true is
not the default va
Apart from the lack of SWORD support, there is also an OSIS conversion issue
relating to the speaker element.
See http://www.crosswire.org/tracker/browse/MODTOOLS-87
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/The-OSIS-speaker-element-tp4651387p4654535.html
Se
The question arises because usfm2osis.py converts \sp_text to
text
In the Welsh beibl.net translation, Arfon has used the \sp marker in these
four OT books:
Song, Jeremiah, Lamentations, Ezekiel ( but not in Job ! ).
I therefore assume that he did this as a matter of interpretation, rather
than
Is the speaker identified in Job and Songs canonical text? That is, is it in
the underlying Hebrew?
— DM
> On Jan 3, 2015, at 8:55 AM, David Haslam wrote:
>
> For modules that contain the OSIS element (e.g. in Job & Song for
> some Bibles),
> does the OSISHeadings filter toggle these along wit
For modules that contain the OSIS element (e.g. in Job & Song for
some Bibles),
does the OSISHeadings filter toggle these along with the other headings that
use the element?
cf. The corresponding USFM marker is \sp_text - and this is categorized
under Titles, Headings and Labels.
David
--
I like the idea, Hope to see such features in Arabic modules, but we even don't
even have the modules themselves :)
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listin
Hi David
>From my point of view, the speakers is so infrequently used across OSIS
modules that it would only come in useful for some texts. I'm not entirely
sure how often it is used even in those texts that do have some speaker
elements.
The main use case I'd find for it is find all instances of
Hi Chris,
Do you think it would benefit users if SWORD could be enhanced to use
GlobalOptionFilter=OSISspeakers
??
And should the search index include or exclude the names of speakers?
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/The-OSIS-speaker-element-tp4
Hi David
Step displays this in purple at the moment, which matches a number of other
headings we display.
Chris
On 15 December 2012 10:23, David Haslam wrote:
> *Bible Desktop* displays these *speakers* with blue text.
>
> What do other JSword based front-ends do?
>
> David
>
>
>
> --
> View
*Bible Desktop* displays these *speakers* with blue text.
What do other JSword based front-ends do?
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/The-OSIS-speaker-element-tp4651387p4651398.html
Sent from the SWORD Dev mailing list archive at Nabble.com.
___
How about including in SWORD some suitable support for the element?
With a GlobalOptionFilter to toggle the display of this (non-canonical)
feature, which is used in some translations to identify the lover and the
beloved in the Song of Songs.
David
--
View this message in context:
http://
27 matches
Mail list logo
