# HG changeset patch # User torinthiel # Date 1166344885 0 # Node ID e9736e48523f8f4b84e63902272ca8a8fc25327e # Parent efdab905710b9a4f89b6fa13c9f1e99364b55c96 - there's no for ages, it's automated - another CVS -> SVN diff -r efdab905710b -r e9736e48523f DOCS/xml/README.maintainers --- a/DOCS/xml/README.maintainers Sun Dec 17 08:29:42 2006 +0000 +++ b/DOCS/xml/README.maintainers Sun Dec 17 08:41:25 2006 +0000 @@ -28,10 +28,7 @@ 2) Make sure to create a 'Makefile' for the translation -- you can use 'en/Makefile' as an example. -3) Set to your language code if the DocBook XSL - stylesheets support it. - -4) If you want to use a customized XSL stylesheet, create one and name it +3) If you want to use a customized XSL stylesheet, create one and name it 'html-common.xsl'. Also create two additional XSL stylesheets ('html-single.xsl' and 'html-chunk.xsl'), with content such as this: @@ -62,7 +59,7 @@ Including it can (and will) break building of documentation if chunk.xsl is installed at a nonstandard location. -5) If you wish to change the output encoding of generated files, create +4) If you wish to change the output encoding of generated files, create html-common.xsl as suggested in step 4) and add strings such as these somewhere between the and tags (please, pay attention to quotes): @@ -70,17 +67,15 @@ - Use ru/html-common.xsl as example. - -6) If you are using your own HTML stylesheet, edit your Makefile and set +5) If you are using your own HTML stylesheet, edit your Makefile and set the HTML_STYLESHEET variable to its name. Please, don't call your HTML stylesheet 'default.css'. -7) In each translated file after the tag you must put a note - like , where 1.2 is the revision of corresponding +6) In each translated file after the tag you must put a note + like , where 2 is the revision of corresponding English file (see comment at the top of file). -8) While your translation isn't finished, you can change USE_SYMLINKS +7) While your translation isn't finished, you can change USE_SYMLINKS to "yes" in your Makefile. This will help you testing your translation: English files will be used instead of untranslated ones, when generating HTML docs.