As u2o.py is not supported by CrossWire, the first response ought to be to describe how usfm2osis.py deals with the `\va_#\va*` tag pair.
It's quite likely that both scripts result in an OSIS construct that is far from meeting requirements. An alternative verse number (or chapter number) should not be given merely an osisID as this makes no sense for the v11n to which a module is to be built. Aside: There would really need to be some mechanism in place for these alternate verse or chapter numbers to be usable if two different modules were to be built from the same OSIS XML file, each having a their own versification scheme. Alternative numbers in USFM are designed to cover ecumenical translations where more than one Bible version is to be printed, having different versification schemes according to the target consituency, (e.g.) Protestant, Catholic, Orthodox, etc. If only one module is envisaged, the alternate numbers are purely informational. They should then have no function other than in displaying what some printed versions might have as the verse or chapter number for the same passage. I fear the script developers have not thought this through to basic principles. Best regards, David -- Sent from: http://sword-dev.350566.n4.nabble.com/ _______________________________________________ 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
