X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=README-contrib;h=2afeddf3eeb8d576a8bc050ec55a0ef2aab8bf96;hb=9e30648be2ebd1809a0687306df9cd103637dbc1;hp=8ecb71b5564b08ee4391597cfa812e6d58e79418;hpb=0bcf4a3ca3543c64c1dab98a214f85ec9e50e90a;p=developers-reference.git

diff --git a/README-contrib b/README-contrib
index 8ecb71b..2afeddf 100644
--- a/README-contrib
+++ b/README-contrib
@@ -3,16 +3,25 @@
 The following 'make' targets exist for your convenience:
 
   make validate
-        validate the well-formedness of all SGML materials
+        validate the well-formedness of all XML materials
 
-  make all
+  make or make all (optional: VERSION=x.y.z PUBDATE=2007-07-01)
         build all languages in all formats
 
-  make developers-reference.sgml.validate
-        validate the well-formedness of the English manual
+  make index.html
+        build the English manual in HTML format
 
-  make developers-reference.html
-        build the English manual
+  make fr/developers-reference.pdf
+        build the French manual in PDF format
+
+  make ja/developers-reference.txt
+        build the Japanese manual in text format
+
+  make pot
+        generate .pot files from .dbk sources
+
+  make updatepo LINGUA=xx (with xx=language code)
+        update .po files for language xx
 
 
 * Contacting
@@ -26,18 +35,25 @@ To contain the maintainers of this package, email
 If you want to contribute to the Developer's Reference, it's best to
 first submit a few patches as bug reports.  Writing patches for
 existing bugs are also always appreciated.  You may wish to make
-patches against the CVS sources, about which see below.
+patches against the SVN sources, about which see below.
 
+Do not commit patches to the developers reference yourself unless
+authorized to do so. Patches need to be finalized and common opinion
+before they are applied. This is even true if you happen to have
+SVN access for other reasons.
 
-* CVS
+
+* SVN
 
 If you're interested in ongoing maintenance, once you've shown that
 you've mastered the style of the manual with a couple accepted
-patches, you can be given CVS pserver access. 
+patches, you can be given SVN access. If you have already
+access to the SVN server for other reasons, do not use it unless
+authorized to do so.
 
-Instructions on how to get the CVS version of this software, including
-how to get CVS access, can be found at
-<URL:http://www.debian.org/doc/cvs>.
+Instructions on how to get the SVN version of this software, including
+how to get SVN access, can be found at
+<URL:http://svn.debian.org/>.
 
 
 * Translators
@@ -46,19 +62,5 @@ We have tried to keep language-independant bits of text in common.ent.
 Feel free to truck stuff out of the English manual into common.ent if
 it's useful, or else report the problem.
 
-You should exploit CVS to see the diffs between when the document was
-last translated and the latest version.  Be sure to set the cvs-en-rev
-entity as appropriate when you do update a translation.
-
-We have provided commands to help with this.  To see the difference in
-numbers between the latest translated version and the latest version,
-do, for instance:
-
-  ./translation-status fr
-
-To get the diff between the latest translated version and the latest
-version:
-
-  ./translation-status -d fr
-
-
+The translation .po files are in po4a/fr/ and po4a/ja/ for French and
+Japanese. We hope very much for more translations.