1
0
mirror of https://github.com/Llewellynvdm/conky.git synced 2024-12-26 04:17:33 +00:00
conky/doc
Pavel Labath e97b67aa20 IPv6 support for $tcp_portmon
In theory, this may fail to compile on ancient systems that don't have IPv6 types (struct
sockaddr_in6 et al.) available. If it turns out that such systems are still in use, the best way
to solve it would be to provide dummy declarations via configure tests.
2009-11-16 18:17:16 +01:00
..
command_options.xml Add the -p/--pause command line option. 2009-10-03 14:26:39 -07:00
config_settings.xml Support for $pid_state 2009-11-14 13:58:07 +01:00
config_settings.xsl Fix title in config_settings.html. 2009-09-16 08:54:12 -07:00
conky-howto.xml IPv6 support for $tcp_portmon 2009-11-16 18:17:16 +01:00
docgen.sh Removing old svn keywords. 2008-12-09 16:35:49 -07:00
docs.xml Doc cleanup. 2009-08-01 13:15:53 -06:00
lua.xml Remove deprecated stuff from docs and conky.c (for 1.7.3). 2009-07-28 12:43:45 -06:00
lua.xsl Refactor some of the new weather code, fix docs. 2009-07-12 23:31:57 -06:00
Makefile.am use CLEANFILES instead of defining a custom clean target 2009-09-05 03:34:33 +02:00
README.docs Reformatted all code 2008-02-20 20:30:45 +00:00
variables.xml IPv6 support for $tcp_portmon 2009-11-16 18:17:16 +01:00
variables.xsl Refactor some of the new weather code, fix docs. 2009-07-12 23:31:57 -06:00

DA DOCS. YO.
============
The main file that contains the bulk of our documentation is docs.xml .
We use the DocBook format, which is a really kickass xml-based way of
writing documentation, heavily oriented towards programming and computer
stuff. There are tags like <command> and <option> that marks up your
content without actually having to mark it up, which is why something
that's of the <command> shows up in some cool style regardless of
whether it's in a man page or a web page. DocBook has been around for
10 years, and there's TONS of resources online about the different
tags and the stuff that can be done.

FILE ORGANIZATION
=================
For the sake of making things readable and organized,
docs.xml "includes" three other files, as of 8/18/05.
These are config_settings.xml, command_options.xml, and variables.xml .
Their names are pretty self-explanatory, and what the "include" essentially
does is stick their contents into docs.xml at the appropriate locations
when it's time to produce a man page or html file. So if you wanted to
add a variable or explain a command line option better, you'd look in
variables.xml and command_options.xml. If you wanted to change the authors
or something, look in docs.xml

BUILDING DA DOCS
================
(NOTE that the docs are now built automatically via doc/Makefile.am, but it requires that you have docbook2x and xsltproc installed)

making the html is easy. xsltproc should more than likely already be on your system:

xsltproc http://docbook.sourceforge.net/release/xsl/current/html/docbook.xsl docs.xml > docs.html
==============================================================================================================
making the man page is pretty easy, it uses a program called docbook2x, which you might or might not have.

docbook2x-man docs.xml (produces a conky.1 file)
gzip conky.1

conky.1.gz can be viewed in man-form by doing "man -l conky.1.gz"
==============================================================================================================
making the README (text-only) file is just some simple unix:
man -l conky.1.gz | col -b > README