After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 562113 - documentation doesn't validate
documentation doesn't validate
Status: RESOLVED FIXED
Product: anjuta
Classification: Applications
Component: documentation
2.24.x
Other Linux
: Normal normal
: ---
Assigned To: Anjuta maintainers
Anjuta maintainers
Depends on:
Blocks:
 
 
Reported: 2008-11-24 11:23 UTC by Gilles Dartiguelongue
Modified: 2009-03-02 20:53 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
build.log (4.53 KB, text/plain)
2008-11-24 11:27 UTC, Gilles Dartiguelongue 		Details

Description Gilles Dartiguelongue 2008-11-24 11:23:16 UTC 
See attached log.
Comment 1 Gilles Dartiguelongue 2008-11-24 11:27:36 UTC 
Created attachment 123316 [details]
build.log
Comment 2 Johannes Schmid 2008-11-24 12:45:52 UTC 
Yeah, it's not really a bug in the documentation but in the way xmllint assumes that the documentation only contains ASCII characters. It contains some (valid) UTF-8 characters. It possible to fix that by replacing all this characters it just didn't have any priority yet.
Comment 3 Johannes Schmid 2009-03-02 08:18:19 UTC 
OK, most of this is now fixed. The remaining problem is:

xmllint --noout --noent --path C:./C --xinclude --postvalid ./C/anjuta-build-tutorial.xml
./C/anjuta-build-tutorial.xml:9: element book: validity error : root and DTD name do not match 'book' and 'manual'
Document ./C/anjuta-build-tutorial.xml does not validate
Comment 4 Claude Paroz 2009-03-02 08:48:45 UTC 
Replace <!DOCTYPE manual... with <!DOCTYPE book
Then include listitem content inside para, and you will have most errors gone.
Comment 5 Shaun McCance 2009-03-02 17:03:56 UTC 
There really shouldn't be any problem with valid UTF8.  xmllint does not assume ASCII, unless the XML declaration declares the document to be in ASCII.
Comment 6 Johannes Schmid 2009-03-02 17:15:23 UTC 
It's no utf-8 problem anymore (I think it was once). Anyway, changing the DOCTYPE led to so many validation errors that I gave up on it. Maybe someone knows a solution.
Comment 7 Claude Paroz 2009-03-02 20:21:01 UTC 
Yes, there was many validation errors :-) Hopefully fixed. Please check and report any more validation problems... or close the bug.
Comment 8 Johannes Schmid 2009-03-02 20:53:03 UTC 
Fixed, thanks to Claude for investigation!