February 2009 - openSUSE Translation - openSUSE Mailing Lists

[opensuse-translation] important change for desktop files
by Stephan Kulow 16 Mar '09

16 Mar '09

Hi, Since 2008-11-19 we were prefering the translations in SVN over those in our packages after (as far as my memory) complaints from italian team. Since Factory is open again and sees new upstream texts, we also kept old translations alive. So I had to change this back, but I wondered what to do with the conflicts that happen between upstream and our teams. So I create now an extra update-desktop-files-conflicts.*.po file that will only contain comments, but gives you a chance to review style differences between upstream/package translations and yours. So it looks e.g. like this: #, fuzzy #~ msgctxt "Comment(digikamimageplugin_whitebalance.desktop)" #~ msgid "White balance correction plugin for digiKam" #~ msgstr "" #~ "Packages:\n" #~ "Estensione di digiKam per la correzione del bilanciamento del bianco\n" #~ "SVN:\n" #~ "Plugin di correzione del bilanciamento del bianco per digiKam" I guess somewhen around 11.2 release we'll either switch back the default to give teams a way to fix bugs that aren't overwritten by outdated package translations. Or we find a way to overwrite specific translations, but I see no good way atm. Till then: if you find a bug in the desktop files: let upstream know. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-translation+help(a)opensuse.org

2 3

[opensuse-translation] Before starting with 11.2 translations
by Karl Eichwalder 09 Mar '09

09 Mar '09

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(a)opensuse.org For additional commands, e-mail: opensuse-translation+help(a)opensuse.org

8 19

[opensuse-translation] zypper in openSUSE using SLED translations instead of openSUSE ones
by Luiz Fernando Ranghetti 02 Mar '09

02 Mar '09

Hi Karl and all! I noted that the zypper in the update repository uses SLED translations instead of the one we do. I find it while using zypper, a saw that the message who appears in the screen was differente than the one I translate (and had a typo in pt_BR :-) zypp.pt_BR: * original string: Retrieving repository '%s' metadata * SLED: Recuperandoos metadados do repositório '%s' (Should be >> "Recuperando os..") * openSUSE: Obtendo os metadados do repositório '%s' The sentences are equivalent, no problem there, the problem is that this string is translated for openSUSE so why use the SLED version? Regards. Luiz -- To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-translation+help(a)opensuse.org

11 14

[opensuse-translation] OpenSUSE vs. openSUSE (Request for clarification)
by Michael Skiba 27 Feb '09

27 Feb '09

Hello everyone, I was wondering about the string in add-on-creator.po, which says "OpenSUSE" (instead of openSUSE, with a small o). I think it stands at the beginning of a sentencen or is a headline or something where you'd usually write the first latter capitalized. But does this rule apply to openSUSE as well? I always thought it's a name and therefore should be always written with a lowercase o. If've added this as a bug in bugzilla, as I think it's simply the string that is wrong. Regards Michael

6 7

[opensuse-translation] OpenSUSE vs. openSUSE (Request for clarification)
by giuseppe gran 26 Feb '09

26 Feb '09

Ops... i always put the O (uppercase) in sign of respect to the Community, so is it an error? -- Linux user number 433087 Linux registered machine number 351448 http://counter.li.org/ -- To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-translation+help(a)opensuse.org

1 0

[opensuse-translation] Merging lcn files
by Karl Eichwalder 25 Feb '09

25 Feb '09

Maybe, you already noticed that there were activities in the lcn part of the suse-i18n SVN repository. Last week I asked the program maintainers to update or remove their POT files as appropriate. Some of them already took a look. I added the --previous option to the msgmerge command and would like to give it a try. Tomorrow I'd like to do a full merge--please, report any problem. For those who are new or not that familiar with the gettext tools: The --previous option was discussed some months ago. If a fuzzy match occurs, the previous msgid is preserved in a special comment (#|) and some tools (or is it lokalize only?) can make use of this special comment. This way you can quickly see what actually has changed in a msgid and updating a longish translation is not that cumbersome. Anyway, if you have changes pending, please commit them within the next 12 hours. If this is not possible, I'll run an additional merge tomorrow in the evening (CET). -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-translation+help(a)opensuse.org

2 2

[opensuse-translation] openSUSE-11_1-Branch and forthcoming online update
by Karl Eichwalder 23 Feb '09

23 Feb '09

I just created https://forgesvn1.novell.com/svn/suse-i18n/branches/openSUSE-11_1-Branch and now I'm about to prepare the online update from it. The online update will address the following languages (for these languages I detected changes since GA--please complain, if I missed some bits): yast: ==== be cs da de el es fi fr gl hr hu it ja ka km ko ku nb nl pl pt ro ru uk pt_BR lcn: ==== cs da de es fi fr gl hr hu it ja ka km ko nb nl pl pt ro ru uk pt_BR This is the main bug entry to be covered with the forthcoming update: https://bugzilla.novell.com/show_bug.cgi?id=464470 This also means that "trunk" is now open for 11.2 changes. -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-translation+help(a)opensuse.org

8 13

[opensuse-translation] Can't access svn
by Gabriel 20 Feb '09

20 Feb '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Karl, I'm getting the following error while trying to access the svn through webdav and apache (https://forgesvn1.novell.com/svn/suse-i18n/branches/openSUSE-11_1-Branch) errcode=13 "Could not open the requested SVN filesystem" Maybe related to SELinux (http://subversion.tigris.org/faq.html#reposperms) - -- Kind regards. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEAREIAAYFAkmcs9MACgkQNHr4BkRe3pIXvwCfQJaQzPHSB2tRy985GNiM3ifB QhcAniyG1xd0SRSOi/K00bVbhdD4btKv =11Jc -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-translation+help(a)opensuse.org

4 9

[opensuse-translation] ukrainian translation
by Сергій Дмитришин 08 Feb '09

08 Feb '09

Hello there, I would like to be involved in translation and send appropriate e-mail to Ukrainian team but not success Simply they don't response for me what can I do to take part ? Actually I'm student from Ukraine Thank you, Sergey -- To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-translation+help(a)opensuse.org

2 1

[opensuse-translation] RELEASE-NOTES for 11.1
by Karl Eichwalder 06 Feb '09

06 Feb '09

Because of https://bugzilla.novell.com/show_bug.cgi?id=468853, the RELEASE-NOTES file is now available for translation again. Next week (Wednesday), I'd like to publish an online update. -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-translation+help(a)opensuse.org

2 2