For OSIS, the only values to indicate Strong's Numbers are:
GlobalOptionFilter=OSISStrongs
and
Feature=StrongsNumbers
There is nothing defined to further distinguish.
BTW, what is extended Greek? Are you referring to the TVM codes that look like
Strong's Number with a G prefix?
I guess what we need is to understand how you'd use the knowledge in a program.
In Him,
DM
On Feb 8, 2013, at 3:15 PM, Chris Burrell <ch...@burrell.me.uk> wrote:
> Thanks, that does clarify. Still the problem remains in that we want to be
> able to distinguish between different types of tagging (greek, hebrew,
> extended greek) by questioning the module. Does the conf file not also define
> supported features? Can we not make it so? Or have a flag in there to
> indicate the Strongs tagging is abnormal/Septuagint (i.e. Greek tags in the
> OT)
>
> Chris
>
>
>
> On 8 February 2013 20:11, DM Smith <dmsm...@crosswire.org> wrote:
> In SWORD the various GlobalOptionFilter values indicate to the SWORD engine
> which pieces of code (filters) to enable. Same with some other entries in the
> conf.
>
> In JSword, we don't have a filter architecture. We convert everything from
> the source type (ThML, Plaintext, GBF, ...) to OSIS. Then we use xslt to
> transform that into HTML. The xslt is passed what the user would like to see
> or not see. It doesn't really matter (so far) what is set in the module's
> conf.
>
> This has one problem. Regarding Headings (aka Titles). They should always
> show in a commentary, as they should all be assumed to be canonical (properly
> part of the module) unless marked non-canonical.
>
> Hope this clarifies.
>
> In Him,
> DM
>
>
> On Feb 8, 2013, at 11:00 AM, Chris Burrell <ch...@burrell.me.uk> wrote:
>
>> Perhaps in Sword-terms a property isn't a statement of what's there, however
>> JSword does seem to read it and give the front-end information about whether
>> an option is available in the module or not...
>>
>> Maybe I misunderstand something?
>>
>> Chris
>>
>>
>>
>> On 8 February 2013 15:12, David Haslam <dfh...@googlemail.com> wrote:
>> Our three Finnish modules do not have Strong's numbers.
>>
>> The conf files do not include GlobalOptionFilter=OSISStrongs, yet the
>> pseudo-markup in the source text files
>> (from an /ad hoc/ workaround to provide the original verse references from
>> an Av11n translation)
>> get interpreted as if they were Strongs!!!
>>
>> The engine still parses the text, and displays these tags, despite the fact
>> that they can't be hidden by a filter.
>>
>> A filter property in a conf file is just that! It tells the engine what to
>> do when asked.
>> It's not a statement about what's there.
>>
>> David
>>
>>
>>
>> --
>> View this message in context:
>> http://sword-dev.350566.n4.nabble.com/Strong-tagging-and-Septuagint-tp4651344p4651916.html
>> Sent from the SWORD Dev mailing list archive at Nabble.com.
>>
>> _______________________________________________
>> 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
>>
>> _______________________________________________
>> 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
>
>
_______________________________________________
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
