Posted: Sat 16 Apr 2011, 18:52
Russian updated
(old)Puppy Linux Discussion Forum
READ-ONLY Archive
https://oldforum.puppylinux.com/
pMusic language support
Page 4 of 8
russian for 1.8
Posted: Mon 30 May 2011, 08:29
Updated Russian for Pmusic-1.8. I also found out that LOC326 is still needed.
Posted: Tue 31 May 2011, 16:47
rodin.s
I have updated Russian. I have also changed LOC326 to LOC669, so this should work properly in 1.8.1
Thank you
Sigmund
I have updated Russian. I have also changed LOC326 to LOC669, so this should work properly in 1.8.1
Thank you
Sigmund
Russian for 2.0.2
Posted: Sun 18 Sep 2011, 19:43
I have updated ru-locale file for Pmusic-2.0.2. Also LOC267 is in added and removed lists, so I decided to keep it.
Re: Russian for 2.0.2
Posted: Wed 21 Sep 2011, 07:48
It should be included. I have fixed the changelog - Thank yourodin.s wrote:Also LOC267 is in added and removed lists, so I decided to keep it.
Sigmund
Posted: Wed 21 Sep 2011, 07:51
russian updated
Posted: Wed 28 Sep 2011, 07:22
French updated
Russian for 2.1.4
Posted: Wed 28 Sep 2011, 20:21
I have updated Russian translation for Pmusic-2.1.4.
Posted: Sat 01 Oct 2011, 08:17
Russian updated
Update for Russian.
Posted: Mon 10 Oct 2011, 11:59
Russian update for Pmusic-2.1.8.
Posted: Thu 13 Oct 2011, 16:42
Russian updated
Posted: Sun 29 Jan 2012, 07:07
Polish updated
Russian translation for Pmusic-2.3.0
Posted: Sat 11 Feb 2012, 16:51
I have made Russian translation for Pmusic-2.3.0. I know it's not the latest one but it is in Woof. I'll post translation for 2.4.2 later.
Posted: Sat 11 Feb 2012, 21:22
Hello zigbert,
Here is the french file for Pmusic 2.42.
Cordialement
Here is the french file for Pmusic 2.42.
Cordialement
Posted: Fri 17 Feb 2012, 09:57
Russian and french updated
Russian translation
Posted: Thu 01 Mar 2012, 21:39
I have made Russian translation for Pmusic-2.4.4.
I also was experimenting with gettext and poedit. Locale file consists of 353 lines so it's easier to use poedit to handle it. Normal locale file is created with script gettext_script.
Some instructions how to use it are in the script:
I also was experimenting with gettext and poedit. Locale file consists of 353 lines so it's easier to use poedit to handle it. Normal locale file is created with script gettext_script.
Some instructions how to use it are in the script:
Code: Select all
# use 'xgettext -L shell gettext_file -o pmusic2.pot' to generate pot file
# use poedit to create and translate po file and then mo file will be created
# put pmusic2.mo to /usr/share/locale/xx/LC_MESSAGES (xx - name of your locale)
# run the script to create text translation file for pmusic with name of your locale (ex: ./gettext_file)
# you can run the script with your name as first parameter for tranlsator line. (ex: ./gettext_file rodin.s)
# and locale could be second parameter. If it is not given then it defaults to current locale (ex: ./gettext_file rodin.s ru_RU.UTF-8)
# place the file to /usr/local/pmusic/localsPosted: Thu 01 Mar 2012, 22:51
Sergey
I have updated the main post/pet.
I wonder if you could tell me....
What is so great about gettext? I have never used it....
I have just put all this NLS on hold until things get settled in Puppy. Now when Barry has started the work on NLS, all I see is many different standards. I hoped that Puppy should use one (or a few) to standardize the handling of language files.
From the view-point of a translater, do you find the zigbert-way hard to manage? I clearly see that I have missed the placement of the local files. I will probably move them, now when Puppy seems to be using /usr/share/locale/xx/
I simply want to learn more about the pro and cons for the different ways of doing things.
Thank you
Sigmund
I have updated the main post/pet.
I wonder if you could tell me....
What is so great about gettext? I have never used it....
I have just put all this NLS on hold until things get settled in Puppy. Now when Barry has started the work on NLS, all I see is many different standards. I hoped that Puppy should use one (or a few) to standardize the handling of language files.
From the view-point of a translater, do you find the zigbert-way hard to manage? I clearly see that I have missed the placement of the local files. I will probably move them, now when Puppy seems to be using /usr/share/locale/xx/
I simply want to learn more about the pro and cons for the different ways of doing things.
Thank you
Sigmund
gettext
Posted: Fri 02 Mar 2012, 17:23
In my opinion gettext is easy to use with scripts and internationalization could be made faster. It is a great tool for my work on Russian l10n of Puppy. Poedit has features of spell-checking and translation memory. It also works good when old script is updated. Old translation is not lost but updated automatically and new untranslated lines appear at the top of the list.
In case of Pmusic I have two files: new English file and old Russian one and then I have to compare them using information about changes made. And these changes are in different parts of the file. It takes time to find them all. These files are usually opened in different tabs of geany and I have to switch between the tabs.
Gettext is a little bit slower but it's a price I'm ready to pay for comfort. I had 2100 lines in my puppy.pot file and I could manage them with poedit but I think it would be hard to do zigbert-way.
In case of Pmusic I have two files: new English file and old Russian one and then I have to compare them using information about changes made. And these changes are in different parts of the file. It takes time to find them all. These files are usually opened in different tabs of geany and I have to switch between the tabs.
Gettext is a little bit slower but it's a price I'm ready to pay for comfort. I had 2100 lines in my puppy.pot file and I could manage them with poedit but I think it would be hard to do zigbert-way.
Posted: Sun 04 Mar 2012, 09:20
rodin.s
Thank you for the explanation.
Sigmund
Thank you for the explanation.
Sigmund
Russian translation
Posted: Sun 01 Apr 2012, 20:45
I have made Russian translation for Pmusic-2.5.3.