[opensuse-translation] Inconsistencies in files in project opensuse-i18n

newer
[opensuse-translation] Translation...

Freek de Kruijf

1 Apr 2010 1 Apr '10

19:39

Hi, Recently updated .pot files appeared in trunk webyast. However updated (merged) .po files did not appear. So I tried to do the merging myself. Because doing it all by hand did not seem smart, so I designed a script to do that, also for yast and lcn. I assumed that by checking the POT-Creation-Date in the .pot and the corresponding .po file would give me an indication whether to use msgmerge or leave things alone. However I found .pot files without a POT-Creation-Date line. I also found a file in the .../nl/po/ directory which did not end on .nl.po but only on .po Will this be improved or do we have to work with these inconsistencies? -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

Show replies by date

Carlos E. R.

1 Apr 1 Apr

20:34

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2010-04-01 at 21:39 +0200, Freek de Kruijf wrote:

...

Hi,

Recently updated .pot files appeared in trunk webyast. However updated (merged) .po files did not appear. So I tried to do the merging myself. Because doing it all by hand did not seem smart, so I designed a script to do that, also for yast and lcn.

I wrote another script, but only for webyast. I took an already existing script from lcn or yast as a base - those scripts live in the "50-tools/" directory, something "*merge". The problem is that they are not documented, we don't know their intended use. #!/bin/bash log=log.txt :>$log # Set to echo for debugging #echo=true echo=echo # set -x fromdir=~/Projects/babel/SuSE/trunk/webyast potdir=00-pot memdir=50-memory check_file () { [ -f $1 ] || { echo "*** file $1 does not exist" ; exit 1 ; } } check_dir () { [ -d $1 ] || { echo "*** directory $1 does not exist" ; exit 1 ; } } file_by_file () { fromdirpo="$fromdir/es/po" fromdirpot="$fromdir/$potdir" #$echo $fromdirpo #$echo $fromdirpot check_dir $fromdirpot for pot in $fromdirpot/*.pot; do check_file $pot textdomain=${pot##*/}; textdomain=${textdomain%\.pot} echo es/po/$textdomain.es.po | tee -a $log po=$fromdirpo/$textdomain.es.po if [ -f $po ]; then msgmerge --previous --update --backup=simple $po $pot else $echo " --> no existe $po, creandolo" | tee -a $log msginit --no-translator --locale=es_ES.utf8 --input=$pot --output=$po fi $echo echo done } [ -z "$fromdir" ] && { echo "*** from DIR missing; exiting" exit 1 } file_by_file And I see that I wrote another such a script long ago, on this desktop (the one I mention above I was using the portable and away from most of my scripts).

...

I assumed that by checking the POT-Creation-Date in the .pot and the corresponding .po file would give me an indication whether to use msgmerge or leave things alone. However I found .pot files without a POT-Creation-Date line.

I do a merge when I see the warning in "vertal". Another hint can be taken from the catalog tool kbabel uses, comparing the number of messages in the pot and po files.

...

I also found a file in the .../nl/po/ directory which did not end on .nl.po but only on .po

That's probably the fault of someone in your team; you can use "svn log somefile" and learn who created it. You can use "svn move" to rename it.

...

Will this be improved or do we have to work with these inconsistencies?

Some things need manual interaction, I think. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAku1A/EACgkQtTMYHG2NR9Uz/QCbBqkDGZfU2qBifU7HlolOPn+N Vk4An3O8lDvJAw9rf0hreuAx9a2jY8R0 =9IUo -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

Karl Eichwalder

2 Apr 2 Apr

17:15

New subject: [opensuse-translation] Inconsistencies in files in project opensuse-i18n

Am Thu 01 Apr 2010 10:34:05 PM CEST schrieb "Carlos E. R." :

...

I wrote another script, but only for webyast. I took an already existing script from lcn or yast as a base - those scripts live in the "50-tools/" directory, something "*merge".

