[opensuse-translation] Before starting with 11.2 translations

newer
Fwd: [opensuse-translation] First...

Karl Eichwalder

23 Feb 2009 23 Feb '09

13:42

The official SLED 11 and SLES 11 translations are mostly done now. Comparing with openSUSE 11.1 (= trunk) many messages are translated differently. To avoid a fork-like product, it is desirable to align translations as close as possible. It would be great if you could make use of SLE 11 translations, as vice versa SLE translators are encouraged to make use of openSUSE translations. But now it is your turn; these translations are available in the SLE11 branch: ar cs de en_GB en_US es fr hu it ja ko nl pl pt_BR ru sv zh_CN zh_TW There is an experimental merge script in the yast directory of the trunk: 50-tools/y2-merge-from-dir.sh With .../branches/SLE11/yast checked out, use it as follows: cd .../trunk/yast 50-tools/y2-merge-from-dir.sh -f ../../branches/SLE11/yast -s -l de With -f you point to the translations of the branch; -s means, merge file by file (single), and -l denotes the language. Once done, you will see fuzzy entries auch as: #: data/country.ycp:31 data/country_long.ycp:36 #, fuzzy msgid "Czech Republic" msgstr "" "#-#-#-#-# base.de.po (base) #-#-#-#-#\n" "Tschechien\n" "#-#-#-#-# base.de.po (base.de) #-#-#-#-#\n" "Tschechische Republik" The first variant comes from the SLE11 branch and the second is the openSUSE variant. Resolve this fuzzy as every other fuzzy message. I'd appreciate feedback. Maybe, there are better ways :-) Cheers, Karl -- 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

Show replies by thread

Michael Skiba

24 Feb 24 Feb

00:25

Am Montag, 23. Februar 2009 14:42:59 schrieb Karl Eichwalder:

...

50-tools/y2-merge-from-dir.sh

With .../branches/SLE11/yast checked out, use it as follows:

cd .../trunk/yast 50-tools/y2-merge-from-dir.sh -f ../../branches/SLE11/yast -s -l de

