So any chance we can include something? I really need this, and I don't see
why the conf files isn't the ideal place to put this?
On 8 February 2013 20:40, Chris Burrell ch...@burrell.me.uk wrote:
Hi
Because I provide Interlinears, I need to be able to tell the user that
for the combination
Regarding proposed new module configuration properties
xulsword http://code.google.com/p/xulsword/ already makes use of a few
extra properties in the conf files for modules made for that front-end.
See note 2 in
http://crosswire.org/wiki/Module_Repositories#Institute_for_Bible_Translation
Yes, but in this case, these are existing modules used with a new front-end
(with I'm guessing functionality that isn't yet available in existing
front-ends), hence the issue.
Chris
On 12 February 2013 14:52, David Haslam dfh...@googlemail.com wrote:
Regarding proposed new module
Maybe we should consider the concept of ancillary configuration files???
i.e. Which augment what's in the module.conf file, and which are specific to
one or more front-end apps.
And which are downloaded from the front-end developer's allocated space in
the crosswire server.
If we had a file
Chris,
I understand the possible need for general facility, to indicate
features and this is why we have the Feature=StrongsNumbers tag.
I also understand why this isn't straight forward the LXX.
But, I would say that this is an exception and one that doesn't warrant
adding a new feature
Hi
I haven't had any responses to this. I'm considering hard-coding the values
in STEP to ensure I'm not trying to match tagging across versions that have
a different type of mark-up.
Let me know if there is appetite for doing this in a slightly more formal
way?
i.e. the Sword conf files should
I believe we preface strongs numbers with G or H to differentiate.
Chris Burrell ch...@burrell.me.uk wrote:
Hi
I haven't had any responses to this. I'm considering hard-coding the
values
in STEP to ensure I'm not trying to match tagging across versions that
have
a different type of mark-up.
Indeed we do, but that implies one has to read the module content to work
out which set of Strongs is used. Ideally you should be able to tell
without consulting the book contents. For example, I display which features
are available to the user while they pick the version from a dropdown.
Chris
Chris makes an important point.
A few weeks ago, it was discovered that our Finnish modules contain tags
that our software interpreted as linguistic markup, but that were an
artifact from something else.
See http://www.crosswire.org/tracker/browse/MOD-230
David
--
View this message in
Indeed, although looking at the MOD-230, this would only help fix your
issue if the Finish module doesn't also contain strong numbers!
Chris
On 8 February 2013 13:13, David Haslam dfh...@googlemail.com wrote:
Chris makes an important point.
A few weeks ago, it was discovered that our
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
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
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
Hi
Because I provide Interlinears, I need to be able to tell the user that for
the combination of LXX and KJV you are unable to see the interlinears in
the OT. The reason being, KJV uses H and LXX uses G. If you're
looking at several texts in interlinears, it simply looks like there is a
Hi all
I have a question about the strong tagging. Some of our modules have strong
tagging for the old testament, but instead of tagging the Hebrew it tags
the Hebrew.
Is there any easy way to know whether a module supports a Old Testament
Septuagint tagging vs a Hebrew tagging.
I'm
15 matches
Mail list logo
