[sword-devel] divineName wrapping w in NASB

[Ben Morgan]

Hi all,

While looking at the NASB, I found that the way it uses the divineName tag
with the w tag isn't supported by sword.

For example, from Genesis 2:4
In the NASB, w is inside the divineName tag:
 that the <divineName><w lemma="strong:H3068">Lord</w></divineName>
in the KJV, it is outside
<w lemma="strong:H03068">that the
<seg><divineName>Lord</divineName></seg></w>
According to DM, these are both legal.

However, doing it the NASB way means
a) the osisplain filters in sword don't uppercase it up properly
(I added the code for this, so its partly my fault :)
b) SWORD web doesn't work properly with it:
You can't click on the word LORD in the NASB and get a popup
If you turn strong's numbers on, the number is before LORD, rather than
after it.
c) The osishtmlhref filters leave the strong's number out altogether

Also, according to DM, there is another problem when you have
<divineName>Lord's</divineName>. At least one of the filters cannot handle
the possessive form.

God Bless,
Ben
-------------------------------------------------------------------------------------------
The Lord is not slow to fulfill his promise as some count slowness,
but is patient toward you, not wishing that any should perish,
but that all should reach repentance.
2 Peter 3:9 (ESV)

On Fri, Jul 18, 2008 at 12:31 PM, DM Smith <dmsmith555 at yahoo.com> wrote:

>
> On Jul 17, 2008, at 8:54 PM, Ben Morgan wrote:
>
>  Hi DM,
>>
>> In the NASB, w is inside the divineName tag:
>>  that the <divineName><w lemma="strong:H3068">Lord</w></divineName>
>> in the KJV, it is outside
>> <w lemma="strong:H03068">that the
>> <seg><divineName>Lord</divineName></seg></w>
>>
>
> Both are correct. The wiki on OSIS Bibles explains it.
>
> In OSIS, <divineName> can contain <w> but not the other way around. So if
> H3068 is translated by a single word, this is the preferred form.
>
> But if H3068 is translated into a phrase,  then <w> needs to surround the
> whole phrase, but <divineName> needs to surround just Lord. (or God or Yah).
> However OSIS does not allow for this directly. Turns out <seg> can be
> contained by <w> and <seg> can contain <divineName>.
>
> One of the differences between the KJV OT and NT is the precision of
> tagging. In the NT the goal was to tag every word. In the OT, we took what
> we got and that was not a complete tagging. Further the OT was derived from
> ThML or GBF, which places markers where the Strong's number should appear.
> When the OT was automatically converted to OSIS, the starts and ends of the
> marking were heuristically determined. (This was before my time :)
>
> The NASB was provided to us and the phrases were marked with Strong's
> numbers. I just preserved what was there.
>
> I could change the NASB to be <w
> lemma="strong:H3068"><seg><divineName>Lord</divineName></seg></w>, but that
> would only be a bandaid. The real solution is to either have osis2mod
> normalize it to a form that SWORD can handle or to have SWORD handle valid
> OSIS.
>
>
>
>>
>> Is either more correct than the other?
>> The NASB way of doing it means that:
>> a) the osisplain filters in sword don't uppercase it up properly
>> b) SWORD web doesn't work properly with it:
>> You can't click on the word LORD in the NASB and get a popup
>> If you turn strong's numbers on, the number is before LORD, rather than
>> after it.
>> c) The osishtmlhref filters leave the strong's number out altogether
>>
>
> These are all bugs. I'm not a C++ programmer anymore, so these would be
> better handled by someone else.
>
> There is another problem when you have <divineName>Lord's</divineName>. At
> least one of the filters cannot handle the possessive form.
>
> I'd suggest posting this to sword-devel.
>
>
>>
>> God Bless,
>> Ben
>>
>
> In Christ,
>        DM
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.crosswire.org/pipermail/sword-devel/attachments/20080718/abd5bef9/attachment-0001.html