1
--------------------------------------
2
Documentation Guidelines
3
---------------------------------------
4
Welcome to the Xiphos documentation guidelines.
5
This document will contain some guidelines for writing/submitting a good patch
6
to the Xiphos documentation project.
8
Any new features or large scale work should first be discussed on the
9
xiphos-developers mailing-list first. This will ensure the idea fits in the
10
direction we wish to take Xiphos, and also that the effort is not
16
1. Please read the Gnome Documentation Project guidelines. If you would like a copy of it
17
in PDF format, please email one of the Documentation developers.
19
2. Whilst editing, you can view your changes by simply going into your working directory and running :
20
" yelp filename.xml". You may have to give the full path, like this: "yelp `pwd`/xiphos.xml"
21
Also, using xmllint can save a lot of frustration: "xmllint xiphos.xml"
23
This also helps with finding errors and debugging.
24
3. Please make sure that you have properly edited xiphos-manual-(lang).omf and Makefile.am.
32
1. xiphos-manual.xml is the main file to the documentation. All chapter are linked from here. It acts
33
as a contents page. The interface section's within Xiphos are broken up into smaller more manageable
34
files which are listed within this file. If a new section is to be added to the manual eg. "Advanced Search dialogs",
35
this needs to be mentioned in here.
37
2. Files are broken up into groups of interface categories. If you wish to edit the preferences dialog documentation, just
38
simply edit the "preferences.xml" file.
43
1. screenshots will only be accepted if it is in the "Simple" theme. It can be
46
Applications -> Desktop Preferences -> Theme
48
by simply running the command "gnome-theme-manager" in the terminal.
50
2.Please use discretion about image sizes. This includes file size and images size ( length
51
and height). While there is no rule or standard to how big the image must be, visibility of the
52
screenshot and visibility within "Yelp" is the main priority. We don't want to user to scroll horizontally
53
just to view a screenshot. I normally keep my screenshot width at a maximum of 600 pixels.
55
3.file naming will be done with the prefix of the interface ( eg. preferences, underscore, interface subsection ( eg. font-color )
56
eg. " preferences_fontscolor.png"
57
NOTE: please use lower-case.
62
The DocBook copies are the master copy. Any alterations on the Windows
63
helpfiles should only be done if the addition is absolutely and definitely
64
Windows specific about a Windows subject only. If it is advise about the way
65
a common problem is solved in Windows (and a similar piece of advice should
66
be given to Unix/Linux users, please add your addition to Docbook.
68
The Windows htmlhelp files should regularly get updated after serious commits.
69
To create a Windows Help file you require two steps:
71
1) process the docbook files with an XSL1.0 processor - e.g. Saxon 6.5.5
72
(not the newer Saxon9 versions) and the htmlhelp stylesheet (available in
75
java -jar saxon.jar xiphos.xml htmlhelp.xsl
77
2) create the CHM file out of the intermediate source by using htmlhelp.exe
78
on a Windows system (obtainable from Microsoft).