| 1 |
Release Notes
|
| 2 |
|
| 3 |
The Release Notes contain important information for new users and for an update
|
| 4 |
from the previous version of Debian. It is written in SGML which allows the
|
| 5 |
creation of various output files in the formats HTML, text, PostScript, PDF, ...
|
| 6 |
|
| 7 |
To build it you need the package debiandoc-sgml and (dependent on the output
|
| 8 |
format and language) suggested and recommended packages of it. For PO file based
|
| 9 |
translations you also need po4a. and of course make, ...
|
| 10 |
|
| 11 |
Just call "make" to build it. It works also from a language directory but you
|
| 12 |
need to add the architecture for which you want to create the document on the
|
| 13 |
commandline, e.g.: "make architecture=i386".
|
| 14 |
|
| 15 |
Translations
|
| 16 |
|
| 17 |
The document is available in many languages. There are two ways for
|
| 18 |
translations: SGML based or PO based. Each format has it own advantages
|
| 19 |
and disadvantages. If in doubt select the PO file based method for a
|
| 20 |
new translation.
|
| 21 |
|
| 22 |
Both methods require that you create a subdirectory for your language.
|
| 23 |
Copy en/Makefile into it.
|
| 24 |
|
| 25 |
To add a new PO file based translation, change into the new directory and call
|
| 26 |
"make update-po" to create a new PO template file which you need to translate.
|
| 27 |
|
| 28 |
ATTENTION: Once you have a PO file (even an empty one), the make system assumes
|
| 29 |
that the translation is PO file based and may overwrite an existing SGML file!
|
| 30 |
|
| 31 |
An SGML file based translation requires you to copy en/release-notes.en.sgml
|
| 32 |
into your directory. Rename it according to your language (release-notes.XX.sgml)
|
| 33 |
and translate the content of this file. Do not touch all SGML command which
|
| 34 |
are embedded in "<" and ">", e.g. <var> and translate only the English text.
|
| 35 |
It is important to save the revision of the English template file in your file
|
| 36 |
to simplify later updates. If the English file contains in the header
|
| 37 |
<!entity docid "$Id: Readme,v 1.2 2006-10-29 15:59:07 robster Exp $">
|
| 38 |
you should add something like this:
|
| 39 |
<!-- Translation based on English version 1.69.2.7 -->
|
| 40 |
|
| 41 |
It is suggested that you now try to create the document for at least one
|
| 42 |
architecture. This will detect possible syntax errors in your file.
|
| 43 |
|
| 44 |
Send your translation for inclusion to the public mailing list
|
| 45 |
debian-doc@lists.debian.org. To avoid too many large mails on the list or
|
| 46 |
public postings you can also send your translation in a private mail to Frans
|
| 47 |
Pop <elendil@planet.nl> or Jens Seidel <jensseidel@users.sf.net>. If both do
|
| 48 |
not respond please send it to the mailing list.
|
| 49 |
|
Parent Directory
| 
Revision Log