Yes, these are the merge scripts I run from time to time (manually). If wanted, I can do it automatically every night or once the week. Maybe, we can install such a crontab entry on BerliOS. I would not mind if one of the co-admin would do the merging in the trunk. I thing the merge scripts are rather generic and do not rely on the internal SUSE infrastructure. If I'm wrong, we can change it. Of course, if there is something strange in the scripts, I'll try to explain it. Some parts are written some ten years ago, though ;)

...

The problem is that they are not documented, we don't know their intended use.

Yes, as always ;) In the beginning, these scripts were very short and no documetation was needed. But you are right, we should list the useful scripts in the wiki (and remove the obsolete files). Minimal usage info is in 50-doc/readme.txt, if you are lucky. Cheers, Karl -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

Carlos E. R.

18:12

New subject: [opensuse-translation] Inconsistencies in files in project opensuse-i18n

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2010-04-02 19:15, Karl Eichwalder wrote:

...

Am Thu 01 Apr 2010 10:34:05 PM CEST schrieb "Carlos E. R." <>:

...
I wrote another script, but only for webyast. I took an already existing script from lcn or yast as a base - those scripts live in the "50-tools/" directory, something "*merge".

Yes, these are the merge scripts I run from time to time (manually). If wanted, I can do it automatically every night or once the week. Maybe, we can install such a crontab entry on BerliOS.

Mmm... not automatically, or not for every language or file. If the merge happens when a translator is working on his local file.po copy, it is confusing and problematic. I prefer to do the merge myself of the files I'm working on. Others can do that or click a button in "vertaal".

...

Of course, if there is something strange in the scripts, I'll try to explain it. Some parts are written some ten years ago, though ;)

What is "textdomain"? In "y2-merge-from-dir.sh" O:-)

...

...
The problem is that they are not documented, we don't know their intended use.

Yes, as always ;) In the beginning, these scripts were very short and no documetation was needed. But you are right, we should list the useful scripts in the wiki (and remove the obsolete files). Minimal usage info is in 50-doc/readme.txt, if you are lucky.

Ah. I see there it points to 50-tools/y2-prep-packages.sh instead. There are so many scripts with similar purposes that it is confusing. That's why I wrote mine instead, because I don't know what I'm doing otherwise. - -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iF4EAREIAAYFAku2M5UACgkQja8UbcUWM1x4YgD/X8ufvj35qceOWIiG8jEH03hH eovONwihpbHqMZn/FRsA/RVWtTTxJK0Bk7H7gw3pPDCZAfpxW6Blta2jINAnxTlK =JvAh -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

Freek de Kruijf

3 Apr 3 Apr

09:20

Op donderdag 1 april 2010 22:34:05 schreef Carlos E. R.:

...

On Thursday, 2010-04-01 at 21:39 +0200, Freek de Kruijf wrote:

...
Hi,

Recently updated .pot files appeared in trunk webyast. However updated (merged) .po files did not appear. So I tried to do the merging myself. Because doing it all by hand did not seem smart, so I designed a script to do that, also for yast and lcn.

I wrote another script, but only for webyast. I took an already existing script from lcn or yast as a base - those scripts live in the "50-tools/" directory, something "*merge". The problem is that they are not documented, we don't know their intended use.

#!/bin/bash

log=log.txt

:>$log

# Set to echo for debugging #echo=true echo=echo # set -x

fromdir=~/Projects/babel/SuSE/trunk/webyast potdir=00-pot memdir=50-memory

check_file () { [ -f $1 ] || { echo "*** file $1 does not exist" ; exit 1 ; } }

check_dir () { [ -d $1 ] || { echo "*** directory $1 does not exist" ; exit 1 ; } }

