[sword-devel] ThML and OSIS references
Adrian Korten
sword-devel@crosswire.org
Tue, 23 Dec 2003 15:59:51 +0700
This is a multi-part message in MIME format.
--------------060702050507090302030702
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Good day,
That makes sense and is what I thought should have been happening. It
isn't working with neither a Thai commentary or dictionary. This
commentary and dictionary use ThML formatting so maybe this feature is
not supported by Sword. I did not test it with OSIS formatted files so
maybe the 'osisref=' attribute is properly handled.
Attached is a file with three examples that all use the attribute
'passage='. With two of them, there is no pop-up display or a jump-to
reference with right-click. With the third one, the display and jump-to
reference look good but are invalid -- the passage within the markers is
displayed and not the actual 'passage='. It seems that 'passage=' is not
picked up by the program.
This is not a big concern for me; I was just playing with it to see if
it could be done. Writing a python/perl script to properly insert the
reference info in OSIS or ThML format seems like a lot of work for the
Thai modules. However, there does not seem to be a way for a non-English
commentary/dictionary to insert references with actual Bible verses
behind a user displayed piece of arbitrary text (Thai or otherwise).
ak
p.s. It was interesting to see a mention of a python project in the
works. I'm just beginning to play more with python and will be
interested to see how it goes.
Troy A. Griffitts wrote:
> Adrian,
> I can only speak concerning OSIS, but authoritative osisRef
> abbreviations can be found here:
>
> http://www.bibletechnologieswg.org/osis/specs/
>
> Top Section, last entry: Bible Book Names
>
> This means that you would use these (roman/latin script) abbreviations
> in the osisRef attribute, but would have anything you would like in the
> text node of the reference, e.g.
>
> <reference osisRef="John.3.16">THAI UTF8 TEXT HERE</reference>
>
> Hope that makes sense,
>
> -Troy.
>
> PS. Just so Chris doesn't jump all over me... There has been 'talk'
> about providing a way to translate the meta information (tag names,
> attribute name, etc.) into other languages (would use UTF8). If this
> ever happened, than it would follow that these abbreviations would also
> likely be candidates for translation. I think the whole idea is silly
> :), but hey, it may happen anyway! :)
>
>
>
> Adrian Korten wrote:
>
>> Good day,
>>
>> I have a question about the markup for references within a text to
>> another bible verse with either ThML or OSIS. The short tutorial has a
>> note as described below.
>>
>> "OSIS includes a reference element for this purpose, and for our
>> example, an instance may look something like:
>> Please see <reference osisRef="Jas.1.19">James 1:19</reference>"
>>
>> Should the osisRef (or ThML equivalent) field use the KJV English book
>> abbreviations? Or should it use the original language book
>> abbreviations? Should they be encoded as UTF-8 characters?
>>
>> ak
>>
>>
>> _______________________________________________
>> sword-devel mailing list
>> sword-devel@crosswire.org
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>
>
> _______________________________________________
> sword-devel mailing list
> sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
>
--------------060702050507090302030702
Content-Type: text/plain;
name="scripref.txt"
Content-Transfer-Encoding: 8bit
Content-Disposition: inline;
filename="scripref.txt"
$$$กลับใจเสียใหม่
(ดู กลับใจใหม่) <scripRef passage="John 3:16">ลนต.1:3</scripRef>
$$$กลับใจใหม่
หันจากบาปมานอบน้อมถ่อมใจลงเชื่อฟังพระเจ้า
$$$กิตติคุณ
(ดู ข่าวประเสริฐ) test1 <scripRef passage="Rom. 8:30">Romans 8:29</scripRef> test2 <scripRef passage="Rom. 8:29,30">verses 29 and 30</scripRef>
--------------060702050507090302030702--