Files
postgresql/doc/src/sgml
Michael Meskes a2769a4e21 Fixed incorrect description of EXEC SQL VAR command.
Thanks to MauMau <maumau307@gmail.com> for finding and fixing this.
2013-06-27 17:07:03 +02:00
..
2013-01-24 08:01:16 +00:00
2013-02-22 16:56:55 -03:00
2013-02-21 05:27:16 -05:00
2013-03-10 14:16:02 -04:00
2013-04-20 16:29:58 -04:00
2013-05-09 22:26:04 -04:00
2013-06-21 22:48:06 -04:00
2013-04-10 23:06:19 -04:00
2012-12-08 07:37:11 -05:00
2012-12-06 17:47:30 -03:00
2012-04-23 22:43:09 -04:00
2012-04-23 22:43:09 -04:00
2012-04-23 22:43:09 -04:00
2012-04-23 22:43:09 -04:00
2011-08-17 10:05:22 +03:00
2013-02-21 05:27:16 -05:00
2013-02-25 17:58:14 -05:00

<!-- doc/src/sgml/README.links -->

Linking within SGML documents can be confusing, so here is a summary:


Intra-document Linking
----------------------

<xref>
	use to get chapter/section # from the title of the target
	link, or xreflabel if defined at the target; has no close tag
	http://www.oasis-open.org/docbook/documentation/reference/html/xref.html

<link>
	use to supply text for the link, requires </link>
	http://www.oasis-open.org/docbook/documentation/reference/html/link.html

linkend=
	controls the target of the link/xref, required

endterm=
	for <xref>, allows the text of the link/xref to be taken from a
	different link target title


External Linking
----------------

<ulink>
	like <link>, but uses a URL (not a document target);  requires
	</ulink>; if no text is specified, the URL appears as the link
	text
	http://www.oasis-open.org/docbook/documentation/reference/html/ulink.html

url=
	used by <ulink> to specify the URL, required


Guidelines
----------

o  If you want to supply text, use <link>, else <xref>
o  Do not use text with <ulink> so the URL appears in printed output
o  Specific nouns like GUC variables, SQL commands, and contrib modules
   usually have xreflabels