file_by_file () { fromdirpo="$fromdir/es/po" fromdirpot="$fromdir/$potdir" #$echo $fromdirpo #$echo $fromdirpot check_dir $fromdirpot for pot in $fromdirpot/*.pot; do check_file $pot textdomain=${pot##*/}; textdomain=${textdomain%\.pot} echo es/po/$textdomain.es.po | tee -a $log po=$fromdirpo/$textdomain.es.po if [ -f $po ]; then msgmerge --previous --update --backup=simple $po $pot else $echo " --> no existe $po, creandolo" | tee -a $log msginit --no-translator --locale=es_ES.utf8 --input=$pot --output=$po fi $echo echo done }

[ -z "$fromdir" ] && { echo "*** from DIR missing; exiting" exit 1 }

file_by_file

I do miss in the above script the check on .po files that do not have a counterpart .pot file. In which case the .po file should be deleted. Currently I have in each lcn and webyast 3 of these .po files.

...

And I see that I wrote another such a script long ago, on this desktop (the one I mention above I was using the portable and away from most of my scripts).

...
I assumed that by checking the POT-Creation-Date in the .pot and the corresponding .po file would give me an indication whether to use msgmerge or leave things alone. However I found .pot files without a POT-Creation-Date line.

I do a merge when I see the warning in "vertal". Another hint can be taken from the catalog tool kbabel uses, comparing the number of messages in the pot and po files.

I have no idea what "vertal" is.

...

...
I also found a file in the .../nl/po/ directory which did not end on .nl.po but only on .po

That's probably the fault of someone in your team; you can use "svn log somefile" and learn who created it. You can use "svn move" to rename it.

Or in this case svn delete wrongfilename

...

...
Will this be improved or do we have to work with these inconsistencies?

Some things need manual interaction, I think.

I am only confronted with the above discrepancies since opensuse-i18n moved to berlios. The argument that a user might be working on a file that get automatically updated is not very strong. It probably only need good communication of the time such an automatic update will be done. In the KDE project this is done automatically and one knows that the robot "scripty" is doing its work around a certain time, for me during the night. So I only need to commit my changes before I go to bed. -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

Carlos E. R.

12:31

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2010-04-03 11:20, Freek de Kruijf wrote:

...

Op donderdag 1 april 2010 22:34:05 schreef Carlos E. R.:

...
On Thursday, 2010-04-01 at 21:39 +0200, Freek de Kruijf wrote:

...

...
file_by_file

I do miss in the above script the check on .po files that do not have a counterpart .pot file. In which case the .po file should be deleted. Currently I have in each lcn and webyast 3 of these .po files.

Perhaps it existed in the original script. Anyway, I prefer deleting those manually, once I know they really have to be deleted. Notice that you have to delete the file in svn, or you will get it back on next "svn up".

...

...
...
I assumed that by checking the POT-Creation-Date in the .pot and the corresponding .po file would give me an indication whether to use msgmerge or leave things alone. However I found .pot files without a POT-Creation-Date line.

I do a merge when I see the warning in "vertal". Another hint can be taken from the catalog tool kbabel uses, comparing the number of messages in the pot and po files.

I have no idea what "vertal" is.

The collaboration/coordination tool some of the teams use, made by Gabriel. http://www.vertaal.com.ar/ If there is a discrepancy between pot and po, pushing a button gets it done.

...

...
Some things need manual interaction, I think.

I am only confronted with the above discrepancies since opensuse-i18n moved to berlios.

Just luck. I have seen them earlier.

...

The argument that a user might be working on a file that get automatically updated is not very strong.

It has happened to me, more than once.

...

It probably only need good communication of the time such an automatic update will be done. In the KDE project this is done automatically and one knows that the robot "scripty" is doing its work around a certain time, for me during the night. So I only need to commit my changes before I go to bed.

"The night" has a different meaning for different people - time zones, you know :-p Some people work during the night. Me, I work away from network, so I can't get any "emergency" communication till many hours past. If there is any automatic or manual change I have to override it later with my own version, and then try to redo whatever change the robot or whoever did. - -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Elessar)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAku3NRIACgkQU92UU+smfQX35wCfe28Al/EozXb1u9NX/5ymeqLF GZkAn221OTIMnVHtRW67AOzOuFf50n+q =0Qi0 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

Freek de Kruijf

5 Apr 5 Apr

16:13

Op zaterdag 3 april 2010 14:31:14 schreef Carlos E. R.:

...

On 2010-04-03 11:20, Freek de Kruijf wrote:

...
Op donderdag 1 april 2010 22:34:05 schreef Carlos E. R.:

...
On Thursday, 2010-04-01 at 21:39 +0200, Freek de Kruijf wrote:

I do miss in the above script the check on .po files that do not have a counterpart .pot file. In which case the .po file should be deleted. Currently I have in each lcn and webyast 3 of these .po files.

Perhaps it existed in the original script. Anyway, I prefer deleting those manually, once I know they really have to be deleted. Notice that you have to delete the file in svn, or you will get it back on next "svn up".

Below is my script to handle .po files without corresponding .pot files, and merging .po files with newer .pot files and making .po files from a .pot file. It can be run from any directory above the trunk or branch directory. #!/bin/bash # openSUSE trunk and branch check for updates #set localization code loc="nl_NL.utf8" # save the current directory savedir=$(pwd) # setup the language lang="nl" # find the trunk and branch directories ldir=$(find ./ -name lcn) [ "ldir" != "" ] || { echo "directories with trunk and/or branch not found" ; cd $savedir; exit 1 ;} # check in all trunk and branch directories for dir in $ldir; do echo "branch/trunk is: ${dir%/lcn}" for lyw in lcn yast webyast; do cd $savedir [ -d ${dir%/lcn}/$lyw ] || { echo "$lyw directory not present" ; cd $savedir; continue ;} cd ${dir%/lcn}/$lyw echo "Now working in $(pwd)" # svn delete a .po file without a corresponding .pot file for file in $lang/po/*.po; do # there are 2 pot directories 00-pot and 50-pot, but not both is assumed here [ -d *0-pot ] || { echo "Directory *0-pot with .pot files not present"; continue ; } potfile=${file##$lang/po/}; potfile=${potfile%$lang.po}pot; #[ -f *0-pot/$potfile ] && echo "*0-pot/$potfile found" [ -f *0-pot/$potfile ] || { svn delete $file; } done [ -d *0-pot ] || continue for pot in *0-pot/*.pot; do # first check POT-Creation-Date, not equal means a merge potrevpot=$(grep POT-Creation-Date $pot) [ "$potrevpot" = "" ] && echo "$pot does not have a POT-Creation- Date:" pofile="$lang/po/${pot##*/}" pofile="${pofile%\.pot}.$lang.po" # when .po file does not exist, it needs to be created if [ ! -f $pofile ] ; then msginit --no-translator --locale=$loc --input=$pot -- output=$pofile continue fi potrevpo=$(grep POT-Creation-Date $pofile) [ "$potrevpo" = "" ] && echo "$pofile does not have a POT- Creation-Date:" [ "$potrevpot" != "" ] && [ "$potrevpo" != "" ] && [ "$potrevpot" = "$potrevpo" ] && continue echo "msgmerge --previous -U $pofile $pot" msgmerge --previous -U $pofile $pot done cd $savedir done done -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

Carlos E. R.

8 Apr 8 Apr

08:49

New subject: [opensuse-translation] Handling script [Was: Inconsistencies in files in project opensuse-i18n]

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2010-04-05 18:13, Freek de Kruijf wrote:

...

Op zaterdag 3 april 2010 14:31:14 schreef Carlos E. R.:

...
On 2010-04-03 11:20, Freek de Kruijf wrote:

...
Op donderdag 1 april 2010 22:34:05 schreef Carlos E. R.:

...
On Thursday, 2010-04-01 at 21:39 +0200, Freek de Kruijf wrote:

I do miss in the above script the check on .po files that do not have a counterpart .pot file. In which case the .po file should be deleted. Currently I have in each lcn and webyast 3 of these .po files.

Perhaps it existed in the original script. Anyway, I prefer deleting those manually, once I know they really have to be deleted. Notice that you have to delete the file in svn, or you will get it back on next "svn up".

Below is my script to handle .po files without corresponding .pot files, and merging .po files with newer .pot files and making .po files from a .pot file. It can be run from any directory above the trunk or branch directory.

Perhaps we could design a generalized script. Let me write a wishlist of features (it's beyond my scripting abilities): * assume the trunk directory structure from the cvs. Perhaps needs a configuration file with the paths. * work on any of yast, webyast, lcn, etc. * option to verify the directory structure for missing parts. * option to work on a given po file, or the entire subdirectory (--all) of one of the projects * option "verify": checks for orphaned .po files, new .pot files, non-up-to-date po files. * option "update-po" only updates po files from their corresponding pot files. Option to use memory or not. * option "purge-po" deletes po files (renames to backup, perhaps) that do not have a corresponding pot file. Creates a log file or script to run and remove them from the cvs too. * option "new-po" creates new po files from new pot file. Creates a log file or script to run and add them to the cvs too. All or most of this already exists, only that we do not know where, and only for one project. Ah! When, and who, and how, creates the memory files? - -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iF4EAREIAAYFAku9mLIACgkQja8UbcUWM1yaQwD+NA2b5gmjZBnjrPVAuqphwkEf fgxYtS44O1j5SusEEUEBAICS4nVUxqqmny+2pISZE2Q+fAwCILZiG/Et0OFu2y8N =YC44 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

Karl Eichwalder

9 Apr 9 Apr

12:43

New subject: [opensuse-translation] Handling script

"Carlos E. R." writes:

...

Perhaps we could design a generalized script. Let me write a wishlist of features (it's beyond my scripting abilities):

Nice list with valid features.

...

* assume the trunk directory structure from the cvs. Perhaps needs a configuration file with the paths. * work on any of yast, webyast, lcn, etc. * option to verify the directory structure for missing parts. * option to work on a given po file, or the entire subdirectory (--all) of one of the projects * option "verify": checks for orphaned .po files, new .pot files, non-up-to-date po files. * option "update-po" only updates po files from their corresponding pot files. Option to use memory or not.

I'd even say: Option to use default or any translation memory resp. compendium file (gettext uses the term "compendium file").

...

* option "purge-po" deletes po files (renames to backup, perhaps) that do not have a corresponding pot file. Creates a log file or script to run and remove them from the cvs too. * option "new-po" creates new po files from new pot file. Creates a log file or script to run and add them to the cvs too.

All or most of this already exists, only that we do not know where, and only for one project.

Yes, I think so :) I'd like to add the following aspects: Creating packages where appropriate (u-d-f, yast) or creating translation bundles suitable for packaging. Cross-product merging and pulling from and pushing upto upstream where appropriate. I think Stanislav's gnome-patch-translation can do this in a configuarble manner.

...

Ah! When, and who, and how, creates the memory files?

Normally this is or was me. But because some teams to not like this memory based initialization of translations that much, I'm a little bit hesitant ;) IIRC, they prefer memory based translations set to fuzzy, which I did not get around implementing that far. -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

Александр Мелентьев

10 Apr 10 Apr

20:16

New subject: [opensuse-translation] Handling script

...

Creating packages where appropriate (u-d-f, yast) or creating translation bundles suitable for packaging. This is a completely different task, at least thats not what

...

Cross-product merging and pulling from and pushing upto upstream where appropriate. I think Stanislav's gnome-patch-translation can do this in a configuarble manner. We raised that question some time ago: files with upstream

While creating such a tool would be nice, let's not overhead this with enormous functionality, it's not a UNIX-way of things =) It is obvious that we need to split the tasks: 1) Syncing (merging) po's with pot's (this is just technical issue, that needs to be solved on a regular basis) 2) Translation memory tasks (this one is not just technical, but also political, cause we know that not every team wishes to use TM's) 3) Packaging translators think about in the first place.=) But I'd like to get messed with it some time later... 4) Upstream translations require a completely different workflow for both developers and translators, so that some separate tools (and, as I believe, separate repo branch ;) ), but that definitely deserves a separate discussion at least =) -- Regards, Minton. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

