[Bug 101585] New: Cannot build documentation with the latest gtk-doc because of xml error

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=101585

            Bug ID: 101585
           Summary: Cannot build documentation with the latest gtk-doc
                    because of xml error
           Product: Telepathy
           Version: git master
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: logger
          Assignee: telepathy-bugs at lists.freedesktop.org
          Reporter: lantw44 at gmail.com
        QA Contact: telepathy-bugs at lists.freedesktop.org

It seems that gtk-doc tools no longer allow using < and > directly in
<programlisting> after gtk-doc is rewritten in python.


../xml/log-walker.xml:82: parser error : error parsing attribute name
  #include <telepathy-glib/telepathy-glib.h>
                          ^
../xml/log-walker.xml:82: parser error : attributes construct error
  #include <telepathy-glib/telepathy-glib.h>
                          ^
../xml/log-walker.xml:82: parser error : Couldn't find end of Start Tag
telepathy-glib line 82
  #include <telepathy-glib/telepathy-glib.h>
                          ^
../xml/log-walker.xml:83: parser error : error parsing attribute name
  #include <telepathy-logger/telepathy-logger.h>
                            ^
../xml/log-walker.xml:83: parser error : attributes construct error
  #include <telepathy-logger/telepathy-logger.h>
                            ^
../xml/log-walker.xml:83: parser error : Couldn't find end of Start Tag
telepathy-logger line 83
  #include <telepathy-logger/telepathy-logger.h>
                            ^
../docs.xml:14: element include: XInclude error : could not load
../xml/log-walker.xml, and no fallback was found


This problem has been reported to gtk-doc as
https://bugzilla.gnome.org/show_bug.cgi?id=783420, and they recommend using
CDATA sections or |[ and ]|.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.