<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 05/08/12 00:15, Chris Little wrote:<br>
<blockquote cite="mid:501D124C.6080802@crosswire.org" type="cite">Bug
reports are welcome if you try it, but this is still largely
untested stuff, so expect bugs.
<br>
<br>
<br>
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.<br>
</blockquote>
I'm not sure how to submit bug reports, but in testing this on our
in-progress translation I get:<br>
<br>
From: usfmtags.py<br>
<blockquote>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<br>
Unrecognized USFM Tags: <br>
</blockquote>
which is correct, but from usfm2osis.py I get:<br>
<blockquote>Encoding unknown, processing as UTF-8.<br>
Encoding unknown, processing as UTF-8.<br>
Unhandled USFM tags: \n, \o1, \o2, \or, \or*, \ot, \p, \v (8
total)<br>
Consider using the -r option for relaxed markup processing.<br>
</blockquote>
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.<br>
<br>
Hope this helps,<br>
Robert.<br>
<br>
<br>
</body>
</html>