Unfortunately I get the following error: michael@Melchior:~/SVN/suse-i18n/trunk/yast> 50-tools/y2-merge-from-dir.sh -f ../../branches/SLE11/yast -s -l de 50-tools/y2-merge-from-dir.sh: line 93: [: too many arguments However I'd also like to use this mail to point out to a feature of lokalize which does pretty much the same: The sync/merge feature. You can compare the current work with another source (and even a third source), easily switch between messages were something changed and also easily apply those changes. Very useful feature for coordinators and for operations like this one. Regards Michael

Michael Skiba

00:41

Am Montag, 23. Februar 2009 14:42:59 schrieb Karl Eichwalder:

...

The official SLED 11 and SLES 11 translations are mostly done now. Comparing with openSUSE 11.1 (= trunk) many messages are translated differently.

To avoid a fork-like product, it is desirable to align translations as close as possible. It would be great if you could make use of SLE 11 translations, as vice versa SLE translators are encouraged to make use of openSUSE translations. But now it is your turn; these translations are available in the SLE11 branch:

btw. is there a place to communicate with those people / report mistakes in the translations? Regards Michael

Freek de Kruijf

01:07

Op maandag 23 februari 2009, schreef Karl Eichwalder:

...

The official SLED 11 and SLES 11 translations are mostly done now. Comparing with openSUSE 11.1 (= trunk) many messages are translated differently.

The branch openSUSE-11_1-Branch is not present on the webpage http://i18n.opensuse.org/stats/toplist.php -- fr.gr. Freek de Kruijf Member openSUSE community -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

Karl Eichwalder

02:22

Am Tue 24 Feb 2009 01:41:16 AM CET schrieb Michael Skiba :

...

Am Montag, 23. Februar 2009 14:42:59 schrieb Karl Eichwalder:

...
The official SLED 11 and SLES 11 translations are mostly done now. Comparing with openSUSE 11.1 (= trunk) many messages are translated differently.

To avoid a fork-like product, it is desirable to align translations as close as possible. It would be great if you could make use of SLE 11 translations, as vice versa SLE translators are encouraged to make use of openSUSE translations. But now it is your turn; these translations are available in the SLE11 branch:

btw. is there a place to communicate with those people / report mistakes in the translations?

I guess a trick would be to file those as openSUSE bugs. Then I could change the component to SLED/SLES. "Evaluation downloads" such as http://www.novell.com/products/desktop/eval.html might also be an option--I never tried to report bugs using the evaluation "Activation Code"... Shane, what do you think? Karl -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

Karl Eichwalder

09:01

Michael Skiba writes:

...

...
With .../branches/SLE11/yast checked out, use it as follows:

cd .../trunk/yast 50-tools/y2-merge-from-dir.sh -f ../../branches/SLE11/yast -s -l de

Unfortunately I get the following error: michael@Melchior:~/SVN/suse-i18n/trunk/yast> 50-tools/y2-merge-from-dir.sh -f ../../branches/SLE11/yast -s -l de 50-tools/y2-merge-from-dir.sh: line 93: [: too many arguments

Probably a quoting issue. Please 'svn up' and call it with -x: 50-tools/y2-merge-from-dir.sh -x -f ../../branches/SLE11/yast -s -l de \ 2>&1 | tee log.txt and send me log.txt.

...

However I'd also like to use this mail to point out to a feature of lokalize which does pretty much the same: The sync/merge feature.

You can compare the current work with another source (and even a third source), easily switch between messages were something changed and also easily apply those changes.

Very useful feature for coordinators and for operations like this one.

This sounds great. lokalize users should make use of it and others are encouraged to give it a try :) -- 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

Andrea Florio

09:23

Karl Eichwalder ha scritto:

...

Michael Skiba writes:

...
...
With .../branches/SLE11/yast checked out, use it as follows:

cd .../trunk/yast 50-tools/y2-merge-from-dir.sh -f ../../branches/SLE11/yast -s -l de Unfortunately I get the following error: michael@Melchior:~/SVN/suse-i18n/trunk/yast> 50-tools/y2-merge-from-dir.sh -f ../../branches/SLE11/yast -s -l de 50-tools/y2-merge-from-dir.sh: line 93: [: too many arguments

Probably a quoting issue. Please 'svn up' and call it with -x:

50-tools/y2-merge-from-dir.sh -x -f ../../branches/SLE11/yast -s -l de \ 2>&1 | tee log.txt

and send me log.txt.

same issue.. log attached + shift + true + case "$1" in + fromdir=../../SLED11/yast/ + check_dir ../../SLED11/yast/ + '[' -d ../../SLED11/yast/ ']' + shift 2 + true + case "$1" in + single=true + shift + true + case "$1" in + langs=' it' + shift 2 + true + case "$1" in + shift + break + '[' -z ../../SLED11/yast/ ']' + '[' -z ' it' ']' + log=log.txt + : + potdir=50-pot + memdir=50-memory + for l in '$langs' + '[' -r ../../SLED11/yast//50-memory/yast2.it.po ']' + mem_file=50-memory/memory.it.po + '[' -n '' ']' + '[' -z true ']' + file_by_file it + local ll=it + fromdirpo=../../SLED11/yast//it/po + true ../../SLED11/yast//it/po + for pot in '$potdir/*.pot' + textdomain='*.pot' + textdomain='*' + true it/po/add-on-creator.it.po it/po/add-on.it.po it/po/audit-laf.it.po it/po/autofs.it.po it/po/autoinst.it.po it/po/backup.it.po it/po/base.it.po it/po/bootloader.it.po it/po/ca-management.it.po it/po/casa-ats.it.po it/po/CASA.it.po it/po/control-center.it.po it/po/control.it.po it/po/country.it.po it/po/dhcp-server.it.po it/po/dirinstall.it.po it/po/dns-server.it.po it/po/drbd.it.po it/po/fingerprint-reader.it.po it/po/firewall.it.po it/po/firewall-services.it.po it/po/firstboot.it.po it/po/ftp-server.it.po it/po/heartbeat.it.po it/po/http-server.it.po it/po/inetd.it.po it/po/installation.it.po it/po/instserver.it.po it/po/irda.it.po it/po/iscsi-client.it.po it/po/iscsi-server.it.po it/po/isns.it.po it/po/iso-countries.it.po it/po/iso-languages.it.po it/po/kdump.it.po it/po/kerberos.it.po it/po/kerberos-server.it.po it/po/kernel-update-tool.it.po it/po/languages_db.it.po it/po/ldap-client.it.po it/po/ldap-server.it.po it/po/linux-user-mgmt.it.po it/po/live-installer.it.po it/po/mail.it.po it/po/mouse.it.po it/po/multipath.it.po it/po/ncurses.it.po it/po/ncurses-pkg.it.po it/po/network.it.po it/po/nfs.it.po it/po/nfs_server.it.po it/po/nis.it.po it/po/nis_server.it.po it/po/ntp-client.it.po it/po/OneClickInstall.it.po it/po/online-update.it.po it/po/packager.it.po it/po/pam.it.po it/po/phone-services.it.po it/po/pkg-bindings.it.po it/po/power-management.it.po it/po/printer.it.po it/po/product-creator.it.po it/po/profile-manager.it.po it/po/qt.it.po it/po/qt-pkg.it.po it/po/registration.it.po it/po/reipl.it.po it/po/repair.it.po it/po/restore.it.po it/po/rpm-groups.it.po it/po/runlevel.it.po it/po/s390.it.po it/po/samba-client.it.po it/po/samba-server.it.po it/po/samba-users.it.po it/po/scanner.it.po it/po/security.it.po it/po/slepos-installation.it.po it/po/slp.it.po it/po/slp-server.it.po it/po/sound_db.it.po it/po/sound.it.po it/po/squid.it.po it/po/sshd.it.po it/po/storage.it.po it/po/sudo.it.po it/po/sysconfig.it.po it/po/system-profile.it.po it/po/tftp-server.it.po it/po/timezone_db.it.po it/po/tune.it.po it/po/tv.it.po it/po/update.it.po it/po/users.it.po it/po/vm.it.po it/po/wagon.it.po it/po/wol.it.po it/po/x11.it.po it/po/xpram.it.po it/po/yast2-apparmor.it.po it/po/yast2-gtk.it.po + '[' -f it/po/add-on-creator.it.po it/po/add-on.it.po it/po/audit-laf.it.po it/po/autofs.it.po it/po/autoinst.it.po it/po/backup.it.po it/po/base.it.po it/po/bootloader.it.po it/po/ca-management.it.po it/po/casa-ats.it.po it/po/CASA.it.po it/po/control-center.it.po it/po/control.it.po it/po/country.it.po it/po/dhcp-server.it.po it/po/dirinstall.it.po it/po/dns-server.it.po it/po/drbd.it.po it/po/fingerprint-reader.it.po it/po/firewall.it.po it/po/firewall-services.it.po it/po/firstboot.it.po it/po/ftp-server.it.po it/po/heartbeat.it.po it/po/http-server.it.po it/po/inetd.it.po it/po/installation.it.po it/po/instserver.it.po it/po/irda.it.po it/po/iscsi-client.it.po it/po/iscsi-server.it.po it/po/isns.it.po it/po/iso-countries.it.po it/po/iso-languages.it.po it/po/kdump.it.po it/po/kerberos.it.po it/po/kerberos-server.it.po it/po/kernel-update-tool.it.po it/po/languages_db.it.po it/po/ldap-client.it.po it/po/ldap-server.it.po it/po/linux-user-mgmt.it.po it/po/live-installer.it.po it/po/mail.it.po it/po/mouse.it.po it/po/multipath.it.po it/po/ncurses.it.po it/po/ncurses-pkg.it.po it/po/network.it.po it/po/nfs.it.po it/po/nfs_server.it.po it/po/nis.it.po it/po/nis_server.it.po it/po/ntp-client.it.po it/po/OneClickInstall.it.po it/po/online-update.it.po it/po/packager.it.po it/po/pam.it.po it/po/phone-services.it.po it/po/pkg-bindings.it.po it/po/power-management.it.po it/po/printer.it.po it/po/product-creator.it.po it/po/profile-manager.it.po it/po/qt.it.po it/po/qt-pkg.it.po it/po/registration.it.po it/po/reipl.it.po it/po/repair.it.po it/po/restore.it.po it/po/rpm-groups.it.po it/po/runlevel.it.po it/po/s390.it.po it/po/samba-client.it.po it/po/samba-server.it.po it/po/samba-users.it.po it/po/scanner.it.po it/po/security.it.po it/po/slepos-installation.it.po it/po/slp.it.po it/po/slp-server.it.po it/po/sound_db.it.po it/po/sound.it.po it/po/squid.it.po it/po/sshd.it.po it/po/storage.it.po it/po/sudo.it.po it/po/sysconfig.it.po it/po/system-profile.it.po it/po/tftp-server.it.po it/po/timezone_db.it.po it/po/tune.it.po it/po/tv.it.po it/po/update.it.po it/po/users.it.po it/po/vm.it.po it/po/wagon.it.po it/po/wol.it.po it/po/x11.it.po it/po/xpram.it.po it/po/yast2-apparmor.it.po it/po/yast2-gtk.it.po ']' ./y2-merge-from-dir.sh: line 89: [: too many arguments + cat log.txt + exit 0

Karl Eichwalder

09:56

Andrea Florio writes:

...

same issue.. log attached ... + fromdirpo=../../SLED11/yast//it/po + true ../../SLED11/yast//it/po + for pot in '$potdir/*.pot' + textdomain='*.pot' + textdomain='*'

The 50-pot directory does not exist. Please, also 'svn up 50-pot' from the yast directory. I added a check to catch this error. -- 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

Shane Wims

10:17

New subject: [opensuse-translation] Before starting with 11.2 translations

Hi Karl, I think opening them as openSUSE bugs is the way to go, and then changing the product to SUSE Linux Enterprise Desktop/Server 11 SP1, once those options are available in Bugzilla. We could differentiate them by using an agreed whiteboard entry, for example "From_openSUSE". regards Shane Wims Localisation Engineer Novell Ireland Software Limited Corrig Court, Corrig Road Sandyford Business Park Dublin 18 e-mail: swims@novell.com Phone: +35316058293 Novell. Making IT Work As One http://www.novell.com/ Registered in Ireland No: 223694

...

...
...
On Tue, Feb 24, 2009 at 2:22 AM, in message <20090224032233.opcejanq8goks8gs@imap.suse.de>, Karl Eichwalder btw. is there a place to communicate with those people / report mistakes in the translations?

I guess a trick would be to file those as openSUSE bugs. Then I could change the component to SLED/SLES. "Evaluation downloads" such as http://www.novell.com/products/desktop/eval.html might also be an option--I never tried to report bugs using the evaluation "Activation Code"...

Shane, what do you think?

Karl

-- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

Andrea Florio

10:32

Karl Eichwalder ha scritto:

...

Andrea Florio writes:

...
same issue.. log attached ... + fromdirpo=../../SLED11/yast//it/po + true ../../SLED11/yast//it/po + for pot in '$potdir/*.pot' + textdomain='*.pot' + textdomain='*'

The 50-pot directory does not exist. Please, also 'svn up 50-pot' from the yast directory. I added a check to catch this error.

looks to be ok now (but i need also 50-memory): anubis@Hp-Linux:~/openSUSE/trunk/yast> 50-tools/y2-merge-from-dir.sh -f ../../SLED11/yast -s -l it ....................................... fatto. ........ fatto. ............. fatto. ....... fatto. .............................................. fatto. ................................ fatto. .......................................................................................... fatto. ../../SLED11/yast/it/po/bootloader.it.po:866: i messaggi internazionalizzati non devono contenere la sequenza di escape "\b" ............................................ fatto. it/po/bootloader.it.po.tmp:1276: i messaggi internazionalizzati non devono contenere la sequenza di escape "\b" ................................................... fatto. .......... fatto. ...... fatto. ..... fatto. ........ fatto. .................. fatto. ........................................ fatto. ...... fatto. ........................................... fatto. ....... fatto. ....... fatto. ............................... fatto. .......... fatto. ..... fatto. ../../SLED11/yast/it/po/ftp-server.it.po:1505: i messaggi internazionalizzati non devono contenere la sequenza di escape "\b" ................................ fatto. it/po/ftp-server.it.po.tmp:2346: i messaggi internazionalizzati non devono contenere la sequenza di escape "\b" .................. fatto. .............................. fatto. ........... fatto. ........................................ fatto. ............ fatto. ... fatto. .......... fatto. ......... fatto. ........ fatto. ......................... fatto. ................................................. fatto. ...................... fatto. ............... fatto. .................... fatto. .. fatto. ....... fatto. ........................ fatto. ........................................ fatto. .............. fatto. ..... fatto. ............................................ fatto. ..... fatto. ......... fatto. ..................... fatto. ... fatto. ................................................................................................................... fatto. ........ fatto. .......... fatto. ........... fatto. ................. fatto. ....................... fatto. ......... fatto. ........... fatto. ............................................. fatto. . fatto. ....... fatto. .... fatto. .......... fatto. ....................................... fatto. .................................... fatto. ............. fatto. .............................. fatto. .... fatto. .................. fatto. ...... fatto. .............................................................. fatto. ............... fatto. ...................... fatto. ............. fatto. .............. fatto. ................ fatto. ............................ fatto. ... fatto. .................... fatto. ..................... fatto. ...... fatto. .. fatto. ....... fatto. ................ fatto. ......................... fatto. ............................. fatto. ...... fatto. ../../SLED11/yast/it/po/storage.it.po:1780: i messaggi internazionalizzati non devono contenere la sequenza di escape "\v" .................................................................................................... fatto. it/po/storage.it.po.tmp:2149: i messaggi internazionalizzati non devono contenere la sequenza di escape "\v" ............ fatto. ............ fatto. .... fatto. ... fatto. ................................................ fatto. ............................ fatto. ...................... fatto. ............ fatto. .................................................................. fatto. ... fatto. ... fatto. ... fatto. .............. fatto. ... fatto. .............................................. fatto. ...................... fatto.

Karl Eichwalder

14:31

Andrea Florio writes:

...

looks to be ok now (but i need also 50-memory):

I thought this was optional. But probably you are right. -- 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

25 Feb 25 Feb

10:49

Freek de Kruijf writes:

...

Op maandag 23 februari 2009, schreef Karl Eichwalder:

...
The official SLED 11 and SLES 11 translations are mostly done now. Comparing with openSUSE 11.1 (= trunk) many messages are translated differently.

The branch openSUSE-11_1-Branch is not present on the webpage http://i18n.opensuse.org/stats/toplist.php

Yes, Klára is working on this. Expect it to appear 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

Jannick Kuhr

26 Feb 26 Feb

09:05

2009/2/23 Karl Eichwalder :

...

To avoid a fork-like product, it is desirable to align translations as close as possible. =A0It would be great if you could make use of SLE 11 translations, as vice versa SLE translators are encouraged to make use of openSUSE translations.

Could you tell me when and why these SLE translations have been created? In many files, especially files we (the german team) have proof read before the 11.1 release are very different (70%?). Many changes/improvements (conformity with Gnome/KDE!) are reverted, other strings are just translated differently - not better not worse. Of course some typos have been fixed, others been introduced. But in general I would say that at least our files recently proofread before the 11.1 release are better. I have the impression that for at least some files SLE did not make any use of our translations or real fork happened a long time ago. For example the installation.de.po from openSUSE is almost an other translation. There are only few strings the same and our openSUSE translations are absolutely ok. There was no reason to change almost every string and/or revert improvements made by the openSUSE team in the past. I am a bit angry about this situation and I don't understand why openSUSE should have a community based team, if there also payed translators working independently from us. I don't really understand why I should spend rare time in translating and improving translations for openSUSE, if S.u.S.E. has it's own teams... Sorry. Kind regards, Jannick Kuhr (German OpenSUSE and KDE translation team) -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

Olav P.

10:00

Torsdag 26. februar 2009 10:05:04 skrev Jannick Kuhr:

...

2009/2/23 Karl Eichwalder :

...
To avoid a fork-like product, it is desirable to align translations as close as possible. =A0It would be great if you could make use of SLE 11 translations, as vice versa SLE translators are encouraged to make use of openSUSE translations.

Could you tell me when and why these SLE translations have been created? In many files, especially files we (the german team) have proof read before the 11.1 release are very different (70%?). Many changes/improvements (conformity with Gnome/KDE!) are reverted, other strings are just translated differently - not better not worse. Of course some typos have been fixed, others been introduced. But in general I would say that at least our files recently proofread before the 11.1 release are better. I have the impression that for at least some files SLE did not make any use of our translations or real fork happened a long time ago. For example the installation.de.po from openSUSE is almost an other translation. There are only few strings the same and our openSUSE translations are absolutely ok. There was no reason to change almost every string and/or revert improvements made by the openSUSE team in the past. I am a bit angry about this situation and I don't understand why openSUSE should have a community based team, if there also payed translators working independently from us. I don't really understand why I should spend rare time in translating and improving translations for openSUSE, if S.u.S.E. has it's own teams... Sorry.

Kind regards, Jannick Kuhr (German OpenSUSE and KDE translation team)

I have not checked my language very recently, but I can relate to this from past experiences. It is indeed quite annoying to fix bad translations (which I suspect comes from the SLES/SLED process), only to have the the same bad translations reintroduced before the next translation round. Olav (nb) -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

Carlos E. R.

12:54

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2009-02-26 at 11:00 +0100, Olav P. wrote:

...

Torsdag 26. februar 2009 10:05:04 skrev Jannick Kuhr:

...
2009/2/23 Karl Eichwalder :

...
To avoid a fork-like product, it is desirable to align translations as close as possible. =A0It would be great if you could make use of SLE 11 translations, as vice versa SLE translators are encouraged to make use of openSUSE translations.

Could you tell me when and why these SLE translations have been created? In many files, especially files we (the german team) have proof read before the 11.1 release are very different (70%?). Many changes/improvements (conformity with Gnome/KDE!) are reverted, other strings are just translated differently - not better not worse. Of course some typos have been fixed, others been introduced. But in general I would say that at least our files recently proofread before the 11.1 release are better. I have the impression that for at least some files SLE did not make any use of our translations or real fork happened a long time ago. For example the installation.de.po from openSUSE is almost an other translation. There are only few strings the same and our openSUSE translations are absolutely ok. There was no reason to change almost every string and/or revert improvements made by the openSUSE team in the past. I am a bit angry about this situation and I don't understand why openSUSE should have a community based team, if there also payed translators working independently from us. I don't really understand why I should spend rare time in translating and improving translations for openSUSE, if S.u.S.E. has it's own teams... Sorry.

Kind regards, Jannick Kuhr (German OpenSUSE and KDE translation team)

I have not checked my language very recently, but I can relate to this from past experiences.

It is indeed quite annoying to fix bad translations (which I suspect comes from the SLES/SLED process), only to have the the same bad translations reintroduced before the next translation round.

I still haven't had time to do any verification, the script seems very arduous to use; and as I can't use 11.1, I can't try the "lokalize" trick, which I think would be neat. I'm not aware that any of the Spanish team has been able to do any checking yet. But from past experiences I fear I will not like the SLE translation. And I must say that if I can finally do any review, I'm 95% sure I will prefer the openSUSE translation to the SLE translation. Why? Because we took our time to do it, to dicusse terminology on our mail list, to check what other upstream translators use, etc. We are not professionals, but we took a lot of care. And we haven't seen the SLE translators asking us why we decided to translate that way and not the other, participating, or offering conseil. No, I will not take their changes unless argued that their choice is more correct than ours. Not unless I see clearly that we made a mistake. I don't speak for my entire team (Spanish), of course, but I have the feeling they think around these lines, too. Sorry. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmmkPYACgkQtTMYHG2NR9UR4wCcCHjsA/rG7W7cz46dUesxKLMH LHwAn1vDjRbZ3XLB0NlFKN0uXpPHh+PD =CNwl -----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 Mar 2 Mar

14:04

"Olav P." writes:

...

Torsdag 26. februar 2009 10:05:04 skrev Jannick Kuhr:

...

...
Could you tell me when and why these SLE translations have been created? In many files, especially files we (the german team) have proof read before the 11.1 release are very different (70%?). Many changes/improvements (conformity with Gnome/KDE!) are reverted, other strings are just translated differently - not better not worse.

No, nothing got reverted. SLE11 translations are based on the approved SLE10 SP2 translations plus new translations. These new translations are either done from scratch or based on openSUSE or upstream translations.

...

...
Of course some typos have been fixed, others been introduced. But in general I would say that at least our files recently proofread before the 11.1 release are better. I have the impression that for at least some files SLE did not make any use of our translations or real fork happened a long time ago.

Some of the 11.1 translations were done "too late". For example, even shortly before GA the German openSUSE translations were rather mixed and thus we have had to use the SLE10 SP2 translations as the basis.

...

I have not checked my language very recently, but I can relate to this from past experiences.

I admit that in the past SLE translations surfaced in the openSUSE world via the memory files, but we never exchanged existing translations directly or intentionally. Lately, I stopped adding translations from the SLE branches to the memory files of the trunk.

...

It is indeed quite annoying to fix bad translations (which I suspect comes from the SLES/SLED process), only to have the the same bad translations reintroduced before the next translation round.

Please check whether this actually happened in the trunk of the SVN. Maybe, something weird happened by accident. Otherwise it would help a lot if you create a bug entry telling us which messages you have had to fix. -- 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.

16:09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2009-03-02 at 15:04 +0100, Karl Eichwalder wrote:

...

...
It is indeed quite annoying to fix bad translations (which I suspect comes from the SLES/SLED process), only to have the the same bad translations reintroduced before the next translation round.

Please check whether this actually happened in the trunk of the SVN. Maybe, something weird happened by accident. Otherwise it would help a lot if you create a bug entry telling us which messages you have had to fix.

I had a look at the zypper-1.0.5-2.1.2.src.rpm security update for openSUSE 11.0. Just open the es.po file, and you will see that it is the SLE version, not our trunk version. Yes, the openSUSE translation has been replaced with the SLE version. Not in our SVN, but directly in the rpm package. :-( - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmsBKoACgkQtTMYHG2NR9WgqQCdEAwe37DgpXyauOUmtY/WfDvk 0Z4An3TuU2CsMDZuGaYsJlAnxG6SLEsQ =NT31 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

Karl Eichwalder

16:30

Am Mon 02 Mar 2009 05:09:08 PM CET schrieb "Carlos E. R." :

...

I had a look at the zypper-1.0.5-2.1.2.src.rpm security update for openSUSE 11.0. Just open the es.po file, and you will see that it is the SLE version, not our trunk version.

I guess you mean 11.1. And yes, the zypper issue is very known and coolo already explained the details. It did not happen intentionally and we are about to provide a fix--which in some cases replaces completely translated SLE files with imcompletely translated openSUSE files ;-(

...

Yes, the openSUSE translation has been replaced with the SLE version. Not in our SVN, but directly in the rpm package. :-(

This time I was interested in SVN examples because there are complaints that are not proofed thus far. Cheers, Karl -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org

Carlos E. R.

21:37

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2009-03-02 at 17:30 +0100, Karl Eichwalder wrote:

...

Am Mon 02 Mar 2009 05:09:08 PM CET schrieb "Carlos E. R." <>:

...
I had a look at the zypper-1.0.5-2.1.2.src.rpm security update for openSUSE 11.0. Just open the es.po file, and you will see that it is the SLE version, not our trunk version.

I guess you mean 11.1.

Yes, sorry.

...

And yes, the zypper issue is very known and coolo already explained the details. It did not happen intentionally and we are about to provide a fix--which in some cases replaces completely translated SLE files with imcompletely translated openSUSE files ;-(

That's bad. You should ask the teams affected what to do in those cases, something like importing messages. As for Spanish, I know it is fully translated.

...

...
Yes, the openSUSE translation has been replaced with the SLE version. Not in our SVN, but directly in the rpm package. :-(

This time I was interested in SVN examples because there are complaints that are not proofed thus far.

I have only investigated one package, the zypper one. I'm not aware of more, but I could download more rpms and investigate. It is tedious, though. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmsUYQACgkQtTMYHG2NR9WjQwCeKaTHa0Lpj7VWxgJGt4yweeWu CUEAnjvR24BKzc6L05seU1mBeHfLYgHg =y78z -----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 Mar 9 Mar

10:28

Karl Eichwalder writes:

...

There is an experimental merge script in the yast directory of the trunk:

50-tools/y2-merge-from-dir.sh

With .../branches/SLE11/yast checked out, use it as follows:

cd .../trunk/yast 50-tools/y2-merge-from-dir.sh -f ../../branches/SLE11/yast -s -l de

With -f you point to the translations of the branch; -s means, merge file by file (single), and -l denotes the language.

Once done, you will see fuzzy entries auch as:

#: data/country.ycp:31 data/country_long.ycp:36 #, fuzzy msgid "Czech Republic" msgstr "" "#-#-#-#-# base.de.po (base) #-#-#-#-#\n" "Tschechien\n" "#-#-#-#-# base.de.po (base.de) #-#-#-#-#\n" "Tschechische Republik"

Maybe, I should have mentioned that this applies for the very first message (the header) of every PO file, too. This means once done you must also remove the fuzzy flag from the PO file header.

...

The first variant comes from the SLE11 branch and the second is the openSUSE variant. Resolve this fuzzy as every other fuzzy message. I'd appreciate feedback. Maybe, there are better ways :-)

-- 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

5528

Age (days ago)

5542

Last active (days ago)

List overview

Download

19 comments

8 participants

participants (8)

Andrea Florio
Carlos E. R.
Freek de Kruijf
Jannick Kuhr
Karl Eichwalder
Michael Skiba
Olav P.
Shane Wims