> On Sun, Dec 17, 2000 at 04:48:52PM +0100, Ivo Timmermans wrote:
> > I would like to start on translating the boot floppies to Dutch. I
> > asked around, and a few people are interested in helping.
> >
> > Is the potato boot floppy set a good place to start, or will the set
> > for woody be so much different that it will be outdated very quickly?
You should be working out of CVS. The same source tree which is now
for Potato will soon be branched, and the head will become woody.
Anyhow, you should subscribe to debian-boot, check out the CVS sources
(use the anonymous user if you like). For now, you can submit patches
to this list. If you like, later, I can set you up with a CVS
account.
See the below instructions on how to get the CVS source.
--
.....Adam Di [EMAIL PROTECTED]<URL:http://www.onShore.com/>
*** Information for boot-floppies translators ***
If you want to translate the installation messages to language <LANG>
(your two-letter language code), you'll have to provide the following
files (in order of importance):
1) dbootstrap's po file
How to create a new dbootstrap translation?
cd utilities/dbootstrap/po
make dbootstrap.pot
cp dbootstrap.pot <LANG>.po
Edit <LANG>.po to contain translations for all the strings
How to check your translation is OK?
Well, the first of all try to give it to somebody who speaks your language.
It's likely that that person will give you some advices what can be
improved. :)
The second thing is to check that the file will be correctly used.
Execute:
make check-C check-<LANG>
If there are no warnings/errors, and you should see something
like:
C.po: 624 translated messages, 1 fuzzy translations.
<lang>.po: 624 translated messages, 1 fuzzy translations.
If the set of numbers is the same (624, 1 in our case) and the
appropriate numbers are equal (like in our case: 624 is equal to 624,
and 1 is equal to 1), it's fine. If not, you should check what is
wrong with your translation.
Also Please make sure that the header (the translation for empty
string) has fuzzy flag. That means that all translations will have
one (1!) fuzzy translation.
If it is OK, add your <LANG> to the definition of __AVAILABLE_LANGUAGES
variable in utilities/dbootstrap/po/Makefile. Please append a
'+' character to the langage code there.
What do fuzzy tags mean?
Sometimes you can see that a message is marked as "fuzzy". This
is because of some intelligence built into msgmerge (the
program that creates and updates po files). They usually appear
in two cases during a msgmerge run (when you run make
update-<LANG>):
a) There was an already translated string. For example:
msgid "Insert a disk in the floppy drive"
msgstr "Blah blah blah"
and msgmerge noticed that a new, similar message was
added by the program developer, it will automatically
add a msgstr to it marking it as "fuzzy" It does that
because it "thinks" that if the msgids are similar, then
the msgstrs are probably also similar. For example:
#, fuzzy
msgid "Insert a diskette in the floppy drive"
msgstr "Blah blah blah"
b) The msgid has changed between program revisions.
Naturally, in both cases the translator should revise the
translation, fix it if necessary, and delete the "fuzzy" tag.
Makefile
Makefile performs all needed actions when called correctly:
make all
make do-trm -- creates all .trm files
make check-<lang> -- checks whether the file <lang>.po is
correct. actually, it just shows the
information about this very translation
make update-po -- updates all translations.
it tries to msgmerge new dbootstrap.pot
file with the current translation
make update-<lang> -- updates an translation.
2) Add your language to language chooser (utilities/dbootstrap/langs)
1. cp english.src <enlgish-name-for-your-language>.src
2. Modify the first line to reflect the character set you are going to
use while preparing this file:
<language name="English-name-your-language" charset="your-charset"
font="some-font-name" acm="some-acm-name">
at the moment, attributes font= and acm= are not used (but they will be!).
Please make sure that <language...> line is the first line, and the
charset you specified as the value for charset= attribute is supported
by iconv program (which, I believe, comes with libc6 package).
3. Modify the content accordingly. A good source of information about the
content can be file called bf-localization.sgml in
utilities/dbootstrap/langs directory. To create a text version of it,
execute:
make bf-localization.txt
5. Check that the file can be successfully converted into utf-8:
make <english-name-for-your-language>.xml
Should you see any error messages you do not understand, seek help at
[EMAIL PROTECTED]
4. In file Makefile add <english-name-for-your-language>.xml to
generated_languages variable.
5. Modify file file langs.xml:
a) you need add a declaration:
<!ENTITY english-name-for-your-language SYSTEM
"english-name-for-your-language.xml">
b) add a reference to your file (right before the line containing </languages>)
&english-name-for-your-language;
6. Try to execute
make langs.c
Should you see any error messages you do not understand, seek help at
[EMAIL PROTECTED]
3) other messages that are placed on the root disk:
cd scripts/rootdisk/messages
mkdir <LANG>
cd <LANG>
cp ../C/{release_notes,boot_message} .
Edit the release_notes and boot_message files appropriately.
4) files that are placed on the rescue disk
cd scripts/rescue/messages
mkdir <LANG>
cd <LANG>
cp ../C/debian.* ../C/f* ../C/install.sh.txt ../C/readme* .
Edit the files appropriately. You may find the program
syslinux2ansi (from package syslinux) useful.
5) README-Users.<LANG>.m4 (a translation of README-Users.m4)
6) The Debian Installation Guide
You need to provide the file documentation/install.<LANG>.sgml
This is usually the main file, which makes use of some sgml files
in documentation/<LANG>/ directory.
You may find the doc-check script (found in documentation
directory) useful. If called ./doc-check <LANG>, it checks which of
the documentation files need updating if the original has changed.
If given the '-d' flag, it also spits out the differences that were
made in the original since your last translation. Note that in
order to actually use it, you need to put some comments to the
translated files, like: <!-- original version: X.xx -->, where X.xx
is the revision of the original file.
See documentation/README-authors for some more detailed
information.
7) Release Notes
The file documentation/release_notes.<LANG>.sgml - a translation of
documentation/release_notes.sgml
8) The Installation Documentation Index
The file documentation/index.<LANG>.html.m4 - a translation of
documentation/index.en.html.m4
Note: whenever you update utilities/dbootstrap/po/<LANG>.po file
please execute `make check-<LANG>' command (you should be in
utilities/dbootstrap/po directory while executing this command)
before committing: this allows to make sure that the translation
is *syntactically* correct.
Charset to use:
In all texts use the local character encoding. The installation
routine will convert texts into IBMPC charset where it is needed.
Translators:
The following is a list of some people that have worked in the
translation of the installation messages to any language:
Bulgarian: George Tchavdarov <[EMAIL PROTECTED]>
Croatian: Matej Vela <[EMAIL PROTECTED]>
Czech: Pavel Makovec <[EMAIL PROTECTED]>
Jiri Masik <[EMAIL PROTECTED]>
Vilem Vychodil <[EMAIL PROTECTED]>
Miroslav Kure <[EMAIL PROTECTED]>
Esperanto: Edmund Grimley Evans <[EMAIL PROTECTED]>
Finnish: Tapio Lehtonen <[EMAIL PROTECTED]>
Antti-Juhani Kaijanaho <[EMAIL PROTECTED]>
French: Christophe Le Bars <[EMAIL PROTECTED]>
Vincent Renardias <[EMAIL PROTECTED]>
Eric Van Buggenhaut <[EMAIL PROTECTED]>
German: Hartmut Koptein <[EMAIL PROTECTED]>
Martin Schulze <[EMAIL PROTECTED]>
Philipp Stratmann <[EMAIL PROTECTED]>
Joerg Friedrich <[EMAIL PROTECTED]>
Gerd Bavendiek <[EMAIL PROTECTED]>
Peter Ganten <[EMAIL PROTECTED]>
Michael Bramer <[EMAIL PROTECTED]>
Torsten Landschoff <[EMAIL PROTECTED]>
Hungarian: Gergely Risko <[EMAIL PROTECTED]>
Italian: Michele Dalla Silvestra <[EMAIL PROTECTED]>
Paolo Didon� <[EMAIL PROTECTED]>
Japanese: Yoshizumi Endo <[EMAIL PROTECTED]> [1]
Atsushi Kamoshida <[EMAIL PROTECTED]>
Polish: Piotr Pogorzelski <[EMAIL PROTECTED]> (no response)
Marcin Owsiany <[EMAIL PROTECTED]>
Portuguese: Gleydson Mazioli da Silva <[EMAIL PROTECTED]>
Eduardo Marcel Macan <[EMAIL PROTECTED]>
Jose Carlos Benfati <[EMAIL PROTECTED]>
Paulo Henrique B. Oliveira <[EMAIL PROTECTED]>
Rafael Laboissiere <[EMAIL PROTECTED]>
Russian: Michael Sobolev <[EMAIL PROTECTED]>
Alexey Vyskubov <[EMAIL PROTECTED]>
Aleksey Novodvorsky <[EMAIL PROTECTED]>
Peter Novodvorsky <[EMAIL PROTECTED]>
Paul Romanchenko <[EMAIL PROTECTED]>
Slovak: Miroslav Vasko <[EMAIL PROTECTED]>
Spanish: Enrique Zanardi <[EMAIL PROTECTED]>
Fernando Herrera <[EMAIL PROTECTED]>
Sergio G�mez Bachiller <[EMAIL PROTECTED]>
Gonzalo G. Agull� <[EMAIL PROTECTED]>
Ignacio J. Alonso <[EMAIL PROTECTED]>
Tinguaro Barreno <[EMAIL PROTECTED]>
Pedro Gracia <[EMAIL PROTECTED]>
Angel David Rancel Mendoza <[EMAIL PROTECTED]>
Swedish: G\vran Andersson <[EMAIL PROTECTED]> (obsolete)
Nils-Erik Svang�rd <[EMAIL PROTECTED]>
Peter Karlsson <[EMAIL PROTECTED]>
There are a lot of names that should be on this list, and currently aren't.
I just don't know your names yet! :-)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
