- openSUSE Translation

[opensuse-translation] Thruth likes to join the Chinese Simplefied Translation Team
by Truth 30 Jul '07

30 Jul '07

Hi all, I'd like to join the Chinese Simplefied Translation Team. Chinese Simplified translations for openSUSE are currently handled by Novell Language Service and the translation process is not open. Actually I've been doing suse related tanslation for some time. I've been building packages ,in the build service, with self-made Chinese translation patches patched. I am a beryl(now compiz fusion) translator and I fixed YaST Chinese typo mistakes (the package in in my repo). I wish I could participate futher in the translation process and help. Regards, Thruth --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-translation+help(a)opensuse.org

3 2

[opensuse-translation] Italian translations
by Alberto Passalacqua 30 Jul '07

30 Jul '07

Hello, I'm an Italian guy and I would like to give some help with the Italian translations. Who is part of the translation team? How can I join it? With kind regards, Alberto --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-translation+help(a)opensuse.org

3 2

[opensuse-translation] I like to join the Italian translation team
by Francesco Raffaele Pastore 29 Jul '07

29 Jul '07

Hi, I'm italian and I want to join the Italian translation team. Regards, Francesco. --------------------------------------------------------------------- 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] I want to join Traditional Chinese translation team
by chen swyear 28 Jul '07

28 Jul '07

Hi I'm swyear, I think I can do some help about Traditional Chinese translation I had translated smart ( http://labix.org/smart ) into Traditional Chinese and I am now working for Traditional Chinese wiki ( http://zh_tw.opensuse.org Not public announced yet!) Best Regards swyear --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-translation+help(a)opensuse.org

1 0

Re: [opensuse-translation] OpenSUSE 10.3 - 1st translation round starts
by aliks-os 27 Jul '07

27 Jul '07

Well, my opinion that variant b) is more acceptable for us, reason: >some words that are translated > differently in different contexts will look silly >(e.g. "volume" can refer > to sound or disk-related stuff requiring very different >translation). Other ideas: First, In the memory a lot of such situation as above (in any case were a lot of), during last period, these messages were fixed in the trunk. Sometime, during the merging from the memory, we had in the trunk strings, which marked as good but really with the mistakes. Next, at the current time, we have trunk fully (98%) corrected. We do this job since suse 10.0, each next version (I mean translation) more better. And, if we will following variant c), we may damage our work in the trunk. At the past (mostly during translation version 10.2), I often have the following situation: grand update of trunk from translators side, a lot of strings corrected. Next round come or next merging occurs in the trunk, we have new strings for translating, and all old strings which were corrected and updated in trunk still present here as untouched (I mean as not corrected)!!! Several times I have shock. Karl do for me rollback. So, before merging, memory was not updated from trunk??? During the current round (version 10.3) situation more better, above situation never occur (and hope never will). So, according above mentioned, I suggest the following: 1. Clean up current memory 2. Build new memory on base of the current trunk 3. New strings put in the trunk from memory marked only as fuzzy 4. The very new string, which are comes from developers, search in the memory, a) if the result of searching by words more than 80%, mark as fuzzy; b) if less not take translation from memory at all; c) never mark as translated. 5. Simultaneously, put new messages in the trunk for translation, with the marks fuzzy or not translated, see item 4; 6. More often update memory from the trunk, as trunk is continuously updated by translators. 7. And last. I’d like ask developers, I mean programmers, put more comments for translating of the strings. Sometimes, very difficult to define true meaning of the string. Kindly regards Aleksey Osipov 26.07.07, 16:00, Nikolay Derkach <nderkach(a)gmail.com>: > В сообщении от Thursday 26 July 2007 15:41:16 Martin Schlander написал(а): > > > I completely agree with you that that's dangerous and I sure I can > > > improve the process for > 10.3. > > > > It's a difficult situation.. > > > > a) not using memory: > > Means a lot of extra work. > > > > b) marking all memory stuff fuzzy > > Means quite some extra work - apart from not being an option for 10.3 > > > > c) using the memory unconditionally > > Means poor quality by reproducing errors of the past, not complying with > > current translation team "standards", and some words that are translated > > differently in different contexts will look silly (e.g. "volume" can refer > > to sound or disk-related stuff requiring very different translation). This > > either means a lot less work and acceptance of poor quality. Or it means > > you have to proofread everything after the last merge for every release, > > which would mean an extreme amount of work, with short time to do it. > > > > I think we (read: you guys) should strive for giving teams an option > > between b) and c) in the future. > > > > Apart from pl answering here to the list, I've had discussions with fi and > > ru on IRC - they seem to be slightly worried about the issue, but > > nevertheless it seems they prefer c) > > > > > I'd propose to merge the files on your own, ignoring the memories. > > > > We've already done a lot of work since the merge, I don't want to mess with > > it. Primarily worried about the future. > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org > > For additional commands, e-mail: opensuse-translation+help(a)opensuse.org > I personally vore for variant b), maybe you have missunderstood me. > Proof reading additional fuzzy lines is not much work but leads to better > quallity. > Since memory strings are mostly correct this won't cause much of work. > I'm not able to decide for our team, have to ask our coordinator. -- Яндекс.Фотки - заливай свои, любуйся чужими! http://fotki.yandex.ru/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-translation+help(a)opensuse.org

