[sword-devel] Generated footnote markers in non-Roman modules
chrislit at crosswire.org
Tue Feb 19 09:22:39 MST 2013
On 2/19/2013 8:09 AM, Greg Hellings wrote:
> On Tue, Feb 19, 2013 at 9:21 AM, David Haslam <dfhmch at googlemail.com
> <mailto:dfhmch at googlemail.com>> wrote:
> Some Bible modules that are for a language with a non-Roman script
> do NOT
> have an attribute 'n' value in the OSIS,
> so the automatically generated footnote markers (a, b, c, d, ...) look
> especially bad.
> That is what the 'n' attribute is for. If the auto-generated footnote
> markers look bad, then put in an 'n' attribute to the source OSIS file.
> Defaults generally look bad when applied to circumstances outside of
> their source default.
> If at all possible, we should employ letters from the same script.
> I don't know of a programmatic method for this, but if there is one it
> would probably introduce dependency on another library such as ICU or
> similar. Xiphos currently does not require ICU directly and BibleTime
> tries to not require it at all by using the built-in Qt libraries for
> Unicode handling. But, in general, if users don't like the 'default'
> behavior they should use the provided mechanism of the 'n' attribute to
> change it.
We could define a set of enumeration symbols as a part of our
locale-wide localization files and/or as part of the module .conf.
I'm not sure I necessarily like the idea, but it wouldn't introduce
dependencies. I doubt ICU would help with this anyway since I suspect
this is presently beyond the scope of CLDR.
More information about the sword-devel