Gecko [ fernandoquevedodop.com ]

Name	Size	Permission
AUTHORS.gz	2.28 KB	-rw-r--r--
BUGS.gz	2.19 KB	-rw-r--r--
DEVEL-CVS	1.44 KB	-rw-r--r--
FAQ.gz	106.42 KB	-rw-r--r--
HACKING.DOCS	2.26 KB	-rw-r--r--
HACKING.gz	7.37 KB	-rw-r--r--
MINOR-BUGS	3.21 KB	-rw-r--r--
NEWS.Debian.gz	1.81 KB	-rw-r--r--
NEWS.gz	30.9 KB	-rw-r--r--
PROJECTS	2.33 KB	-rw-r--r--
RCSFILES.gz	4.67 KB	-rw-r--r--
README.gz	2.26 KB	-rw-r--r--
TODO.gz	16.5 KB	-rw-r--r--
changelog.Debian.gz	2.64 KB	-rw-r--r--
copyright	5.6 KB	-rw-r--r--
cvs-paper.ms.gz	12.73 KB	-rw-r--r--
cvs-paper.pdf	72.84 KB	-rw-r--r--
cvs.html	947.6 KB	-rw-r--r--
cvs.pdf	1.28 MB	-rw-r--r--
cvs.txt.gz	148.48 KB	-rw-r--r--
cvsclient.html	117.3 KB	-rw-r--r--
cvsclient.pdf	256.45 KB	-rw-r--r--
cvsclient.txt.gz	28.35 KB	-rw-r--r--
intro.txt	3.91 KB	-rw-r--r--
writeproxy.rtf.gz	18.96 KB	-rw-r--r--

Code Editor : HACKING.DOCS

Here's some of the texinfo conventions the CVS documentation uses:

@code{ ... }			command usage & command snippets, including
				command names.
@var{ ... }			variables - text which the user is expected to
				replace with some meaningful text of their own
				in actual usage.
@file{ ... }			file names
@samp{ ... }			for most anything else you need quotes around
				(often still misused for command snippets)
@example ... @end example	example command usage and output, etc.
@emph{ ... }			emphasis - warnings, stress, etc.  This will be
				bracketed by underline characters in info files
				(_ ... _) and in italics in PDF & probably in
				postscript & HTML.
@strong{ ... }			Similar to @emph{}, but the effect is to
				bracket with asterisks in info files (* ... *)
				and in bold in PDF & probably in postscript &
				HTML. It will cause spurious links in info if
				used in some circumstances; if in doubt, use
				@empy{ ... } instead then.
@noindent			Suppresses indentation of the following
				paragraph.  This can ocassionally be useful
				after examples and the like.
@cindex ...			Add a tag to the index.
@pxref{ ... }			Cross reference in parentheses.
@xref{ ... }			Cross reference.

Preformatted text should be marked as such (use @example... there may be other
ways) since many of the final output formats can use relational fonts otherwise
and marking it as formatted should restrict it to a fixed width font.  Keep
this sort of text to 80 characters or less per line since larger may not be
properly viewable for some info users.

There are dictionary lists and function definition markers.  Scan cvs.texinfo
for their usage.  There may be table definitions as well but I haven't used
them.

Use lots of index markers.  Scan the index for the current style.  Try to reuse
an existing entry if the meaning is similar.

`makeinfo' 3.11 or greater is required for output generation since earlier
versions do not support the @ifnottex & @ifnothtml commands.  There may be
other commands used in `cvs.texinfo' that are unsupported by earlier versions
of `makeinfo' by the time you read this.

For more on using texinfo docs, see the `info texinfo' documentation or
http://www.gnu.org/manual/texinfo/texinfo.html .

$MirOS: src/gnu/usr.bin/cvs/doc/HACKING.DOCS,v 1.3 2010/09/19 19:42:52 tg Exp $

${this.title}

Code Editor : HACKING.DOCS