On 09/11/10 22:10, lomov.vl wrote:
Hi.
On 9 Nov, 03:27, Stuart Rackham<[email protected]> wrote:
I don't have xmlto(1) installed so I used xmllint(1) to validate and there were
no errors:
$ $ xmllint --noout git-web--browse.xml
I then ran a2x to generate git-web--browse.1:
$ a2x -dmanpage -fmanpage git-web--browse.xml
It ran without errors and the man page looked fine.
[...]
I don't understand, I downloaded both your 896 files from pastebin and they
validate and generate manpages:
$ xmllint --noout git-mergetool--lib.xml
$ a2x -fmanpage -dmanpage git-mergetool--lib.xml
[...]
I'm still not clear on this, do we still have a problem with the AsciiDoc
output?
Yes, I have. Do you try
$ xmllint --noout --postvalid git-web--browse.xml
?
Seems that '--postvalid' gives this error (by default this option is
passed to xmllint by xmlto). The '--valid' option also raises error
message.
Put it in another way, the xml file generated by any version beginning
from rev. 883 gives not valid xml file. Seems that this problem is
another side of this:
http://groups.google.com/group/asciidoc/browse_thread/thread/1b3f88f1f8118ab3
I had problem with the same file (git-lib--mergetool) earlier (the
same error) but didn't report about it. Now I do. From my point of
view: the 'refentrytitle' tag is not in file due to postponed title
processing (as I understand this was the solution to that thread).
(Mentioned in that thread rev. 02c8e59ce1 is 877, the last working for
me rev. 882 is a40a136d1312.)
Any thoughts?
(I wouldn't pretend that I know python good enough to understand the
changes between 882->883, I see them but don't understand the
consequnces).
I see the problem now (if I hadn't forgotten the xmllint(1) --valid option I
would have seen it earlier). Yes, the refentrytitle has been dropped because the
man page title (saved as mantitle attribute) has no attribute substitution, the
{litdd} in the title effectively resulted in nested simple attribute references.
I think (but not sure) this was not a problem prior to 756:2e1c5b2adbfa.
I've committed a fix, please try it and report back:
http://code.google.com/p/asciidoc/source/detail?r=9fb64750d9996796a2c0d87c037ca3aab300b507
Cheers, Stuart
--
You received this message because you are subscribed to the Google Groups
"asciidoc" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/asciidoc?hl=en.
