On 30/12/14 06:29, Peter von Kaehne wrote:
It is very well written and neatly done and does its job with near
perfection. I would welcome contributions to it, as long as they are
equally well done. 
Just for your info: usfm2osis.py basically treats each USFM book as a huge hunk of text to which it does a large number of global text substitutions. Although this, in fact, does make it a very neat and tidy program, I don't think it's nearly perfect. The main disadvantage of using this method can be expressed as two results to the user (and I think these are quite serious defects in terms of reliable module making as other threads attest):
  1. Certain errors or non-conformities in the USFM are not even detected (e.g., when \d is used as a paragraph type marker with verses logically "inside" the \d marker which is not actually documented [nor banned] in the USFM specification)

  2. If there is an error, the program is completely unable to give the user any indication of where (e.g., line number or chapter/verse) the error occurs because it has absolutely no concept of "position within the file".

Perhaps this is accounted for by running some other program first to thoroughly check that the formation of the USFM is within the expected/programmed range???

Robert.




_______________________________________________
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

Reply via email to