Vous trouverez ici les informations relative à la localisation (l10n)de Freeciv.
Freeciv utilise le système gettext pour le support de l'internationalisation et de la localisation. Voir le fichier d'information de gettext pour plus d'information.
Voir Internationalisation pour les détails techniques de la traduction de Freeciv.
- 1 Comment contribuer ?
- 1.1 How to add support for new languages
- 1.2 How to update your translations
- 1.3 How to keep two branches in sync
- 1.4 How to create the most current freeciv.pot file
- 1.5 How to handle qualified translatable strings
- 1.6 How to check your translations for common errors
- 1.7 How to check in your translations
- 2 Localization Mini-FAQ
- 2.1 How does Freeciv determine what language it should use?
- 2.2 When I try to "make freeciv.pot", no file is generated.
- 2.3 Should I try to translate "Freeciv"?
- 2.4 The Emacs po-mode doesn't start when I load a po-file. What should I do?
- 2.5 I have GNU Gettext installed but the po-mode still doesn't start. What should I do now?
- 2.6 Emacs throws the error message "Fontifying XX.po...buffer too big" when I load a po-file. Is the po-file to big?
These address a few problems and questions about Localization.
How does Freeciv determine what language it should use?
Freeciv checks the environment variable $LANG for that, so you should set it; for example, to use German, issue the bash command "export LANG=de_DE" before you start civserver or civclient, or "setenv LANG de_DE" if you use tcsh. If you still get English, perhaps you are trying an invalid value (the value "de" instead of "de_DE" will probably fail to work) or the Freeciv software was compiled without localization support.
When I try to "make freeciv.pot", no file is generated.
It's likely that ./configure didn't find the GNU version of xgettext. Look at the output from ./configure, and if you find something like:
checking for xgettext... :
(note, just a ":", not a path to xgettext) then ./configure could not find any version of xgettext. Or, if you see something like:
checking for xgettext... /usr/bin/xgettext found xgettext program is not GNU xgettext; ignore it
then ./configure could not find the GNU version of xgettext.
In either case, you will need to get and install the GNU version of the gettext system. If they are installed in a non-standard directory, you have to add it to your $PATH before calling ./configure.
Should I try to translate "Freeciv"?
No, just leave it "Freeciv" wherever you find it. (Also, note that the "c" in "Freeciv" is not capitalized.)
The Emacs po-mode doesn't start when I load a po-file. What should I do?
Make sure you have GNU Gettext installed. You can download it from a GNU ftp mirror site.
I have GNU Gettext installed but the po-mode still doesn't start. What should I do now?
Type 'info gettext' in a shell (or use the Emacs info-mode), select 'Basics' and select 'Installation'. Then you will find more information about installing the Emacs po-mode.
Emacs throws the error message "Fontifying XX.po...buffer too big" when I load a po-file. Is the po-file to big?
Don't worry. The buffer/file size is just fine. What Emacs is trying to say is that the value of the variable font-lock-maximum-size is too small. Emacs refuses to fontify buffers larger than this value because font-lock may consume a lot of resources for big buffers. To change the value, press 'M-x', type 'customize-variable', press Return, type 'font-lock-maximum-size' and press Return. Read the helptext in the buffer that opens and customize by changing the value to something like 524288 (2^19) (or whatever value you think is suitable). Now the files should become fontified when you open them (unless they are larger than 512kB).