Hi DM, Thanks for those observations. The output from MOD2IMP should be seen merely as circumstantial evidence as to what has happened after using OSIS2MOD to make the module.
cf. Even MOD2IMP has a small amount of "lossyness", miniscule when compared to MOD2OSIS. These trivial quirks are a result of using http://crosswire.org/ftpmirror/pub/sword/utils/perl/imp2osis.pl imp2osis.pl on the IMP file that I had already created by other means from the supplied source text. It seemed sensible to me (after reading stuff from Chris) to move on from using IMP2VS to generating a proper OSIS XML file that I can then validate using XML Copy Editor. I am using imp2osis.pl with the -m option. Earlier I had tried it without this option, but I subsequently found that using the milestoned version solved some matters relating to displaying colophons. David -- View this message in context: http://sword-dev.350566.n4.nabble.com/osis2mod-and-NT-heading-tp3071316p3072490.html Sent from the SWORD Dev mailing list archive at 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