3 2

[opensuse-translation] Want to join the Norwegian language team
by Rune Nordbøe Skillingstad 25 Jul '07

25 Jul '07

Hello, my name is Rune Nordbøe Skillingstad, and have started to translate some of the missing parts of the Norwegian language. I've had a dialog with Olav Pettershaugen and agreed on a roadmap to get the Norwegian translation ready to 10.3. To coordinate this, I would like to have my SVN account enabled. I have a Novell account (username runesk) and have accessed my "user page" (http://developer.novell.com/wiki/index.php/User:Runesk) Cheers, Rune Nordbøe Skillingstad --------------------------------------------------------------------- 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] Re: [Suse-i18n-dev] Updating translation files (.po)
by Karl Eichwalder 20 Jul '07

20 Jul '07

Andreas Jaeger <aj(a)suse.de> writes: >> web-updater.pot: "POT-Creation-Date: 2006-02-10 11:40+0100\n" > > Remove web-updater! > >> kpowersave.pot: "POT-Creation-Date: 2006-03-14 00:16+0100\n" >> kinternet.pot: "POT-Creation-Date: 2006-06-08 12:58+0200\n" >> kfiledialog.pot: "POT-Creation-Date: 2006-09-14 17:19+0200\n" >> suseplugger.pot: "POT-Creation-Date: 2006-09-14 17:19+0200\n" > > I think suseplugger is obsolete - remove it. Thanks for the info! I'm going to remove the files soon. >> RELEASE-NOTES.pot: "POT-Creation-Date: 2006-12-08 15:41+0100\n" > > Karl, release notes is your job ;-) Release notes are special -- I could have sworn having replaced the file already... ;-( Ignore RELEASE-NOTES for the moment. The new file is mostly empty, and we will start with it later (2nd translation round). -- 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

1 0

[opensuse-translation] update-desktop-files problem
by Martin Schlander 17 Jul '07

17 Jul '07

I'm wondering what has happened to our update-desktop-files.da.po I guess some merging/scripting has gone horribly wrong. It says last revision 2005-08-16 by Martin Møller and all the work we did on it for 10.2 is lost... which also explains why it looks so horrible in 10.3a5. Would it be fixable somehow? It's of course a huge file and we're talking many hours of work. I have here locally a backup of the last known good version of it that I made on april 23 before the Novell-translations were merged. In general can we expect translations to not be broken when they undergo this treatment? Many files in lcn have strange revision dates and translators - like "Novell Language, 2002". Is it safe to assume that our previous translations are intact in such files, so we can focus on "untranslated" and "fuzzy" or do we need to proofread the entire files to be safe? --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-translation+help(a)opensuse.org

3 12

[opensuse-translation] Stat-page issues
by Martin Schlander 16 Jul '07

16 Jul '07

There's a problem with the stats page. It seems to believe that the update-desktop-files.po has a syntax error - this is the same for all languages (or at least the 3-4 languages that I checked) However kbabel verifies the syntax as correct. Therefore I assume it's just a stat-page problem, and that there's actually nothing wrong with the file. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-translation+help(a)opensuse.org

2 2

Re: [opensuse-translation] OpenSUSE 10.3?
by Martin Schlander 11 Jul '07

11 Jul '07

Den Wednesday 11 July 2007 13:38:22 skrev du: > And the general procedure is to translate the lcn an yast folders, commit > and be happy. No changes there, right? Yup. Apparently if you translate enough of the packages descriptions they'll get included. And there are now different branches in svn.. 10.2, SLED SP1-stuff and trunk.. remember to use trunk. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-translation+help(a)opensuse.org

1 0