/[ddp]/manuals/trunk/release-notes/README
ViewVC logotype

Diff of /manuals/trunk/release-notes/README

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

manuals/branches/release-notes/lenny/README revision 5521 by debacle, Thu Nov 13 23:39:54 2008 UTC manuals/trunk/release-notes/README revision 7754 by jfs, Thu Nov 11 01:14:39 2010 UTC
# Line 1  Line 1 
1  Release Notes  Release Notes
2    -------------
3    
4  The Release Notes contain important information for new users and for  The Release Notes contain important information for new users and for
5  an update from the previous version of Debian. It is written in  an update from the previous version of Debian. It is written in
6  DocBook XML which allows the creation of various output files in the  DocBook XML which allows the creation of various output files in the
7  formats HTML, text, PDF, ...  formats HTML, text, PDF, ...
8    
9    You can find more information about the Release Notes at
10    http://wiki.debian.org/ReleaseNotes
11    and
12    http://www.debian.org/doc/user-manuals#relnotes
13    
14    
15    Building the RN
16    ---------------
17    
18  To build it you need these packages:  To build it you need these packages:
19   - docbook-xsl         (transformation stylesheets)   - docbook-xsl         (transformation stylesheets)
20   - libxml2-utils       (for xmllint)   - libxml2-utils       (for xmllint)
21   - dblatex and xmlroff (depending on the output format and language)   - dblatex and xmlroff (depending on the output format and language)
22   - po4a                (for handling PO file based translations)   - po4a                (for handling PO file based translations)
23   - make   - make                (or you will type a lot)
24     - ttf-arphic-*        (fonts)
25     - texlive-*           (used by dblatex)
26     - w3m                 (to create the text version)
27    
28    For etch, you need the lenny backports of dblatex and xmlroff.
29    
30  Just call "make" to build it. To build the release notes in a single  Just call "make" to build it. To build the release notes in a single
31  format (html or txt or pdf) for a single language (e.g. zh_CN, en, es)  format (html or txt or pdf) for a single language (e.g. zh_CN, en, es)
32  and a single architecture (such as amd64, i386, powerpc), call e.g.:  and the "all" pseudo-architecture, call e.g.:
33  "make html LINGUA=es architecture=i386".  "make html LINGUA=es architecture=all".
34    
35    Autobuilding of the RN
36    ----------------------
37    
38    The Release Notes are automatically built at www-master.debian.org
39    in order to publish them at http://www.debian.org/ and all the mirrors
40    around the world.
41    
42    An automatic task updates the www-master SVN copy to the latest revision
43    and builds the Release Notes for different releases.
44    
45    Build logs are available at
46       http://www-master.debian.org/build-logs/webwml/release-notes.log
47    
48  Translations  Translations
49    ------------
50    
51  The document is available in many languages. po4a is currently used as  The document is available in many languages. po4a is currently used as
52  the translation tool.  the translation tool.
53    
54    To add a new language "new", do as follows:
55    
56    $ svn checkout svn+ssh://svn.debian.org/svn/ddp/manuals/trunk/release-notes
57    $ cd release-notes
58    $ mkdir new
59    $ make updatepo LINGUA=new
60    (now translate all po files in new/)
61    (if your new language is supported by dblatex, add a file
62    hyphenation.tex to the language directory, e.g.
63    $ cp en/hyphenation.tex; svn add new/hyphenation.tex
64    edit the file to your new languages needs.
65    See the LaTeX \hyphenation{} command for further information.)
66    $ make tidypo LINGUA=new (always before commit!)
67    $ make validate LINGUA=new (always before commit!)
68    (fix any XML validity problems)
69    $ make html txt pdf LINGUA=new architecture=all
70    (proof-read and correct)
71    $ svn commit
72    
73  Some translators prefer full-text translation without po. For this  Some translators prefer full-text translation without po. For this
74  style of translations, the original English files are just copied  style of translations, the original English files are just copied
75  into the language directory and the translators have to make sure,  into the language directory and the translators have to make sure,
76  that the translation is up to date.  that the translation is up to date.
77    
 To add a new translation, call "make updatepo LINGUA=xx" to create a  
 new PO template file which you need to translate, with xx being the  
 language code of your translation.  
   
 It is suggested that you now try to create the document for at least  
 one architecture. This will detect possible syntax errors in your  
 file. Furthermore you may call "make validate LINGUA=xx".  
   
78  Send your translation for inclusion to the public mailing list  Send your translation for inclusion to the public mailing list
79  debian-doc@lists.debian.org.  debian-doc@lists.debian.org.

Legend:
Removed from v.5521  
changed lines
  Added in v.7754

  ViewVC Help
Powered by ViewVC 1.1.5