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 698021 - GtkSourceView: bad links to GTK+ symbols (should be version 3 instead of version 2)
GtkSourceView: bad links to GTK+ symbols (should be version 3 instead of vers...
Status: RESOLVED DUPLICATE of bug 644111
Product: gtk-doc
Classification: Platform
Component: general
1.21
Other Linux
: Normal normal
: ---
Assigned To: gtk-doc maintainers
gtk-doc maintainers
Depends on:
Blocks:
 
 
Reported: 2013-04-14 20:54 UTC by Sébastien Wilmet
Modified: 2014-03-08 20:23 UTC
See Also:
GNOME target: ---
GNOME version: ---



Comment 1 Sébastien Wilmet 2013-04-17 11:33:01 UTC
I don't know how the documentation available on the web site is generated, but in the Makefile.am, the FIXXREF_OPTIONS mention gtk3:

https://git.gnome.org/browse/gtksourceview/tree/docs/reference/Makefile.am#n70

And the links work correctly in devhelp.
Comment 2 Frederic Peters 2014-01-27 00:12:37 UTC
I just checked the 3.10.1 and 3.11.2 tarballs and the generated HTML files have pointers to developer.gnome.org/gtk2/, I'm reassigning the bug to gtksourceview, but maybe it should go to gtk-doc.
Comment 3 Sébastien Wilmet 2014-01-27 15:09:50 UTC
I think everything is fine in GtkSourceView, it's maybe a bug with the FIXXREF_OPTIONS.
Comment 4 Sébastien Wilmet 2014-03-08 20:04:28 UTC
In developer.gnome.org:

> <a href="http://developer.gnome.org/gtk2/GtkTextBuffer.html">GtkTextBuffer</a>

HTML file generated locally, not installed (in docs/reference/html/):

> <a href="../gtk3/GtkTextBuffer.html">GtkTextBuffer</a>

HTML file generated locally, and installed in /opt/gnome/:

> <a href="/opt/gnome/share/gtk-doc/html/gtk3/GtkTextBuffer.html">GtkTextBuffer</a>

So it seems that when installing the files, the links are modified (from relative paths to absolute paths). If gtk2 is present, it has maybe the priority. So it's maybe a gtk-doc bug.
Comment 5 Sébastien Wilmet 2014-03-08 20:23:38 UTC
It has been fixed recently, developer.gnome.org is just not up-to-date.

*** This bug has been marked as a duplicate of bug 644111 ***