Olav P.

3 Apr 3 Apr

11:31

Torsdag 1. april 2010 21.39.09 skrev Freek de Kruijf :

...

Hi,

Recently updated .pot files appeared in trunk webyast. However updated (merged) .po files did not appear. So I tried to do the merging myself.

I have noticed this as well, along with some pot files in the lcn tree. Will these files be "merged" at some point of the future or will I (as a regular translator) have to perform some action to "merge" the files for my own language? I suppose it is not enough to merely rename the files and replace the pot extension with the proper language extension? I'm aware that this probably sounds quite ill-informed :-). However, I know how to update local copies, translate these as required and then commit translated files. So, will there be some sort of "central merge" in the future, or will I have to educate myself about what to do with these pot files for my language? And if so, is there a pointer to straighforward instructions about how to proceed? Olav -- openSUSE VERSION = 11.2 Powered by Kernel: 2.6.31.12-0.2-desktop Linux x86_64 13:16 up 0:03, 2 users, load average: 1,69, 1,47, 0,62 -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

Carlos E. R.

12:39

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2010-04-03 13:31, Olav P. wrote:

...

Torsdag 1. april 2010 21.39.09 skrev Freek de Kruijf :

...
Hi,

Recently updated .pot files appeared in trunk webyast. However updated (merged) .po files did not appear. So I tried to do the merging myself.

