Yes, mapping! I don't have strong opinion about how this works out on
the engine side of things, but proper mapping between versifications for
front-ends that support parallel display is essential for doing work
with Old Testament Hebrew and Greek texts and with modern translations.
I have hap
I agree with Chris.
It will take a lot of work in the SWORD and JSword engine to implement it.
If anything we should develop a v11n that can be read in from a resource file.
But before that I'd like to see support for mapping from one v11n to another.
In Him,
DM
On Jan 6, 2012, at 6:31
I prefer Scope too. It is a term we already use in JSword to express what the
module includes.
In Him,
DM
On Jan 6, 2012, at 6:12 PM, Chris Little wrote:
> On 1/6/2012 1:21 AM, David Haslam wrote:
>> For the new config property, would Scope be a better word than Coverage?
>>
>> http://
On 1/6/2012 1:29 AM, David Haslam wrote:
Extending Peter's concept, might we also make the book order something that
can be worked with by front-end developers?
e.g. For the NT in Eastern Canonical order we might have:
Scope=Matt-Acts James-Jude Rom-Heb Rev
i.e. with the General Epistles order
On 1/6/2012 1:21 AM, David Haslam wrote:
For the new config property, would Scope be a better word than Coverage?
http://www.merriam-webster.com/dictionary/coverage
http://www.merriam-webster.com/dictionary/scope
David
I'm somewhat more in favor of Scope, since it is the term used in OSIS
f
2012/1/6 Костя и Алёна Маслюк :
> While there is no support for module-supplied v11n in engine, no sense to
> making and testing modules. Test module for this task could be any
> incomplete module (without NT or OT).
And there you have the problem.
- The engine has no reason to support it if there
On Fri, Jan 6, 2012 at 3:29 AM, David Haslam wrote:
> Extending Peter's concept, might we also make the book order something that
> can be worked with by front-end developers?
>
> e.g. For the NT in Eastern Canonical order we might have:
>
> Scope=Matt-Acts James-Jude Rom-Heb Rev
This would be un
While there is no support for module-supplied v11n in engine, no sense to
making and testing modules. Test module for this task could be any
incomplete module (without NT or OT).
As for me this task is not very difficult and well discussed to start
working over implementation. But two thing
Extending Peter's concept, might we also make the book order something that
can be worked with by front-end developers?
e.g. For the NT in Eastern Canonical order we might have:
Scope=Matt-Acts James-Jude Rom-Heb Rev
i.e. with the General Epistles ordered prior to the Pauline Epistles.
This wou
For the new config property, would Scope be a better word than Coverage?
http://www.merriam-webster.com/dictionary/coverage
http://www.merriam-webster.com/dictionary/scope
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/Av11n-and-coverage-tp4265350p4268743.html
Se
10 matches
Mail list logo
