Markup ambiguity in module FinPR92

Module error:

One of the 1986 versification markers has the '>' missing!

$$$I Chronicles 12:11
<WTH12:12kuudes Attai, seitsemäs Eliel,

Caution: Some of the versification markers occur later within the verse text than at the start.

As well as 1858 'mapped single verses' there are also some 127 other types:

• Linked verses
• Split verses
• Moved verses
• Psalm titles

Presumably the "H" denotes something in Finnish.

Proposed solution:

Rebuild the module with <H ... > all replaced by {H ... }, plus the particular correction in I Chronicles 12:11.
cf. Braces {} would not trigger the wrong interpretation as XML markup.

Assuming we might no longer have the original source text from 2003 or earlier, if we use mod2imp as the first step, then the replacements would actually be "<WT" to "{" and ">" to "}". Then use imp2vs to rebuild the module.

OK - I've just rebuilt the module as per my previous comment.
Also replaced every instance of multiple whitespace by a single space.

I've submitted it via the usual email route.

I just concluded that the "H" was an artifact of our SWORD utilities,
so I've just rebuilt the module with the "H" removed from the verse map braces.

The rebuild has been sent to modules at crosswire dot org.

False Strong's tags are also present in our other two Finnish modules, FinPR and FinBiblia.

Neither of these were UTF-8 encoded, so these will first be changed to UTF-8.

When is the updated FinPR92 going to be released?

I've just updated the FinPR module as follows:

Version=1.3
History_1.3=Changed encoding to UTF-8. Rebuilt module with braces {} instead of lt/gt for av11n refs (2013-01-21)

The rebuild has been sent to modules at crosswire dot org.

I've just updated the FinBiblia module as follows:

Version=1.2
History_1.2=Changed encoding to UTF-8. Rebuilt module with braces {} instead of lt/gt for av11n refs (2013-01-21)

The rebuild has been sent to modules at crosswire dot org.

The updates to these 3 Finnish modules should also solve the errors generated while making the Lucene search indices, as recently reported by Martin Denham when he tried to make the search index for module FinPR92 for download by And Bible.

Follow-up tasks:

See http://crosswire.org/wiki/User:Osk/Todo#Modules_needing_v11n_rebuilds_.28post_JSword_av11n-compatibility.29

Submissions of modules exported via mod2imp are fine, but they will never actually be imported and released. We haven't changed to a policy where we re-import exported texts. The only case wherein a text would be imported from an exported source would be if the original imported doc were somehow lost. That would be rare, and is in any case not so with the Finnish Bibles.

By all means, do continue submitting modified .imp files. They are at least a good checksum for the correction of the original documents. But it does take more time than a simple submission of a ready-to-import module since I've got other tasks ahead of it in my queue.

OK - thanks for the positive note in your response.