Ok, thanks for the info. So I'll be using the standard (English-looking) id's for osisID. But I guess I'll sacrifice sID (and eID) to provide the extra information about Finnish abbreviations, with the cost of some consistency.<br>
<br>Btw, are there any other OSIS references than the User Manual by Patrick Durusau (found at <a href="http://www.bibletechnologies.net/">http://www.bibletechnologies.net/</a>) and the wiki (which I never can find, should bookmark it...)?<br>
<br>Markku<br><br><br><br><br><div class="gmail_quote">2012/1/10 Todd Tillinghast <span dir="ltr"><<a href="mailto:todd@snowfallpress.com">todd@snowfallpress.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
Markku,<br>
<br>
The values in the osisID attribute for scripture references are
standardized. Techincially you can define your own reference system
but 100% of the scripture texts encoded are using the standard OSIS
defined Bible book names along with numbers for chapters and
verses. These Bible book names are not English or any other
languages and are language independent (even though they look like
English names).<br>
<br>
The sID attribute can be any value you with (limited to valid
characters for the attribute) and MUST match the value of the eID
attribute of the paired "milestone" element.<br>
<br>
As a PRACTICE I like to use <verse sID="Matt.2.1"
osisID="Matt.2.1"/> for verses and <q level="1"
sID="Matt.2.6!Quote.1"/> and <q level="1"
eID="Matt.2.6!Quote.1"/> for quotes. I like this because I can
automatically generate unique sID and eID values. <br>
<br>
Todd<br>
OSIS Technical Committee<div><div class="h5"><br>
On 1/10/2012 4:07 AM, Markku Pihlaja wrote:
</div></div><blockquote type="cite"><div><div class="h5">Hi everyone,<br>
<br>
Some background info first (skip to "------" if you want to get
straight to business!).<br>
<br>
The current official Finnish translation of the Bible was
published in 1992 - and the official digital source files also
date back to that time. Now the time has come to update the source
files to a modern version, and we've selected OSIS for the job.<br>
<br>
The original source files included certain coding for headings,
chapter and verse numbers etc., and I have now been doing a lot of
complicated regexp replacements to convert them to OSIS.<br>
<br>
On the way, I've come across quite a number of questions that
don't get answered by the OSIS manual. I believe many of them are
familiar to you as well, so I'll be feeding them to you in the
near future.<br>
<br>
I've actually never used a mailing list like this before, so I'm
not familiar with any etiquette or standard behaviour that might
be required - please inform me if I'm doing something funny ;).<br>
<br>
But let's finally get to business. I guess I should post one
question at a time, with a descriptive message subject. So I'll
stat with this, more to come:<br>
<br>
------<br>
<br>
osisID vs. language<br>
<br>
Should osisID's e.g. in <verse> tags always be formed from
the English abbreviations of books? And if that is the case, can I
somehow include an additional attribute for the Finnish versions?<br>
<br>
That is: I'd like to tag my verse like this: <br>
<verse sID="Luuk.13.10" osisID="Luuk.13.10" /> <br>
("Luuk." instead of "Luke")<br>
but that would probably make my file rather incompatible with any
international software that uses OSIS files.<br>
<br>
On the other hand, our main target group are Finnish publishers,
and having the osisID's solely in English would not be very good
service for them.<br>
<br>
<br>
<br>
<fieldset></fieldset>
<br>
</div></div><pre>_______________________________________________
osis-users mailing list
<a href="mailto:osis-users@crosswire.org" target="_blank">osis-users@crosswire.org</a>
<a href="http://www.crosswire.org/mailman/listinfo/osis-users" target="_blank">http://www.crosswire.org/mailman/listinfo/osis-users</a>
</pre>
</blockquote>
<br>
</div>
</blockquote></div><br>