Hi there. Cyrille informed me about this issue: https://github.com/crosswire/xiphos/issues/1172
According to Karl, """ The deeper problem causing this mess is that LXX 1Kings 2 is pretty braindamaged. Do mod2imp LXX > /tmp/lxx.imp and look at 1Kings 2. The markup ends with a ridiculously long single verse 2:46, with nothing thereafter intervening from vv. 47-71 and 3:1, then picks up normally again at 3:2. Somebody botched this one pretty badly. """ In the source file used to build the module, 1Kings ends with some verse that have a funny index: it contain alphanumeric entry: 2:46 2:46a 2:46b 2:46c ... and so on until the end of the chapter. And chapter 3 starts directly with verse 2 http://ccat.sas.upenn.edu/gopher/text/religion/biblical/lxxmorph/14.1Kings.mlxx It is the same on a paper version (Septuaginta, A Reader's Edition), so I am assuming it is not a mistake. I can rebuild a LXX module with empty verses where there are missing ones such as in 1Kings 3:1 (that is already the case for Odes which is dealt with already. I plan to make a global check for all books and chapters, just to be safe). What about the alphanumerical verse numbering ? Right now, i simply ignore any alphabetical character when switching from the imp format to the xml one: https://github.com/pierre-amadio/LXX/blob/main/bin/imp2xml.py#L48 This ends up with several verse nodes having the same osisID in the final xml file. What should be the ideal way to deal with those ?
_______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
