|
Hello, DM.
I agree that your interpretation of OSIS makes sense. However,
given that this interpretation is totally foreign to the
philosophy behind USFM and Paratext, and that automating a
transformation between the many hundreds of Bibles in USFM/USX
source and finer points of OSIS niceties is impractical, I'm
disinclined to do any more than I have done to reconcile the two
philosophies in the form of an automatic file conversion process.
As you said, the important thing is that it displays. It does.
The vast majority of the World's Bibles are now available in USFM
and/or USX. (Those two formats are totally equivalent in content
and abilities, and conversion back and forth without loss happens
in Paratext.) OSIS would be dead to me if it weren't for the Sword
project. Polishing OSIS at this point seems to be a fruitless
exercise unless it is to improve compatibility with the winning
format. USFM/USX wins based on use, software support, and adoption
by the major Bible translation agencies of the world as well as by
significant open source projects. So, with apologies and all due
respect to the team that devised OSIS and helped refine it
(including myself), I think we can dispense with the illusion that
we can use OSIS without regard to how automated conversions from
USFM/USX happen. The "start fresh" idea sounded good at the time,
but so did the technical superiority of Betamax video tape over
VHS at one time. If we are to improve OSIS at all, it needs to be
towards better compatibility with the Bible translation world and
better interchange. That may or may not be harder than replacing
OSIS with something better.
The USFM/USX philosophy is more like a word processor markup than
a tree-structured document. USFM doesn't mark sections or nest
them. It marks titles of various sorts and paragraphs/stanzas of
various sorts. It doesn't care about the relative ordering of
different levels of titles, or if a title corresponds to a
chapter. This is kind of how a word processing program works, but
a bit more semantic. It is a mix of semantic and presentational
markup. That is OK. It has a lot going for it: over 1400 Bible
translations, so far. I know the shortcomings of USFM as well as
anyone, working with it every day, but seriously, nothing else is
better over all. Not even USFX, because USFX hasn't been used by
many people besides myself.
Anyway, the eBible.org repository is in "stable" maintenance mode,
right now. I'll update modules here and there, but I'm not going
to muck with the core USFM or USX -> USFX -> OSIS converter
for a while. My foreground task has shifted to another higher
priority project.
On 09/22/2015 07:06 AM, DM Smith wrote:
Re: title and the various attributes. The most important thing is
that it displays. Which it does. It may look funky under certain
circumstances. All depends on what the frontend expects as a
hierarchy of titles.
For example:
main - the outermost title, typically the title of
a book
chapter - the main title of a chapter
no attr - a section title
sub - a sub-title of another title
continued - an additional line of the immediately
prior title
Re: title and type=parallel, the OSIS manual
recommends as you have noted, but when it describes the
purpose of parallel it is otherwise. IMHO, one of those two
places is wrong or the document needs improvement.
r title[@type='parallel']/reference
r
- Heading - Parallel References
In looking at how SWORD and JSword frontends
handle this, I looked at Bible Desktop, Xiphos and
Eloquent.
In Bible Desktop, toggling references just
changes whether the link is active or not. So it looks good.
In Xiphos, footnotes are toggled, so it shows as
link text at all times. So it looks good.
However, in Eloquent (successor to MacSword),
the titles are not shown at all. I think it is a bug in
Eloquent.
I think both BD and Xiphos (SWORD? CSS?) would
do well to eliminate the space between immediately adjacent
titles.
In Him,
DM
On 09/21/2015 02:11 PM,
DM Smith wrote:
I found the following in eBible’s kud2008eb. The following is Matt.1.1.
<div type="x-milestone" subType="x-preverse" sID="pv1"/><div sID="gen5" type="section"/><title canonical="false" type="sub">Yeisu Besinana ana mumugao </title><title type="parallel">(<reference osisRef="Luke.3.23">Luke 3:23-38</reference>) </title><div sID="gen6" type="x-p"/> <div type="x-milestone" subType="x-preverse" eID="pv1"/>Laulele teina Besinana Yeisu ana mumugao vehabadi. Yeisu tubuna Deivida, na Deivida tubuna mugamugaina Abelaham.
The problem is that the osisRef is incomplete. It should be osisRef="Luke.3.23-Luke.3.38”.
The impact is that clicking on the reference in Bible Desktop, it only shows Luke 3:23.
This is a known artifact of the current conversion
from human-readable references to machine readable
references. USFM doesn't directly handle reference
links, so I synthesize them on conversion to USFX,
which is then converted to OSIS. This will probably
be fixed eventually, but don't hold your breath
waiting for it. It probably involves rewriting the
code that does that, which is currently a set of 7
XSLT processes. I have a lot of higher priorities on
my work list. If you prefer, I could inhibit such
osisRef entries altogether until such time as I
might possibly get around to improving the reference
reading process. (It is kind of complicated, since
"human readable" actually means "human readable in
any of about 7,000 languages".) The alternative of
getting all of the translators (or anyone else) to
go back and manually enter machine-readable
references probably won't happen during this
century.
The following is just extra. It is in addition to the bug mentioned above.
It is also really odd that there is a second title that contains a parenthesized, inlined reference.
The type="sub” is meant to give a sub part of a title. Since there is no prior title, it shouldn’t be sub. As a plain title, it doesn’t need an attribute.
That "sub" in the title probably came from \s
(section title), which could be (but isn't always)
under \ms (main section title). It does no harm, as
far as I can tell, and having it there covers the
case where \s follows \ms. Let's not move the goal
posts any more than we have to.
Also, the type=“parallel” is inappropriate. The OSIS manual gives that parallel is meant to provide the title in another language. The type sub is probably more appropriate. Or even type="continued” which means that this title continues the last.
Page Appendix F, page 138 of the OSIS User Manual
seems to disagree with you about the proper
conversion of the USFM \r tag.
Note that canonical=“false” is redundant. All titles by default are canonical=“false”.
Yes, it is. That is certainly not the only
redundancy. It is not harmful.
--
Aloha,
Kahunapule Michael Johnson
MICHAEL
JOHNSON
PO BOX 881143
PUKALANI HI 96788-1143
USA |
eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule |
_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at
above page
_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
--
Aloha,
Kahunapule Michael Johnson
MICHAEL JOHNSON
PO BOX 881143
PUKALANI HI 96788-1143
USA |
eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule |
|
