Pardus Translation Aid

[PhiX]

There are some lines that are not present in KDE Kcontrol.

[BenimAdımKırmızı]

well a real good thread!
i signed up!

[tribunal]

Hi all! 2 developers want to join the process of translation to russian. The only problem is that they are not developers. They don't know how to export .po-files and commit them back. Is there something like "Howto for newbie-translators"?
We know, that almost all software is translated, so only Pardus-specific software must be translated.

P.S. Shoud I create a bug about keyboard layout?

[atolboo]

To start with: Have a look at here.
And as long as you do not have a SVN account : Have a look here.
And here for a (not) complete overview.

P.S. Shoud I create a bug about keyboard layout?

Maybe, where is this problem reported?

[PhiX]

Here are some informations I use to commit my translations on SVN.

My little SVN Memento

Pre-requisite

Having asked for an SVN developper account at admins@pardus.org.tr. The SVN username has to be YourFirstname.YourName (all in small case). You also have to provide a shadow password. It can be generated by the following command :

Code:

python -c "import crypt; print crypt.crypt('password', 'xy')"

where 'password' should be replaced by the password of your choice.

1. Download an existing file

If there is an incomplete .po file for your language, you can finish its translation with :
  

Code:

snc co url-of-file-to-be-edited

For example :

Code:

svn co http://svn.pardus.org.tr/uludag/trunk/kde4/package-manager/manager/src/package-manager.notifyrc

This command downloads the corresponding files and folders on your hard drive.

2. Create a new file

If there is no po file available yet for your language, you have to create one. To do so, open Lokalize with the .pot file, begin to edit it and save a copy of it as fr.po, leaving the original .pot file untouched, so that there is the original .pot plus the newly created fr.po file. DO NOT EDIT THE ORIGINAL .POT FILE at all, because it will be reused by other translators to generate their own language files.

In the folder that contains the new fr.po file, do :

Code:

svn add fr.po

3. Locally edit the file with Lokalize or with a text editor (nano, kwrite, kate, etc.)
  
The Lokalize handbook.

4. Transmit the changes to the SVN turkish server

Code:

svn commit -m "French translation."

NB : SVN uses your PC username by default. If your SVN username is different, just type the "Enter" key when you are asked for the password. SVN will then ask you to enter your SVN username.

5. Update your local SVN copy

Before the next edition, don't forget to update your local copy in order to work on the latest version available.

Code:

svn update

6. Final SVN configuration

Contains of the ~/.subversion/servers file :

Code:

[global]
store-passwords = yes
username = MyFirstname.MyName
store-plaintext-passwords = no

NB : Remove the spaces before each line, otherwise SVN will complain with the error message : "Option expected"

7. Other useful commands

Code:

svn diff

Code:

svn status

8. Where are the po files ?

Here is the Pardus translation map that Patrik Karlsson created in order to help you to localize the .po files.


Further details on : http://www.pardus-linux.de/documents/developer/new_developer.html

[tribunal]

Thank you for new info
Several moments:
Translation map is empty... so I don't know where are .pot files...

[atolboo]

Translation map is empty... so I don't know where are .pot files...

When I go to (for instance) http://svn.pardus.org.tr/uludag/trunk/kde4/boot-manager/manager/po/ there is the source file boot-manager.pot
Download this file and rename this file to ru.po for the translation into Russian.

[tribunal]

Hi all!
Everything seems to be ok, I have started translation, but there is no reply from admins, so I cannot commit my translation

[PhiX]

You can post them on the pardus translator mailing-list, asking for a developper to commit them for you. You should then soon have a developper account.

спасибо большое

[tribunal]

Это с моей стороны спасибо

(Thank you for additional info)

[atolboo]

Until this moment I have done all my Dutch translations for Pardus and KDE in Pardus 2008 with KBabel.
I have been doing this for KDE for the past 4 years in KBabel.
In KBabel it's very easy to make a database with Settings > Configure Dictionary > Translation Database > Database > Scan Folders & Subfolders in combination with the "svn checkout" commands from http://forum.pardus-linux.nl/index.php?topic=1578.0 and ~160000 items are added to the database

And now with my transition to Pardus 2009.1 I am trying to make a similar database in Lokalize.
In this Handbook chapter I read "drag and drop a folder with translation files from say Dolphin into the view".
I think "view" means Translation Memory window.
When I drag-drop my svn-checkout folder into the Translation Memory window I get a System Notification (TM:default) for ~ 1-2 minutes (the computer is doing some search?).
But my Translation Memory window remains empty even after selecting a "File" item in the Entry list.
And this "File" item should have more than one hit.
Anybody having the same or different experience with Lokalize and/or having a solution for this problem.
Or am I doing something wrong.