[sword-devel] 1.6.0 bugs

[DM Smith]

I've just fixed an osis2mod bug found in the latest 1.6.0 RC.

We do have some open issues/bug reports against osis2mod. I'd like a  
sense of whether these are still a problem and if so, how urgent it is  
to fix them.

I always advocate using the latest osis2mod from SVN and I'm pretty  
sure that this is true of modules making it into the Crosswire  
repository. My concern is more for those that grab a published copy  
and make personal modules.

Here are the issues:
http://www.crosswire.org/bugs/browse/API-14 - This was a general  
complaint about how osis2mod handled titles badly.
	I think this is fixed. Need someone to verify it in a 1.6.0 front-end.

http://www.crosswire.org/bugs/browse/API-94 - Convert numeric entities  
to UTF-8.
	Nothing has been done on this one. Having numeric entities frustrates  
normalization to UTF-8. Having numeric entities may cause problems in  
some front-ends. This one can be done by using a program such as  
xmllint.

http://www.crosswire.org/bugs/browse/API-96 - crash on apocrypha.
	Is this still a problem?

http://www.crosswire.org/bugs/browse/API-101 - Book intros get placed  
in prior book.
	I think this has been fixed. Can someone please verify?

http://www.crosswire.org/bugs/browse/API-105 - does not handle <lg>  
element well.
	I think this is fixed. Need someone to verify it in a 1.6.0 front-end.

http://www.crosswire.org/bugs/browse/API-111 - give location in input  
messages
	Nothing has been done on this one.

http://www.crosswire.org/bugs/browse/API-114 - use refSystem from the  
OSIS document
	Nothing has been done on this one.

Not logged in Jira (yet), but on sword-devel:
a) Have osis2mod suggest a conf in the same manner that tei2mod does,  
but have both write it to a file.
b) Fill out the conf from informational entries in the OSIS header.
c) Make osis2mod into an class that can be used in a front-end.

Additionally, there are 4 bug reports against MHC, which is waiting on  
osis2mod to be fixed.

I have recently fixed the following:
* API-113 allow standard input of osis
* API-109 add info, warning or error to messages
* API-112 use osisID or osisRef in messages
* API-110 improve exit codes.

Thanks.

In Him,
	DM