comparison DOCS/xml/README.maintainers @ 11199:b61680a0b29a

Add some whitespace for readability + some wording improvements.
author diego
date Tue, 21 Oct 2003 01:32:34 +0000
parents 6dfed0b2a300
children 1470e4dd1a4a
comparison
equal deleted inserted replaced
11198:1d753b45e42e 11199:b61680a0b29a
21 21
22 Adding new translations 22 Adding new translations
23 ~~~~~~~~~~~~~~~~~~~~~~~ 23 ~~~~~~~~~~~~~~~~~~~~~~~
24 24
25 1) Create a new subdirectory and copy the XML files there. 25 1) Create a new subdirectory and copy the XML files there.
26
26 2) Make sure to create a 'Makefile' for the translation -- you can 27 2) Make sure to create a 'Makefile' for the translation -- you can
27 use 'en/Makefile' as an example. 28 use 'en/Makefile' as an example.
29
28 3) Set <book lang="XX"> to your language code if the DocBook XSL 30 3) Set <book lang="XX"> to your language code if the DocBook XSL
29 stylesheets support it. 31 stylesheets support it.
32
30 4) If you want to use a customized XSL stylesheet, create one and name it 33 4) If you want to use a customized XSL stylesheet, create one and name it
31 'html-common.xsl'. Also create two additional XSL stylesheets ('html.xsl' 34 'html-common.xsl'. Also create two additional XSL stylesheets ('html.xsl'
32 and 'html-chunk.xsl', with such content: 35 and 'html-chunk.xsl', with content such as this:
33 36
34 html.xsl: 37 html.xsl:
35 38
36 <?xml version="1.0" encoding="ISO-8859-1"?> 39 <?xml version="1.0" encoding="ISO-8859-1"?>
37 <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" 40 <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
55 58
56 59
57 Note: You mustn't xsl:include or xsl:import chunk.xsl directly! 60 Note: You mustn't xsl:include or xsl:import chunk.xsl directly!
58 Including it can (and will) break building of documentation if chunk.xsl 61 Including it can (and will) break building of documentation if chunk.xsl
59 is installed at a nonstandard location. 62 is installed at a nonstandard location.
60 5) If you wish to change output encoding of generated files, create 63
61 html-common.xsl as suggested in step 4) and add such strings somewhere 64 5) If you wish to change the output encoding of generated files, create
62 between <xsl:stylesheet ...> and </xsl:stylesheet> tags 65 html-common.xsl as suggested in step 4) and add strings such as these
66 somewhere between the <xsl:stylesheet ...> and </xsl:stylesheet> tags
63 (please, pay attention to quotes): 67 (please, pay attention to quotes):
64 68
65 <xsl:param name="chunker.output.encoding" select="'your_encoding'"/> 69 <xsl:param name="chunker.output.encoding" select="'your_encoding'"/>
66 <xsl:output encoding="your_encoding"/> 70 <xsl:output encoding="your_encoding"/>
67 71
68 Use ru/html-common.xsl as example. 72 Use ru/html-common.xsl as example.
73
69 6) If you are using your own HTML stylesheet, edit your Makefile and set 74 6) If you are using your own HTML stylesheet, edit your Makefile and set
70 the HTML_STYLESHEET variable to its name. Please, don't give name 75 the HTML_STYLESHEET variable to its name. Please, don't call your HTML
71 'default.css' to your HTML stylesheet. 76 stylesheet 'default.css'.
77
72 7) In each translated file after the <?xml ... ?> tag you must put a note 78 7) In each translated file after the <?xml ... ?> tag you must put a note
73 like <!-- synced with 1.2 -->, where 1.2 is the revision of corresponding 79 like <!-- synced with 1.2 -->, where 1.2 is the revision of corresponding
74 English file (see comment at the top of file). 80 English file (see comment at the top of file).
81
75 8) While your translation isn't finished, you can change USE_SYMLINKS 82 8) While your translation isn't finished, you can change USE_SYMLINKS
76 to "yes" in your Makefile. This will help you testing your translation: 83 to "yes" in your Makefile. This will help you testing your translation:
77 english files will be used instead of untranslated ones, when generating 84 english files will be used instead of untranslated ones, when generating
78 HTML docs. 85 HTML docs.
79 86