GNOME Bugzilla – Bug 571964
Missing tooltip attribute for ref in compound.xsd
Last modified: 2009-12-30 13:39:01 UTC
The attribute tooltip is missing for refTextType makes XML parsers issue warnings and even stop working on the node. --- orig/compound.xsd +++ new/compound.xsd @@ -100,6 +100,7 @@ <xsd:extension base="xsd:string"> <xsd:attribute name="refid" type="xsd:string" /> <xsd:attribute name="kindref" type="DoxRefKind" /> + <xsd:attribute name="tooltip" type="xsd:string"/> <xsd:attribute name="external" type="xsd:string" /> </xsd:extension> </xsd:simpleContent>
Apparently, this bug still exists still today (1.6.1). The fix is just adding this one line for the to compound.xsd - except of course if the tooltip attribute is not supposed to be used at all. It seems that this bug makes a difference only if source code is inlined. The lines look like this: <codeline lineno="592"><highlight class="normal"><sp/><sp/><sp/><sp/><sp/><sp/><sp/><sp/></highlight><highlight class="keywordflow">return</highlight><highlight class="normal"><sp/><ref refid="classorg_1_1jgraph_1_1graph_1_1AbstractCellView_1a24cb13823e5addf512540088708dc405" kindref="member" tooltip="Editor for the cell.">cellEditor</ref>;</highlight></codeline> A second bug in compound.xsd, in docSimpleSectType, e.g. for XPaths /doxygen/compounddef/sectiondef/memberdef/detaileddescription/para/simplesect, as seen in the following snippet of a class xml: <detaileddescription> <para> <simplesect kind="see"> <para> <ref refid="classorg_1_1jgraph_1_1JGraph_1ae2c9b10de804b706c53e732a66577ffc" kindref="member">getUIClassID</ref> </para> <simplesectsep /> <para> <ref refid="classorg_1_1jgraph_1_1JGraph_1a30845e9850646725817c3e620848bc13" kindref="member">readObject</ref> </para> </simplesect> </para> </detaileddescription> The problem is that the XSD does not allow <simplesectsep /> in this place.
Confirmed. I'll fix both issues in the next subversion update.
This bug was previously marked ASSIGNED, which means it should be fixed in doxygen version 1.6.2. Please verify if this is indeed the case and reopen the bug if you think it is not fixed (include any additional information that you think can be relevant).