I have noticed this as well, along with some pot files in the lcn tree.

Will these files be "merged" at some point of the future or will I (as a regular translator) have to perform some action to "merge" the files for my own language? I suppose it is not enough to merely rename the files and replace the pot extension with the proper language extension?

Something like this can be used to create the po. msginit --no-translator --locale=es_ES.utf8 --input=$pot --output=$po fi There is another method that includes the memory file, so that some messages get a fuzzy translation, but I prefer doing it with kbabel.

...

I'm aware that this probably sounds quite ill-informed :-). However, I know how to update local copies, translate these as required and then commit translated files.

So, will there be some sort of "central merge" in the future, or will I have to educate myself about what to do with these pot files for my language?

And if so, is there a pointer to straighforward instructions about how to proceed?

I suppose that when devs add a new pot file the corresponding po file should be created for all languages on the same operation. It is easier for us all. - -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Elessar)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAku3NwoACgkQU92UU+smfQWCCQCZARwHZEFxsPzVvBjNfQYDwziz sPcAnjs53NFsHAGnko8/8Lj1hN1p8++i =DlXn -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

Александр Мелентьев

15:58

New subject: [opensuse-translation] Inconsistencies in files in project opensuse-i18n

2010/4/3 Carlos E. R. :

...

...
So, will there be some sort of "central merge" in the future, or will I have to educate myself about what to do with these pot files for my language?

