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 699406 - Partial link on https://developer.gnome.org/libgda/stable/null_handling.html
Partial link on https://developer.gnome.org/libgda/stable/null_handling.html
Status: RESOLVED FIXED
Product: libgda
Classification: Other
Component: Documentation
5.2.x
Other Linux
: Normal normal
: ---
Assigned To: malerba
malerba
: 701498 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2013-05-01 18:49 UTC by Lorenz
Modified: 2014-04-27 14:17 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
do not use : in section identifier (1.43 KB, patch)
2014-01-26 16:55 UTC, Frederic Peters 		none Details | Review

Description Lorenz 2013-05-01 18:49:50 UTC 
The next page arrow on the page: 
      https://developer.gnome.org/libgda/stable/null_handling.html

contains the partial link:
      gen:sql_identifiers.html

clicking on the arrow icon causes FireFox 20.0 on Ubuntu 12.04 to give the following error:

      The address wasn't understood
      
      Firefox doesn't know how to open this address, because the protocol 
      (gen) isn't associated with any program.
        
      You might need to install other software to open this address.

Pasting in the full link as below advances correctly to the next page.

      https://developer.gnome.org/libgda/stable/gen:sql_identifiers.html
Comment 1 Frederic Peters 2014-01-26 16:55:41 UTC 
Created attachment 267239 [details] [review]
do not use : in section identifier

This is actually a bug in gtk-doc but much easier to avoid in libgda than to fix properly in gtk-doc.
Comment 2 Murray Cumming 2014-04-27 14:16:17 UTC 
I've taken the liberty of applying this to both the master and LIBGDA_5.2 branches. Thanks.
Comment 3 Murray Cumming 2014-04-27 14:17:51 UTC 
*** Bug 701498 has been marked as a duplicate of this bug. ***