1
0
mirror of https://github.com/Llewellynvdm/conky.git synced 2024-11-16 01:57:09 +00:00
conky/doc
Pavel Labath 87415d6e36 xftfont is renamed to font
whether the font setting specifies an X or an Xft font depends on the use_xft setting.
2010-11-17 14:49:03 +01:00
..
CMakeLists.txt Add missing copyright notices. 2010-01-01 15:49:41 -08:00
command_options.xml Add support for --stdin-config 2010-04-13 17:02:39 +02:00
config_settings.xml xftfont is renamed to font 2010-11-17 14:49:03 +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 Update copyright notices. 2010-01-01 15:46:17 -08:00
lua.xml Add creation functions for certain cairo structures. 2009-11-25 12:53:42 -08:00
lua.xsl Refactor some of the new weather code, fix docs. 2009-07-12 23:31:57 -06:00
README.docs Reformatted all code 2008-02-20 20:30:45 +00:00
variables.xml Merge remote branch 'origin/master' into lua-config 2010-11-13 20:05:59 +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