1
0
mirror of https://github.com/Llewellynvdm/conky.git synced 2024-12-26 04:17:33 +00:00
conky/doc
2018-05-19 10:27:10 -04:00
..
CMakeLists.txt Add formatting/static analysis (#486) 2018-05-12 12:03:00 -04:00
command_options.xml Update command options documentation (#247) 2016-05-06 07:25:06 -04:00
config_settings.xml Added detect_battery setting (multiple batteries) to fix #190 (#482) 2018-05-03 08:34:48 -04:00
config_settings.xsl Read configuration from ~/.config/conky/conky.conf 2014-11-17 22:06:27 +01:00
conky-howto.xml Read configuration from ~/.config/conky/conky.conf 2014-11-17 22:06:27 +01:00
docgen.sh Make sure we get report if one of the commands in the documentation pipeline fails 2012-10-03 22:51:28 +02:00
docs.xml Add formatting/static analysis (#486) 2018-05-12 12:03:00 -04: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 Add cat and catp variables. (#507) 2018-05-19 10:27:10 -04: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