1 * Useful Makefile targets
3 The following 'make' targets exist for your convenience:
6 validate the well-formedness of all XML materials
8 make or make all (optional: VERSION=x.y.z PUBDATE=2007-07-01)
9 build all languages in all formats
12 build the English manual in HTML format
14 make fr/developers-reference.pdf
15 build the French manual in PDF format
17 make ja/developers-reference.txt
18 build the Japanese manual in text format
21 generate .pot files from .dbk sources
23 make updatepo LINGUA=xx (with xx=language code)
24 update .po files for language xx
29 To contain the maintainers of this package, email
30 <developers-reference@packages.debian.org>.
35 If you want to contribute to the Developer's Reference, it's best to
36 first submit a few patches as bug reports. Writing patches for
37 existing bugs are also always appreciated. You may wish to make
38 patches against the SVN sources, about which see below.
40 Do not commit patches to the developers reference yourself unless
41 authorized to do so. Patches need to be finalized and common opinion
42 before they are applied. This is even true if you happen to have
43 SVN access for other reasons.
48 If you're interested in ongoing maintenance, once you've shown that
49 you've mastered the style of the manual with a couple accepted
50 patches, you can be given SVN access. If you have already
51 access to the SVN server for other reasons, do not use it unless
54 Instructions on how to get the SVN version of this software, including
55 how to get SVN access, can be found at
56 <URL:http://svn.debian.org/>.
61 We have tried to keep language-independant bits of text in common.ent.
62 Feel free to truck stuff out of the English manual into common.ent if
63 it's useful, or else report the problem.
65 The translation .po files are in po4a/fr/ and po4a/ja/ for French and
66 Japanese. We hope very much for more translations.