Hi David,
 
Wrt KJV etc Yes, and no. I would not want to issue a module if there is a serious problem with a frontend. I would not call this a serious problem by any account. The text remains unchanged. The inscription is recognisable without problem. So, I would not hesitate to update the KJV or any other relevant module for this matter irreespective of whether all frontends have cought up.
 
If a current libsword dependent frontend does not display the hi element with small caps the right way then this suggests that that frontend uses the the older html filter instead of the xhtml filter (or alternatively loads a different CSS sheet than supplied). The older filter hardcodes display while the xhtml filter has a by and large a semantic markup which then is CSS driven - which allows frontends to override the supplied CSS  either in general or specifically for some modules (which reminds me we need a Wiki article on that). In the old filter all hi elements which do not allow a hard coded non CSS dependent translation are automatically italicisied in order to do something useful with them.
 
Peter
 
Gesendet: Mittwoch, 21. März 2018 um 09:36 Uhr
Von: "David Haslam" <dfh...@protonmail.com>
An: "David Haslam" <dfh...@protonmail.com>, "SWORD Developers' Collaboration Forum" <sword-devel@crosswire.org>
Cc: "ref...@gmx.net" <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 in Eloquent was done by someone else.
 
Best regards,
 
David
 
Sent with ProtonMail Secure Email.
 
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On 21 March 2018 9:19 AM, David Haslam <dfh...@protonmail.com> wrote:
 
Thanks Peter,
 
Whatever view each of us may have about the KJV module, this thread is more general.
Its about any modules that potentially may contain the inscription element.
 
Aside:
Small-caps already works for the divineName element in most front-ends.
Small-caps doesn't work for the hi element with type="small caps" for at least one front-end (Eloquent).
Currently, this defaults to italics.
 
We should also bear in mind that altering a module before all front-ends have implemented the proper rendering in a new release would reduce the quality of the output.
i.e. A Proper Case inscription for ".... The Mother Of Harlots ...." might not "cut the mustard" for some KJV readers.
 
Best regards,
 
David
 
Sent with ProtonMail Secure Email.
 
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On 21 March 2018 8:26 AM, ref...@gmx.net <ref...@gmx.net> wrote:
 
Hi DM, I am not sure I agree. For any number of reasons.
 
We do not copy the presentation as such usually, but normally tag semantically and then attach a presentation fitting to the original presentation. So if small caps is wrong maybe textTransform=capitalize as style, but ordinary text in the OSIS.
 
The main positive result of the change I propose is that the inscriptions 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 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 rendering it differently. In the printed copy of the KJV, the letters are spaced a bit more than otherwise.
 
DM
 
On Mar 20, 2018, at 5:27 PM, David Haslam <dfh...@protonmail.com> wrote:
 
Small caps style makes no change to UPPER CASE letters. The inscription text would have to change to Proper Case. 
 
But wouldn't this deviate from the KJV Oxford Edition of Benjamin Blayney?
 
 
Best regards, David
 
 
Sent from ProtonMail Mobile
 
 
On Tue, Mar 20, 2018 at 18:59, ref...@gmx.net <ref...@gmx.net> wrote:
Hi DM,
 
I am thinking that the "correct" presentation 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?
 
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 Developers' Collaboration Forum
CC:
 
 
 
JSword -> Yes
 
 
On Mar 20, 2018, at 11:46 AM, David Haslam <dfh...@protonmail.com> wrote:
 
No - I was just wondering whether we already did something in either SWORD or JSword.
 
The likelihood is low, and a yes/no answer would suffice.
 
cf. Examples of an inscription in Scripture include those in Acts 17:23 and Revelation 17:5 & 19:16.
 
btw. I'm aware that some front-ends support ancillary CSS files.
 
Best regards,
 
David
 
Sent with ProtonMail Secure Email.
 
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On 17 March 2018 2:31 PM, ref...@gmx.net <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.
 
 
-------- Original Message --------
Subject: [sword-devel] The OSIS element inscription ?
From: David Haslam
To: sword-devel mailing list
CC:
 
 
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
Instructions to unsubscribe/change your settings at above page
 
_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
Instructions to unsubscribe/change your settings at above page
 
 
_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Reply via email to