And if so, is there a pointer to straighforward instructions about how to proceed?

I suppose that when devs add a new pot file the corresponding po file should be created for all languages on the same operation. It is easier for us all. Agreed on that one: automatic po file creation is a 'must have' feature, since it is making our life easier =) However, this goes also for automatic merge with the latest pot file (e.g. just before statistics recounting), cause different 'Total' number for different languages confuses and discourages people. For instance, I myself desperately need this feature, cause being in sync with the latest pot is much more important than being in sync with the latest translator :) (those hypothetical 'working changes' will get solved on the next-day automerge) -- Regards, Minton. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

Carlos E. R.

18:43

New subject: [opensuse-translation] Inconsistencies in files in project opensuse-i18n

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2010-04-03 17:58, Александр Мелентьев wrote:

...

2010/4/3 Carlos E. R. :

...
...
So, will there be some sort of "central merge" in the future, or will I have to educate myself about what to do with these pot files for my language?

And if so, is there a pointer to straighforward instructions about how to proceed?

I suppose that when devs add a new pot file the corresponding po file should be created for all languages on the same operation. It is easier for us all. Agreed on that one: automatic po file creation is a 'must have' feature, since it is making our life easier =) However, this goes also for automatic merge with the latest pot file (e.g. just before statistics recounting), cause different 'Total' number for different languages confuses and discourages people. For instance, I myself desperately need this feature, cause being in sync with the latest pot is much more important than being in sync with the latest translator :) (those hypothetical 'working changes' will get solved on the next-day automerge)

Well... ok if the hour can be choosen by each team. - -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iF4EAREIAAYFAku3jF4ACgkQja8UbcUWM1yF+gD+LH2F1Xgc7oZNtvff5/4Gauja I3RbgH9Ongn2fgabqHQA/AlZzPFISyOePgTihJvXR17jBdxPzUgsAh3QsBMnfOjU =akY7 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

