Thanks DM, I agree - mod2imp is only for getting some clues as to what went on "under the hood" when the module was built using osis2mod.
The OSIS file from which the module was made was generated by [the latest] usf2m2osis.py It is well-formed and valid to the schema, and the only milestone elements therein were for chapters and verses. As it happens, the only div elements in the OSIS were for the 66 books. This is because the USFM files didn't have any section titles \s or major section titles \ms viz. Count SFM tag Description ----- -------- ----------- 01402 \add Translator's added words begin 01402 \ add* Translator's added words end 00001 \b Blank line in poetry (e.g. between stanzas) 01189 \c Chapter 01175 \cd Chapter description 00215 \cl Chapter label 00066 \id Identification 00066 \mt1 Major title (portion 1) 00067 \mt2 Major title (portion 2) 00041 \mt3 Major title (portion 3) 04015 \p Paragraph 00012 \q Poetic line 00012 \q2 Poetic line (indent 2) 00022 \qa Acrostic heading 00069 \rem Remark 31102 \v Verse[s] It's still a relatively simple Bible module with default KJV v11n. The only "corner case" tags are the chapter labels, and there's already an issue on MODTOOLS for that (wrt usfm2osis.py) NB. Text development for the translation revision is not yet finalised. David -- View this message in context: http://sword-dev.350566.n4.nabble.com/MinimumVersion-property-in-module-conf-files-tp4652983p4653003.html Sent from the SWORD Dev mailing list archive at Nabble.com. _______________________________________________ sword-devel mailing list: [email protected] http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
