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 611656 - Update documentation for gtkvruler
Update documentation for gtkvruler
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Documentation
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks: 599599
 
 
Reported: 2010-03-03 00:19 UTC by Steven Harms
Modified: 2010-04-18 02:04 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Update documentation for gtkvruler (3.93 KB, patch)
2010-03-03 00:19 UTC, Steven Harms 		none Details | Review
Update documentation for gtkvruler (4.00 KB, patch)
2010-03-04 00:13 UTC, Steven Harms 		committed Details | Review

Description Steven Harms 2010-03-03 00:19:35 UTC 
Created attachment 155090 [details] [review]
Update documentation for gtkvruler

Update documentation per http://live.gnome.org/GTK+/TaskAPIDocMigration
Comment 1 Javier Jardón (IRC: jjardon) 2010-03-03 02:40:40 UTC 
Review of attachment 155090 [details] [review]:

Thank you for you patch.

You can check that the documentation is correctly generated with:
./autogen --enable-gtk-doc
make
then go with a browser to docs/reference/gtk/html

::: gtk/gtkvruler.c
@@ +45,3 @@
+ * @Short_description: A vertical ruler
+ * SECTION:gtkvruler
+/**

Remove the blank line before </note>, otherwise the generation of the documentation will fail
Comment 2 Steven Harms 2010-03-04 00:13:36 UTC 
Created attachment 155182 [details] [review]
Update documentation for gtkvruler

Remove trailing whitespaces, extra line before note, typo for unit of measurement
Comment 3 Javier Jardón (IRC: jjardon) 2010-04-18 02:04:43 UTC 
Comment on attachment 155182 [details] [review]
Update documentation for gtkvruler

commit 6cdeb370a11b81ded06203bd5af12e8207830f46
Comment 4 Javier Jardón (IRC: jjardon) 2010-04-18 02:04:53 UTC 
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.