[sword-devel] usfm2osis.py and crossreferences

Peter von Kaehne refdoc at gmx.net
Sat Oct 13 00:02:39 MST 2012

Sorry for that empty email...

Wrt references then -  think as all work on xrefs will need to be iterative, reviweing output etc, it would be good to do this - just as now - as a next and subsequent step. This would cut down on time wasted on recreating working OSIS - particularly on slower computer s (much of my module making happens on an Atom netbook...

So, basically as before usfm2osis - then a separate routine which fixes the xrefs.

-------- Original-Nachricht --------
> Datum: Fri, 12 Oct 2012 23:41:42 -0700
> Von: Chris Little <chrislit at crosswire.org>
> An: SWORD Developers\' Collaboration Forum <sword-devel at crosswire.org>
> Betreff: Re: [sword-devel] usfm2osis.py and crossreferences

> On 10/12/2012 10:53 PM, Peter von Kaehne wrote:
> > Currently usfm2osis.py does not produce complete cross references.
> >
> > a) It translates the in the \xo tag contained origin reference as a
> > <reference type="annotateRef>
> >
> > The probably better way in OSIS would be to tack the origin ref as an
> > osisRef argument into the surrounding note tag.
> >
> > Having said this, it is clear that many real life \xo references
> > would require some level of parsing before they could be made a
> > proper osisRef. This in turn would require usfm2osis.py to make use
> > of the sword bindings etc.
> >
> > b) And then of course is the actual xref which requires even more
> > parsing prior final composition
> >
> > Chris - what is your plan re this? Do you want to include sword into
> > the script and let it deal with the parsing? Or do you want me to
> > rework xreffix.pl to deal with the different output?
> There's a roadmap in usfm2osis.py that includes reference parsing as a 
> post-1.0 feature. At the present, usfm2osis.py is just a USFM to OSIS 
> converter. Parsing references from USFM docs is outside that scope since 
> references in USFM docs are completely unstandardized and the few 
> facilities made available to allow reference parsing (\toc3) are 
> infrequently used.
> I'd like to enable reference parsing (though I don't necessarily believe 
> it can be done reliably), but I see it as a future feature, along with 
> things like generating Sword modules directly--without osis2mod.
> --Chris
> _______________________________________________
> sword-devel mailing list: sword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page

More information about the sword-devel mailing list