If you did not migrate your account yet, visit https://idp-portal-info.suse.com/
|De Engelstalige versie van dit artikel heeft aandacht nodig omdat het niet onze wiki-richtlijnen volgt. De Nederlandse versie volgt daarna de Engelse versie.|
U bent van harte welkom om de Engelstalige versie van dit artikel te verbeteren. Als u vragen hebt aarzel dan niet en neem contact met ons op. Wij zijn graag bereid u te helpen! :)
Op deze pagina vindt u informatie over aanpassen aan de taalregio ook genaamd lokalisatie (L10N, LCN) van softwarecomponenten in openSUSE. Het is van toepassing op programma's zoals YaST, de openSUSE applets voor bijwerken of het menusysteem van het bureaublad. Voor informatie over vertalen van de openSUSE wiki (deze site), zie Richtlijnen voor vertalen.
Toevoegen van een nieuwe taal
Zie hiervoor de Engelse wiki Adding a new language
Beginnen met het werk
All files to be translated are stored in a subversion repository. Find basic information about SVN access at the suse-i18n download page at http://developer.novell.com. Downloading the files from subversion is allowed for all team members via anonymous access. Committing is allowed only for team coordinators.
You should change only files of your language team. If your activity in SVN damages work of other teams, your SVN access can be blocked.
The Most Important Files
If you are at the beginning of localization, you should start with the most important files. These files belong to the most visible applications of the openSUSE distribution, like installation or YaST Control Center. The most important files are:
- and all files started with 'package' in yast/your_lang_code/
We have no percentual limits for including localization to distribution.
The PO files for you are stored in 'yast' and 'lcn' directories in the 'trunk' directory. The yast directory includes po files of YaST and the lcn directory includes PO files of other applications. All PO files should have the name in the format application_name.your_language_code.po.
-- trunk +-- doc +-- lcn | +-- 50-etc | +-- 50-memory | +-- 50-pot | +-- Makefile.am | +-- README | +-- configure.ac | +-- cs | +-- cy | +-- ...other language directories +-- www +-- yast +-- 50-pot +-- ar +-- bg +--...other language directories -- branches +--...
You do not have to download whole directories. Both directories contains subdirectories named by language codes. Find the code of your language and download only the directory with the code of your language. For example, if you want download Russian localization, use:
svn checkout https://svn.berlios.de/svnroot/repos/opensuse-i18n/trunk/yast/ru/po . svn checkout https://svn.berlios.de/svnroot/repos/opensuse-i18n/trunk/lcn/ru/po .
These commands will download the 'po' directory content to current directory. Note: without trailing '.' the 'po' directory will be created inside current directory!
It can happens that some po file of an application is missing. In this situation start translation from the template and add it to your language directory. Templates for YaST are stored in the yast/50-pot directory and templates for other applications are stored in the lcn/50-pot directory. All templates have suffix .pot.
All directories starts with '50-' are special directories. They contain the templates and scripts for automatic merging. Please do not change the content of these directories.
In the 'trunk' directory is also 'www' directory, where are stored pages of the localization portal. Please do not change the content of this directory.
- External Subversion (SVN) documentation
At the same level as 'trunk' find the 'branches' directory that contains all the branches. We use branches for testing and for released products:
We do not expect the openSUSE community to work on updates business products such as 'branches/SLE10SP1' (SUSE Linux Enterprise 10 SP1); we cannot even promise to make use of community updates there.
About PO and POT Files
Original English text in the PO file is not possible to change. You can change only translation. If you find an error in the original English text, please use Bugzilla to report it. All wrong texts must be fixed in the source code of the application first and then will be generated a new POT file and automatically merge with your files. After it, the changed string will be marked as fuzzy.
If you do not know, what is the PO and POT file, please read article Work with PO Files.
When comes a new file to localize, the translation memory is used to translate the most common strings. All strings translated with the help of the translation memory are set to the status fuzzy. To disable translation memory, send a request to stop building of the memory files to mailinglist and copy empty file yast2.$LL.po to /yast/50-memory/ and memory.$LL.po to /lcn/50-memory/, where $LL is code of your language.
Statistics are updated once a day. Time of the update is displayed on the top of the each page. If there is missing translation of some file in your language, the file is displayed as untranslated and linked to the POT file. You can translate the POT file and commit to the SVN as the PO file or wait for initialization of the POT file.
Language Team Pages
If you work in the large team, you should have your own team page in your native language. To create one, use openSUSE wiki in your language and add the link to the table of localization teams. If there is no openSUSE wiki translated into your language, create team page in the English wiki page with name your_language_code Language_name Localization Team.
Do you use a tool, which is not mentioned? Add it to the list!
- KBabel - KBabel is the part of the package kdesdk3-translate
- Lokalize - Lokalize is KDE4 successor of KBabel
- poTranslator - Download poTranslator