Karl Eichwalder

7 Apr 7 Apr

08:12

New subject: openSUSE 11.3 Translation Roadmap (Re: [opensuse-translation] Inconsistencies in files in project opensuse-i18n)

Here some news, hints, and remarks. "Olav P." writes:

...

Torsdag 1. april 2010 21.39.09 skrev Freek de Kruijf :

...

...
Recently updated .pot files appeared in trunk webyast. However updated (merged) .po files did not appear. So I tried to do the merging myself.

I have noticed this as well, along with some pot files in the lcn tree.

Will these files be "merged" at some point of the future

Yes, merging will happen pretty soon now. But it does not hurt if those who are familiar with this stuff, do the merging on their own for their language. That's at least my opinion. Instruction about merging are in the yast/50-doc/readme.txt and lcn/README, both files need some love... webyast/README is just a copy of the lcn/README ;-( Once things are settled, adjust the wiki accordingly. -=-=-=-=-=-=-=-=-=-=-=-=-=- cut here -=-=-=-=-=-=-=-=-=-=-=-=-=- Merging ======= Yesterday I asked the developers to honor the string freeze and to submit "final" pot files. This will happen during this week, when they are back from vacation, have read their mail backlog, and fixed other things ;) It's my plan to merge everthing on Thursday in the early afternoon and take a look on Friday again. Today I'll probably pull in the update-desktop-files; but feel free to ignore those for the moment--additional imports will still happen! Using SLE11 SP1 Translations ============================ Novell Globalization Services are about to finish the SLE11 SP1 Translations. Because many software pieces are developed in close cooperation across the products, it would be a good thing, if you'd make use of the translations in the SLE11 branch. The following translations are available in SLE11 SP1 (not all of them are fully done, some of them are only needed for special projects and thus intentional incomplete): ar cs da de el en_GB en_US es fi fr hu it ja ko nb nl pl pt_BR ru sv tr uk zh_CN zh_TW To see the differently translated messages, you can msgcat. Vice versa, Novell Globalization Services has based the SLE11 SP1 translations on the community translations. This is especially true for webyast, lcn upstream software, and new yast messages. -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

Martin Schlander

12:34

New subject: openSUSE 11.3 Translation Roadmap (Re: [opensuse-translation] Inconsistencies in files in project opensuse-i18n)

Onsdag den 7. april 2010 10:12:19 skrev Karl Eichwalder:

...

Using SLE11 SP1 Translations ============================

Novell Globalization Services are about to finish the SLE11 SP1 Translations. Because many software pieces are developed in close cooperation across the products, it would be a good thing, if you'd make use of the translations in the SLE11 branch. The following translations are available in SLE11 SP1 (not all of them are fully done, some of them are only needed for special projects and thus intentional incomplete):

ar cs da de el en_GB en_US es fi fr hu it ja ko nb nl pl pt_BR ru sv tr uk zh_CN zh_TW

To see the differently translated messages, you can msgcat.

Vice versa, Novell Globalization Services has based the SLE11 SP1 translations on the community translations. This is especially true for webyast, lcn upstream software, and new yast messages.

Is SLE11 SP1 == SLE11-GA on berlios or is it somewhere else? I wanted to check out sle11sp1 translations from svn and try to use them as an "alternative translations folder" in lokalize, whereby lokalize should show me the matching SLE translations in a toolview, and let me re-use them if I want. But I'm unsure if I checked out the right stuff. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

Karl Eichwalder

13:00

New subject: openSUSE 11.3 Translation Roadmap (Re: [opensuse-translation] Inconsistencies in files in project opensuse-i18n)

Martin Schlander writes:

...

Is SLE11 SP1 == SLE11-GA on berlios or is it somewhere else?

No, SLE11 SP1 is here (consider it the trunk of the SLE11 product): https://svn.berlios.de/svnroot/repos/opensuse-i18n/branches/SLE11/ The SLE11-GA branch matches the initial SLE11 release (patchlevel #0). Sorry for the confusion.

...

I wanted to check out sle11sp1 translations from svn and try to use them as an "alternative translations folder" in lokalize, whereby lokalize should show me the matching SLE translations in a toolview, and let me re-use them if I want.

