On 05/08/12 00:15, Chris Little wrote:
Bug reports are welcome if you try it, but this is still largely
untested stuff, so expect bugs.
The other script in the above directory can be used to identify all of
the USFM tags used in a set of files and will specify which of them
are unknown to the USFM 2.35 reference.
I'm not sure how to submit bug reports, but in testing this on our
in-progress translation I get:
From: usfmtags.py
Known USFM Tags: \b, \bk, \bk*, \c, \f, \f*, \fq, \fr, \ft, \h, \id,
\ide, \io1, \io2, \ior, \ior*, \iot, \ip, \is, \it, \it*, \li, \m,
\mr, \ms, \mt, \mt1, \mt2, \nb, \p, \q, \q1, \q2, \q3, \r, \s, \s2,
\s3, \tc1, \tcr2, \tr, \v, \x, \x*, \xo, \xt
Unrecognized USFM Tags:
which is correct, but from usfm2osis.py I get:
Encoding unknown, processing as UTF-8.
Encoding unknown, processing as UTF-8.
Unhandled USFM tags: \n, \o1, \o2, \or, \or*, \ot, \p, \v (8 total)
Consider using the -r option for relaxed markup processing.
which are all false errors. The n is actually nb in the USFM, and the
others are all from introduction tags, i.e., io1 io2, ior, etc.
