Go Bible Creator v2.3.5 does not process \q tags in USFM source text

[GoogleCodeExporter]

I have seen this twice in the last few weeks. 

For USFM files containing instances of the tag \q (each on its own) 
GoBibleCreator v2.3.5 does not process them, but reports them as EXTRA 
UNPROCESSED TAGS and leaves them in the compiled Go Bible text.

This is a serious bug, one which seems to revert a previous BUG FIX 
reported in v2.3.3, namely:

- BUG FIX: The tag parsing was reordered to make sure that short tags 
(e.g., \q or \p) were processed after longer tags which started with 
those same characters (e.g., \qa or \pi).  This prevents the longer 
tag from being truncated early by the short tag and leaving residue 
behind.

I also note that simply replacing tags \q by the equivalent \q1 made no 
difference.  The tags remained in the compiled Go Bible.

Currently the only available workaround is to edit the USFM files, and 
remove all these tags. Unsatisfactory!

Original issue reported on code.google.com by DFH...@gmail.com on 18 Sep 2009 at 7:35

[GoogleCodeExporter]

Fixed in version 2.3.6 (forthcoming).

Original comment by DFH...@gmail.com on 28 Sep 2009 at 12:42

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by DFH...@gmail.com on 8 Dec 2009 at 3:02

• Changed state: Verified