Page 1 of 1

Support for tags inside _ORIGWORD_ property of href

Posted: Sun Mar 29, 2020 3:50 pm
by RubioTerra
I've been missing the possibility to use tags inside an _ORIGWORD_ property of href. For instance, consider the following:

Code: Select all

<wt>In <FI>the<Fi> beginning<WH000>
When I use a verse rule to turn on hidden links, the _ORIGWORD_ part of href would have to include the italic tags, like this:

Code: Select all

<a href=_ORIGWORD_In <FI>the<Fi> beginning|_NOLINK_|_STRONG_H000>In <FI>the<Fi> begginning</a><WH000>
But this will result in a broken link, because apparently the parser doesn't account for tags inside _ORIGWORD_. The workaround today is not to use the _ORIGWORD_ property. It would be nice if this would be supported. Of course the "original word" field of the popup would have to handle Bible tags also.

Re: Support for tags inside _ORIGWORD_ property of href

Posted: Sat May 09, 2020 8:13 pm
by jonathangkoehn
Greetings RĂºbio,
Do you have an example module that uses the ORIGWORD . I am curious how it works. Thanks

Re: Support for tags inside _ORIGWORD_ property of href

Posted: Mon May 11, 2020 1:37 am
by RubioTerra
There's HiSB, for instance. And also for bible modules exported from iBiblia.

Re: Support for tags inside _ORIGWORD_ property of href

Posted: Mon May 11, 2020 1:32 pm
by JG
I suggest to use square bracket [ ] around the word instead.

Re: Support for tags inside _ORIGWORD_ property of href

Posted: Mon May 11, 2020 5:05 pm
by RubioTerra
Hm... I wonder if it's possible to replace the <FI> tags for brackets in a single verse rule.

Re: Support for tags inside _ORIGWORD_ property of href

Posted: Mon May 11, 2020 6:12 pm
by JG
Is what you really want an _INTERLINEAR_ placeholder?

_ORIGWORD_ is surely just for the original word, which logically cannot be something added by translator, which is what the <FI> tags are supposed to indicate, in this software

Re: Support for tags inside _ORIGWORD_ property of href

Posted: Mon May 11, 2020 10:34 pm
by RubioTerra
Good point JG, I guess it is a deviation from the original purpose. It is being used to make clear what portion of the text refers to the original word being displayed on a popup. This is very useful when one word of the original is being translated into many words. This is not readily obvious for a user reading the translation, but when he points to a word he can see that it is, in fact, a multi-word translation.
I'm not sure what this placeholder should be called, though.

Re: Support for tags inside _ORIGWORD_ property of href

Posted: Mon May 11, 2020 11:04 pm
by jonathangkoehn
So basically something to differientate between direct translation (some call it word for word/literal) and words added to smooth the translation?

NASB tends to use italics for words added for smoothing.

Re: Support for tags inside _ORIGWORD_ property of href

Posted: Mon May 11, 2020 11:47 pm
by JG
RubioTerra wrote:Good point JG, I guess it is a deviation from the original purpose. It is being used to make clear what portion of the text refers to the original word being displayed on a popup. This is very useful when one word of the original is being translated into many words. This is not readily obvious for a user reading the translation, but when he points to a word he can see that it is, in fact, a multi-word translation.
I'm not sure what this placeholder should be called, though.
I have made some Greek interlinear and reverse interlinear, Bibles for myself, and found it was the way forward to use the [ ] instead. If Costas makes provision in the future then it would be easy to change.