Perfect strategy, I'd say!

...

But I'm unsure if I checked out the right stuff.

I fear you checked out the wrong branch ;-( -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

Carlos E. R.

8 Apr 8 Apr

08:14

New subject: openSUSE 11.3 Translation Roadmap (Re: [opensuse-translation] Inconsistencies in files in project opensuse-i18n)

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2010-04-07 10:12, Karl Eichwalder wrote:

...

Using SLE11 SP1 Translations ============================

Novell Globalization Services are about to finish the SLE11 SP1 Translations. Because many software pieces are developed in close cooperation across the products, it would be a good thing, if you'd make use of the translations in the SLE11 branch.

We talked about this in the Spanish team, and in general we decided to keep our version, and leave up to each translator to revise their files and whether to take anything and what. You see, we have our own glosary and rules, sometimes intensely discussed, and in this process the other team doesn't participate. - -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iF4EAREIAAYFAku9kEcACgkQja8UbcUWM1y7ngD9HSS0oTgxjIshoroBN+AY+zsR xFvU60l8Ymg0uqZhuhQA/3XsNv0YP500Zswgr4k6whGpAvucvaA5S5jL8SX9Uosb =CgxJ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

Karl Eichwalder

14:17

New subject: openSUSE 11.3 Translation Roadmap (Re: [opensuse-translation] Inconsistencies in files in project opensuse-i18n)

Karl Eichwalder writes:

...

It's my plan to merge everthing on Thursday in the early afternoon and take a look on Friday again. Today I'll probably pull in the update-desktop-files; but feel free to ignore those for the moment--additional imports will still happen!

ATM, I'm merging the freshly sumitted YaST files. I guess, lcn will follow tomorrow. -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

Karl Eichwalder

9 Apr 9 Apr

12:29

New subject: openSUSE 11.3 Translation Roadmap (Re: [opensuse-translation] Inconsistencies in files in project opensuse-i18n)

Karl Eichwalder writes:

...

Karl Eichwalder writes:

...
It's my plan to merge everthing on Thursday in the early afternoon and take a look on Friday again. Today I'll probably pull in the update-desktop-files; but feel free to ignore those for the moment--additional imports will still happen!

ATM, I'm merging the freshly sumitted YaST files. I guess, lcn will follow tomorrow.

The lcn merge is running now. -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

Olav P.

10 Apr 10 Apr

14:51

New subject: openSUSE 11.3 Translation Roadmap (Re: [opensuse-translation] Inconsistencies in files in project opensuse-i18n)

Torsdag 8. april 2010 16.17.43 skrev Karl Eichwalder :

...

Karl Eichwalder writes:

...
It's my plan to merge everthing on Thursday in the early afternoon and take a look on Friday again. Today I'll probably pull in the update-desktop-files; but feel free to ignore those for the moment--additional imports will still happen!

ATM, I'm merging the freshly sumitted YaST files. I guess, lcn will follow tomorrow.

And perhaps webyast will follow as well? :) Olav -- openSUSE VERSION = 11.2 Powered by Kernel: 2.6.31.12-0.2-desktop Linux x86_64 16:49 up 7 days 3:36, 2 users, load average: 0,34, 0,50, 0,44 -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

Karl Eichwalder

15 Apr 15 Apr

11:47

New subject: openSUSE 11.3 Translation Roadmap (Re: [opensuse-translation] Inconsistencies in files in project opensuse-i18n)

"Olav P." writes:

...

Torsdag 8. april 2010 16.17.43 skrev Karl Eichwalder :

...

...
ATM, I'm merging the freshly sumitted YaST files. I guess, lcn will follow tomorrow.

And perhaps webyast will follow as well?

:)

This is too new, thus I usually forget about it ;) It will follow later the day... -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

5134

Age (days ago)

5148

Last active (days ago)

List overview

Download

21 comments

7 participants

participants (7)

Carlos E. R.
Carlos E. R.
Freek de Kruijf
Karl Eichwalder
Martin Schlander
Olav P.
Александр Мелентьев