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 642852 - Link titles contain invalid HTML due to ecaping before truncation
Link titles contain invalid HTML due to ecaping before truncation
Status: RESOLVED OBSOLETE
Product: doxygen
Classification: Other
Component: general
1.7.2
Other Linux
: Normal minor
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
[moved_to_github]
Depends on:
Blocks: 650544
 
 
Reported: 2011-02-21 04:59 UTC by Ethan Steinberg
Modified: 2018-07-30 10:35 UTC
See Also:
GNOME target: ---
GNOME version: ---



Comment 1 Murray Cumming 2011-02-21 10:28:49 UTC
Yes, thanks, and this is a problem for the unstable/ URL too.

classGtk_1_1Entry.html does seem to be in the tarball, so I guess this is a problem with library.gnome.org. Reassigning.
Comment 2 Frederic Peters 2011-02-21 10:40:04 UTC
I had a quick look, and a possible cause is those errors:

 $ xmllint classGtk_1_1Entry.html 
classGtk_1_1Entry.html:1149: parser error : CharRef: invalid decimal value
ion in the entry contents (returned by get_text()) to a position in the entry&#3
                                                                               ^
classGtk_1_1Entry.html:1149: parser error : xmlParseCharRef: invalid xmlChar value 0
ion in the entry contents (returned by get_text()) to a position in the entry&#3
                                                                               ^
classGtk_1_1Entry.html:1170: parser error : CharRef: invalid decimal value
ion in the entry contents (returned by get_text()) to a position in the entry&#3
                                                                               ^
classGtk_1_1Entry.html:1170: parser error : xmlParseCharRef: invalid xmlChar value 0
ion in the entry contents (returned by get_text()) to a position in the entry&#3
                                                                               ^
classGtk_1_1Entry.html:1204: parser error : CharRef: invalid decimal value
ion in the entry contents (returned by get_text()) to a position in the entry&#3
                                                                               ^
classGtk_1_1Entry.html:1204: parser error : xmlParseCharRef: invalid xmlChar value 0
ion in the entry contents (returned by get_text()) to a position in the entry&#3
                                                                               ^
I didn't find occurences of the broken "&#3..." in other files.
Comment 3 Murray Cumming 2011-02-21 10:51:54 UTC
I guess it's complaining about that &#3 in this <a> code in the html:
  title="Converts from a position in the entry contents (returned by get_text()) to a position in the entry&#3..."

  Doxygen takes that from the comment for the function that it's linking to with that <a> link:

  /** Converts from a position in the entry contents (returned
   * by get_text()) to a position in the
   * entry's Pango::Layout (returned by get_layout(),
   * with text retrieved via pango_layout_get_text()).
   * @param layout_index Byte index into the entry layout text.
   * @return Byte index into the entry contents.
   */
  int layout_index_to_text_index(int layout_index) const;

I guess that it's meant to be a three-digit decimal number with a closing ;, but that doxygen is truncating and elipsizing it after escaping the ', instead of before. Reassigning to doxygen.
Comment 4 albert 2018-06-17 10:05:56 UTC
Unfortunately seen the time the issue was reported and the information available (no small example attached) it is hard to see what went wrong.
Looking at the still available page https://developer.gnome.org/gtkmm/stable/classGtk_1_1Entry.html the problem was not present here anymore.

I think the problem has been solved in the mean time.
Comment 5 André Klapper 2018-07-30 10:35:22 UTC
As discussed in https://github.com/doxygen/doxygen/pull/734 , Doxygen has moved its issue tracking to 

   https://github.com/doxygen/doxygen/issues

All Doxygen tickets in GNOME Bugzilla have been migrated to Github. You can subscribe and participate in the new ticket in Github. You can find the corresponding Github ticket by searching for its Bugzilla ID (number) in Github.

Hence I am closing this GNOME Bugzilla ticket.
Please use the corresponding ticket in Github instead. Thanks a lot!