2.31.16.1:

2012-02-13  José Alburquerque  <jaalburquerque@gmail.com>

	gmmproc: docs: Convert signal and property names correctly.

	* tools/pm/DocsParser.pm (substitute_identifiers): Search for gtk-doc
	property and signal references and convert them to appropriate C++
	names so that they are referenced correctly in the documentation.

	Bug #668918.

2012-02-08  José Alburquerque  <jaalburquerque@gmail.com>

	gmmproc: DocsParser.pm (convert_tags_to_doxygen): Correct typo.

	* tools/pm/DocsParser.pm (convert_tags_to_doxygen): Make the newline
	following the <itemizedlist> tags optional when converting them to
	Doxygen format (in case the tags are not necessarily on a line by
	themselves).

2012-02-08  José Alburquerque  <jaalburquerque@gmail.com>

	gmmproc: Translate the <itemizedlist> tags in docs correctly.

	* tools/pm/DocsParser.pm (lookup_documentation): Typo.
	(convert_tags_to_doxygen): Add substitutions to convert gtk-doc
	<itemizedlist> tags to Doxygen format.  For example, see
	Gtk::ToolItem's "create-menu-proxy" and "toolbar-reconfigured"
	signal docs.

2012-02-07  José Alburquerque  <jaalburquerque@gmail.com>

	docextract_to_xml.py: Add some HTML entity conversions.

	* tools/defs_gen/docextract_to_xml.py: Add some HTML entity
	conversions that produce errors when processed by gmmproc.

2012-02-07  José Alburquerque  <jaalburquerque@gmail.com>

	gmmproc: Method generation: Fix indentation of void methods.

	* tools/m4/method.m4: Make sure that the generated line in methods
	returning void is indented properly (by two spaces).  Before, there
	was no indentation (see for example the Entry::set_inner_border()
	method).

2012-02-03  José Alburquerque  <jaalburquerque@gmail.com>

	gmmproc: Add documentation to wrapped signals.

	* tools/m4/signal.m4: Add docs to the on_*() default handlers
	referring the users to the signal_*() docs.
	* tools/pm/DocsParser.pm (parse_on_start):
	(parse_on_end): Allow the <signal></signal> tags from the generated
	XML docs to be processed in a similar way as the <function></function>
	tags are processed.  The docs of the signals are stored as
	"Class::a_signal_name" in the hash.
	(append_parameter_docs): Skip the first parameter for signals also
	because the first parameter of signals is the object for which the
	signal is triggered.
	(lookup_documentation): Generalize the no docs warning to include
	signals also.
	* tools/pm/Function.pm (get_refdoc_comment): Modify the subroutine to
	accept the docs of the signal (that the DocsParser stores) and include
	the prototype of the slot in the docs.
	* tools/pm/Output.pm (output_wrap_sig_decl): Modify the subroutine to
	look up the documentation of the signal which it then passes to
	get_refdoc_comment() so that the documentation of the signal from the
	generated XML is included in the declaration of the signal.

	Bug #668918 (Mark)