1
Vote

Mishandling of USFM tag \vp_...\vp*

description

Verses that contain the published verse text tag pair \vp_...\vp* are mishandled by the Check for Versification Issues feature.

They report "No actual verse text detected;" and related errors.

Example of such a verse:

\v 4 \vp 1d\vp* Long\fig 16|HK 17A|span|||Haus bilong king long biktaun Susa. |(1.4)\fig* driman em i lukim olgeta samting bilong graun i paul nabaut, na i gat bikpela nois na klaut i pairap na graun i guria na ol samting i longlong nabaut.

Corresponding output:

42-ESG.usfm 1 4 No actual verse text detected; empty verse
42-ESG.usfm 1 No actual verse text detected; only tag information detected [p 1d]
42-ESG.usfm 1 No actual verse text detected; only tag information detected [p* Long\fig 16|HK 17A|span|||Haus bilong king long biktaun Susa. |(1.4)\fig* driman em i lukim olgeta samting bilong graun i paul nabaut, na i gat bikpela nois na klaut i pairap na graun i guria na ol samting i longlong nabaut.
]

file attachments

comments

DavidHaslam wrote Jun 25, 2013 at 1:46 PM

Zip file attached for testing purposes.

Part of the Tok Pisin Bible downloaded today from ftp://ebible.org/pub/Scriptures

DavidHaslam wrote Jun 29, 2013 at 8:34 AM

The taglist file includes this advice:

// -Tags in a section will be processed by the parser in the order listed below. Be
// sure that you put them in the right order so that the tag will be processed
// properly. Example: "\up" would need to go before another tag called "\u"
// otherwise processing the "\u" will kill off all of the "\up" tags and leave
// at trailing p sitting in your text on the phone

DavidHaslam wrote Jun 29, 2013 at 8:34 AM

It's evident that this prioritisation has not been adequately thought out for tag names that begin with the letters c and p.

DavidHaslam wrote Jun 29, 2013 at 8:35 AM

Corrigendum:

It's evident that this prioritisation has not been adequately thought out for tag names that begin with the letters c and v.