From onur at pardus.org.tr Fri Jan 8 22:12:24 2010 From: onur at pardus.org.tr (Onur =?UTF-8?B?S8O8w6fDvGs=?=) Date: Fri, 8 Jan 2010 22:12:24 +0200 Subject: [Pardus-translators] 2009.1 RC is ready Message-ID: <20100108221224.2ce9a805.onur@pardus.org.tr> Hello, Release candidate of 2009.1 is placed in the ftp servers. Starting with this release we are using hybrid ISO system. I have placed a text file explaining how to use it near the ISO files. Thanks to all that have contributed :) -- Onur K???k Knowledge speaks, but wisdom listens From patrik at pardus.nu Sat Jan 9 20:36:53 2010 From: patrik at pardus.nu (Patrik Karlsson) Date: Sat, 9 Jan 2010 19:36:53 +0100 Subject: [Pardus-translators] Translating (yes/no) in pisi In-Reply-To: <200912281853.27472.patrik@pardus.nu> References: <200912281853.27472.patrik@pardus.nu> Message-ID: <201001091936.53581.patrik@pardus.nu> m?ndagen den 28 december 2009 18.53.27 skrev Patrik Karlsson: > How should I translate the (yes/no) string in pisi? > Do you use the same translation to validate the input? So, can I translate this message? From atolboo at gmail.com Sat Jan 9 22:10:53 2010 From: atolboo at gmail.com (Antoon Tolboom) Date: Sat, 9 Jan 2010 21:10:53 +0100 Subject: [Pardus-translators] Translating (yes/no) in pisi In-Reply-To: <201001091936.53581.patrik@pardus.nu> References: <200912281853.27472.patrik@pardus.nu> <201001091936.53581.patrik@pardus.nu> Message-ID: <201001092110.53771.atolboo@gmail.com> On Saturday 09 January 2010 19:36:53 Patrik Karlsson wrote: > m?ndagen den 28 december 2009 18.53.27 skrev Patrik Karlsson: > > How should I translate the (yes/no) string in pisi? > > Do you use the same translation to validate the input? > > So, can I translate this message? This question isn't very clear te me! Translate which string in pisi? Translate into what language? Could you give a better discription? regards, Antoon Tolboom From patrik at pardus.nu Sat Jan 9 23:08:58 2010 From: patrik at pardus.nu (Patrik Karlsson) Date: Sat, 9 Jan 2010 22:08:58 +0100 Subject: [Pardus-translators] Translating (yes/no) in pisi In-Reply-To: <201001092110.53771.atolboo@gmail.com> References: <200912281853.27472.patrik@pardus.nu> <201001091936.53581.patrik@pardus.nu> <201001092110.53771.atolboo@gmail.com> Message-ID: <201001092208.58457.patrik@pardus.nu> l?rdagen den 9 januari 2010 21.10.53 skrev Antoon Tolboom: > This question isn't very clear te me! > > Translate which string in pisi? > Translate into what language? > Could you give a better discription? The string is: #: pisi/cli/__init__.py:119 msgid " (yes/no)" and looking at the code yesexpr = re.compile(locale.nl_langinfo(locale.YESEXPR)) tty.tcflush(sys.stdin.fileno(), 0) prompt = msg + pisi.util.colorize(_(' (yes/no)'), 'red') s = raw_input(prompt.encode('utf-8')) if yesexpr.search(s): return True return False I would say that it is safe to translate it, but I dont know much about python. From atolboo at gmail.com Sat Jan 9 23:26:43 2010 From: atolboo at gmail.com (Antoon Tolboom) Date: Sat, 9 Jan 2010 22:26:43 +0100 Subject: [Pardus-translators] Translating (yes/no) in pisi In-Reply-To: <201001092208.58457.patrik@pardus.nu> References: <200912281853.27472.patrik@pardus.nu> <201001092110.53771.atolboo@gmail.com> <201001092208.58457.patrik@pardus.nu> Message-ID: <201001092226.43372.atolboo@gmail.com> On Saturday 09 January 2010 22:08:58 Patrik Karlsson wrote: > l?rdagen den 9 januari 2010 21.10.53 skrev Antoon Tolboom: > > This question isn't very clear te me! > > > > Translate which string in pisi? > > Translate into what language? > > Could you give a better discription? > > The string is: > > #: pisi/cli/__init__.py:119 > msgid " (yes/no)" > > and looking at the code > yesexpr = re.compile(locale.nl_langinfo(locale.YESEXPR)) > > tty.tcflush(sys.stdin.fileno(), 0) > prompt = msg + pisi.util.colorize(_(' (yes/no)'), 'red') > s = raw_input(prompt.encode('utf-8')) > if yesexpr.search(s): > return True > > return False > > I would say that it is safe to translate it, but I dont know much about > python. I don't know but to give a better judgement. Where in http://svn.pardus.org.tr/uludag/trunk/ does this string comes from? regards, Antoon Tolboom From patrik at pardus.nu Sun Jan 10 13:15:07 2010 From: patrik at pardus.nu (Patrik Karlsson) Date: Sun, 10 Jan 2010 12:15:07 +0100 Subject: [Pardus-translators] Release notes 2009.1 Message-ID: <201001101215.07273.patrik@pardus.nu> Will you just change the versions from the 2009 release notes for 2009.1 or do we have to make a new translation? If so, where can we find it and when can we/do we have to do it? From necmettin.begiter at gmail.com Sun Jan 10 15:12:45 2010 From: necmettin.begiter at gmail.com (Necmettin Begiter) Date: Sun, 10 Jan 2010 15:12:45 +0200 Subject: [Pardus-translators] Release notes 2009.1 In-Reply-To: <201001101215.07273.patrik@pardus.nu> References: <201001101215.07273.patrik@pardus.nu> Message-ID: <3787dfa81001100512q3b4ef942q56c303e4269cf5f0@mail.gmail.com> On Sun, Jan 10, 2010 at 13:15, Patrik Karlsson wrote: > Will you just change the versions from the 2009 release notes for 2009.1 or do > we have to make a new translation? If so, where can we find it and when can > we/do we have to do it? It will be announced as here as usual. I'm guessing not much change will be needed. From patrik at pardus.nu Sun Jan 10 15:31:24 2010 From: patrik at pardus.nu (Patrik Karlsson) Date: Sun, 10 Jan 2010 14:31:24 +0100 Subject: [Pardus-translators] Swedish pspec-translations Message-ID: <201001101431.25057.patrik@pardus.nu> Can someone add sv to the scripts in trunk/scripts/pspec-translations and generate a sv.po or do I do it by myself? From onur at pardus.org.tr Sun Jan 10 16:33:43 2010 From: onur at pardus.org.tr (Onur =?UTF-8?B?S8O8w6fDvGs=?=) Date: Sun, 10 Jan 2010 16:33:43 +0200 Subject: [Pardus-translators] Translating (yes/no) in pisi In-Reply-To: <201001092208.58457.patrik@pardus.nu> References: <200912281853.27472.patrik@pardus.nu> <201001091936.53581.patrik@pardus.nu> <201001092110.53771.atolboo@gmail.com> <201001092208.58457.patrik@pardus.nu> Message-ID: <20100110163343.b5ab5a7b.onur@pardus.org.tr> On Sat, 9 Jan 2010 22:08:58 +0100 Patrik Karlsson wrote: > l?rdagen den 9 januari 2010 21.10.53 skrev Antoon Tolboom: > #: pisi/cli/__init__.py:119 > msgid " (yes/no)" > > and looking at the code > yesexpr = re.compile(locale.nl_langinfo(locale.YESEXPR)) this part gets the "yes" and "no" parts from locale so that they will work in different locales too. For example in Turkish, yes is "evet" and no is "hay?r", so to accept the action pressing "e" works in Turkish. > I would say that it is safe to translate it, but I dont know much > about python. Yeap you are right, it is safe to translate -- Onur K???k Knowledge speaks, but wisdom listens From onur at pardus.org.tr Sun Jan 10 16:36:13 2010 From: onur at pardus.org.tr (Onur =?UTF-8?B?S8O8w6fDvGs=?=) Date: Sun, 10 Jan 2010 16:36:13 +0200 Subject: [Pardus-translators] test mail Message-ID: <20100110163613.5beaa85d.onur@pardus.org.tr> Ignore -- Onur K???k Knowledge speaks, but wisdom listens From onur at pardus.org.tr Sun Jan 10 16:40:13 2010 From: onur at pardus.org.tr (Onur =?UTF-8?B?S8O8w6fDvGs=?=) Date: Sun, 10 Jan 2010 16:40:13 +0200 Subject: [Pardus-translators] test mail In-Reply-To: <20100110163613.5beaa85d.onur@pardus.org.tr> References: <20100110163613.5beaa85d.onur@pardus.org.tr> Message-ID: <20100110164013.d8b8fcac.onur@pardus.org.tr> liam tset -- Onur K???k Knowledge speaks, but wisdom listens From onur at pardus.org.tr Sun Jan 10 16:40:54 2010 From: onur at pardus.org.tr (Onur =?UTF-8?B?S8O8w6fDvGs=?=) Date: Sun, 10 Jan 2010 16:40:54 +0200 Subject: [Pardus-translators] test mail In-Reply-To: <20100110164013.d8b8fcac.onur@pardus.org.tr> References: <20100110163613.5beaa85d.onur@pardus.org.tr> <20100110164013.d8b8fcac.onur@pardus.org.tr> Message-ID: <20100110164054.641ca7a6.onur@pardus.org.tr> I have fixed the reply-to header in list regards, -- Onur K???k Knowledge speaks, but wisdom listens From onur at pardus.org.tr Sun Jan 10 16:47:25 2010 From: onur at pardus.org.tr (Onur =?UTF-8?B?S8O8w6fDvGs=?=) Date: Sun, 10 Jan 2010 16:47:25 +0200 Subject: [Pardus-translators] Release notes 2009.1 In-Reply-To: <201001101215.07273.patrik@pardus.nu> References: <201001101215.07273.patrik@pardus.nu> Message-ID: <20100110164725.8def3352.onur@pardus.org.tr> On Sun, 10 Jan 2010 12:15:07 +0100 Patrik Karlsson wrote: > Will you just change the versions from the 2009 release notes for > 2009.1 or do we have to make a new translation? If so, where can we > find it and when can we/do we have to do it? Eh I was late for the release notes because of other stuff, sorry, the original plan was to finalize it on friday. I am planning to add some changes (a few about KDE, new drivers, and Hybrid), will do them today and tomorrow and try to finish before monday night, let us make the deadline for the main notes tuesday night (I will inform here if I can finish before then), and translations to be finished by thursday morning. Are these timelines ok ? ps: I am thinking of timelines due to GMT+2 -- Onur K???k Knowledge speaks, but wisdom listens From philsvet at gmail.com Sun Jan 10 16:54:20 2010 From: philsvet at gmail.com (Philippe Svetoslavsky) Date: Sun, 10 Jan 2010 15:54:20 +0100 Subject: [Pardus-translators] Release notes 2009.1 In-Reply-To: <20100110164725.8def3352.onur@pardus.org.tr> References: <201001101215.07273.patrik@pardus.nu> <20100110164725.8def3352.onur@pardus.org.tr> Message-ID: OK for me. 2010/1/10 Onur K???k > > On Sun, 10 Jan 2010 12:15:07 +0100 > Patrik Karlsson wrote: > > > Will you just change the versions from the 2009 release notes for > > 2009.1 or do we have to make a new translation? If so, where can we > > find it and when can we/do we have to do it? > > Eh I was late for the release notes because of other stuff, sorry, the > original plan was to finalize it on friday. > > I am planning to add some changes (a few about KDE, new drivers, > and Hybrid), will do them today and tomorrow and try to finish before > monday night, let us make the deadline for the main notes tuesday > night (I will inform here if I can finish before then), and translations > to be finished by thursday morning. > > Are these timelines ok ? > > ps: I am thinking of timelines due to GMT+2 > > -- > Onur K???k Knowledge speaks, > but wisdom listens > > _______________________________________________ > Pardus-translators mailing list > Pardus-translators at pardus.org.tr > http://liste.pardus.org.tr/mailman/listinfo/pardus-translators > -------------- next part -------------- An HTML attachment was scrubbed... URL: From atolboo at gmail.com Sun Jan 10 18:06:45 2010 From: atolboo at gmail.com (Antoon Tolboom) Date: Sun, 10 Jan 2010 17:06:45 +0100 Subject: [Pardus-translators] English strings in Dutch version of P2009.1RC Message-ID: <201001101706.45495.atolboo@gmail.com> Have a look in http://bugs.pardus.org.tr/show_bug.cgi?id=11219#c11 for details Can anybody tell me what I can do to solve this problem. Thanks. regards, Antoon Tolboom From atolboo at gmail.com Mon Jan 11 16:42:05 2010 From: atolboo at gmail.com (Antoon Tolboom) Date: Mon, 11 Jan 2010 15:42:05 +0100 Subject: [Pardus-translators] Release notes 2009.1 In-Reply-To: <20100110164725.8def3352.onur@pardus.org.tr> References: <201001101215.07273.patrik@pardus.nu> <20100110164725.8def3352.onur@pardus.org.tr> Message-ID: <201001111542.05853.atolboo@gmail.com> On Sunday 10 January 2010 15:47:25 Onur K???k wrote: > On Sun, 10 Jan 2010 12:15:07 +0100 > > Patrik Karlsson wrote: > > Will you just change the versions from the 2009 release notes for > > 2009.1 or do we have to make a new translation? If so, where can we > > find it and when can we/do we have to do it? > > Eh I was late for the release notes because of other stuff, sorry, the > original plan was to finalize it on friday. > > I am planning to add some changes (a few about KDE, new drivers, > and Hybrid), will do them today and tomorrow and try to finish before > monday night, let us make the deadline for the main notes tuesday > night (I will inform here if I can finish before then), and translations > to be finished by thursday morning. > > Are these timelines ok ? > > ps: I am thinking of timelines due to GMT+2 That's OK as far as I am concerned. regards, Antoon Tolboom From patrik at pardus.nu Mon Jan 11 20:28:51 2010 From: patrik at pardus.nu (Patrik Karlsson) Date: Mon, 11 Jan 2010 19:28:51 +0100 Subject: [Pardus-translators] Release notes 2009.1 In-Reply-To: <20100110164725.8def3352.onur@pardus.org.tr> References: <201001101215.07273.patrik@pardus.nu> <20100110164725.8def3352.onur@pardus.org.tr> Message-ID: <201001111928.51318.patrik@pardus.nu> s?ndagen den 10 januari 2010 15.47.25 skrev Onur K???k: > Are these timelines ok ? It's ok. From patrik at pardus.nu Mon Jan 11 20:30:04 2010 From: patrik at pardus.nu (Patrik Karlsson) Date: Mon, 11 Jan 2010 19:30:04 +0100 Subject: [Pardus-translators] Translating (yes/no) in pisi In-Reply-To: <20100110163343.b5ab5a7b.onur@pardus.org.tr> References: <200912281853.27472.patrik@pardus.nu> <201001092208.58457.patrik@pardus.nu> <20100110163343.b5ab5a7b.onur@pardus.org.tr> Message-ID: <201001111930.04853.patrik@pardus.nu> s?ndagen den 10 januari 2010 15.33.43 skrev Onur K???k: > Yeap you are right, it is safe to translate Great, thanks! From philsvet at gmail.com Mon Jan 11 22:00:20 2010 From: philsvet at gmail.com (Philippe Svetoslavsky) Date: Mon, 11 Jan 2010 21:00:20 +0100 Subject: [Pardus-translators] Panthera pardus tulliana Message-ID: Hello all, The Pardus 2009.1 release notes write "Panthera Pardus Tulliana" as the scientific name of the anatolian leopard. But the scientific latin denomination is to write "Panthera pardus tulliana". That is : the genus name always begins by an upper-case letter and the species name (or names) always by a lower-case letter. It's not of vital importance, but it's always better to write with the maximum of correctness, especially as science is concerned. I didn't edit the english release notes, but as far as the french release notes are concerned, it will be zoologically correct :) -------------- next part -------------- An HTML attachment was scrubbed... URL: From onur at pardus.org.tr Mon Jan 11 22:30:07 2010 From: onur at pardus.org.tr (Onur =?UTF-8?B?S8O8w6fDvGs=?=) Date: Mon, 11 Jan 2010 22:30:07 +0200 Subject: [Pardus-translators] Panthera pardus tulliana In-Reply-To: References: Message-ID: <20100111223007.d9a87499.onur@pardus.org.tr> On Mon, 11 Jan 2010 21:00:20 +0100 Philippe Svetoslavsky wrote: > Hello all, > > The Pardus 2009.1 release notes write "Panthera Pardus Tulliana" as > the scientific name of the anatolian leopard. But the scientific latin > denomination is to write "Panthera pardus tulliana". > That is : the genus name always begins by an upper-case letter and the > species name (or names) always by a lower-case letter. > > It's not of vital importance, but it's always better to write with the > maximum of correctness, especially as science is concerned. > I didn't edit the english release notes, but as far as the french > release notes are concerned, it will be zoologically correct :) I'll correct the English ones then, thanks :) -- Onur K???k Knowledge speaks, but wisdom listens From philsvet at gmail.com Tue Jan 12 20:40:35 2010 From: philsvet at gmail.com (Philippe Svetoslavsky) Date: Tue, 12 Jan 2010 19:40:35 +0100 Subject: [Pardus-translators] Localized Firefox bookmarks ? Message-ID: The Firefox bookmarks that come with Pardus are useless for a non english speaking user. Is there a way to have localized Firefox bookmarks ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From atolboo at gmail.com Tue Jan 12 21:40:26 2010 From: atolboo at gmail.com (Antoon Tolboom) Date: Tue, 12 Jan 2010 20:40:26 +0100 Subject: [Pardus-translators] Localized Firefox bookmarks ? In-Reply-To: References: Message-ID: <201001122040.26550.atolboo@gmail.com> On Tuesday 12 January 2010 19:40:35 Philippe Svetoslavsky wrote: > The Firefox bookmarks that come with Pardus are useless for a non english > speaking user. > Is there a way to have localized Firefox bookmarks ? On July 2009 they were in /devel/network/web/firefox/files/pardus/pardus_bookmark-xx.html as you can see in http://liste.pardus.org.tr/pardus-translators/2009-July/000404.html Maybe this will help in finding them at this moment. regards, Antoon Tolboom From onur at pardus.org.tr Tue Jan 12 22:03:06 2010 From: onur at pardus.org.tr (Onur =?UTF-8?B?S8O8w6fDvGs=?=) Date: Tue, 12 Jan 2010 22:03:06 +0200 Subject: [Pardus-translators] English strings in Dutch version of P2009.1RC In-Reply-To: <201001101706.45495.atolboo@gmail.com> References: <201001101706.45495.atolboo@gmail.com> Message-ID: <20100112220306.ce29bfcd.onur@pardus.org.tr> On Sun, 10 Jan 2010 17:06:45 +0100 Antoon Tolboom wrote: > Have a look in http://bugs.pardus.org.tr/show_bug.cgi?id=11219#c11 > for details Can anybody tell me what I can do to solve this problem. > Thanks. You had done your part, package maintainers should update their packages and get the translations in ! I will write a mail about this now to English and Turkish devel lists. -- Onur K???k Knowledge speaks, but wisdom listens From philsvet at gmail.com Tue Jan 12 22:21:43 2010 From: philsvet at gmail.com (Philippe Svetoslavsky) Date: Tue, 12 Jan 2010 21:21:43 +0100 Subject: [Pardus-translators] Localized Firefox bookmarks ? In-Reply-To: <201001122040.26550.atolboo@gmail.com> References: <201001122040.26550.atolboo@gmail.com> Message-ID: Thanks Antoon. It looks like I don't have the right to commit to pardus/2009/devel. Could someone please add and commit "pardus_bookmark-fr.html" for me in http://svn.pardus.org.tr/pardus/2009/devel/network/web/firefox/files/pardus/please ? This file is attached to this mail. 2010/1/12 Antoon Tolboom > On Tuesday 12 January 2010 19:40:35 Philippe Svetoslavsky wrote: > > The Firefox bookmarks that come with Pardus are useless for a non english > > speaking user. > > Is there a way to have localized Firefox bookmarks ? > > On July 2009 they were in > /devel/network/web/firefox/files/pardus/pardus_bookmark-xx.html > as you can see in > http://liste.pardus.org.tr/pardus-translators/2009-July/000404.html > Maybe this will help in finding them at this moment. > > regards, > Antoon Tolboom > > _______________________________________________ > Pardus-translators mailing list > Pardus-translators at pardus.org.tr > http://liste.pardus.org.tr/mailman/listinfo/pardus-translators > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: From atolboo at gmail.com Tue Jan 12 22:55:18 2010 From: atolboo at gmail.com (Antoon Tolboom) Date: Tue, 12 Jan 2010 21:55:18 +0100 Subject: [Pardus-translators] English strings in Dutch version of P2009.1RC In-Reply-To: <20100112220306.ce29bfcd.onur@pardus.org.tr> References: <201001101706.45495.atolboo@gmail.com> <20100112220306.ce29bfcd.onur@pardus.org.tr> Message-ID: <201001122155.18970.atolboo@gmail.com> On Tuesday 12 January 2010 21:03:06 Onur K???k wrote: > On Sun, 10 Jan 2010 17:06:45 +0100 > > Antoon Tolboom wrote: > > Have a look in http://bugs.pardus.org.tr/show_bug.cgi?id=11219#c11 > > for details Can anybody tell me what I can do to solve this problem. > > Thanks. > > You had done your part, package maintainers should update their > packages and get the translations in ! > > I will write a mail about this now to English and Turkish devel lists. THANKS. regards, Antoon Tolboom From sw1976de at googlemail.com Tue Jan 12 23:24:00 2010 From: sw1976de at googlemail.com (Stefan Wilhelm) Date: Tue, 12 Jan 2010 22:24:00 +0100 Subject: [Pardus-translators] English strings in Dutch version of P2009.1RC In-Reply-To: <201001122155.18970.atolboo@gmail.com> References: <201001101706.45495.atolboo@gmail.com> <20100112220306.ce29bfcd.onur@pardus.org.tr> <201001122155.18970.atolboo@gmail.com> Message-ID: @Onur: please note, that the german translations of these strings are also modified and should be implemented. thanks in advance an HAPPY NEW YEAR :-) regards, Stefan 2010/1/12 Antoon Tolboom > On Tuesday 12 January 2010 21:03:06 Onur K???k wrote: > > On Sun, 10 Jan 2010 17:06:45 +0100 > > > > Antoon Tolboom wrote: > > > Have a look in http://bugs.pardus.org.tr/show_bug.cgi?id=11219#c11 > > > for details Can anybody tell me what I can do to solve this problem. > > > Thanks. > > > > You had done your part, package maintainers should update their > > packages and get the translations in ! > > > > I will write a mail about this now to English and Turkish devel lists. > > THANKS. > > regards, > Antoon Tolboom > _______________________________________________ > Pardus-translators mailing list > Pardus-translators at pardus.org.tr > http://liste.pardus.org.tr/mailman/listinfo/pardus-translators > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mete at pardus.org.tr Wed Jan 13 15:55:33 2010 From: mete at pardus.org.tr (Mete Alpaslan) Date: Wed, 13 Jan 2010 15:55:33 +0200 Subject: [Pardus-translators] YALI & 2009.1 translations Message-ID: <201001131555.33383.mete@pardus.org.tr> Merhaba / Hello; Before 2009.1 release, I fixed some bugs and made translation changes in uludag/branches/yali/2009. Please look over YALI 2009 branch and update translations in your localization until tomorrow. Mete Alpaslan From tribunal2000 at gmail.com Wed Jan 13 16:01:06 2010 From: tribunal2000 at gmail.com (=?KOI8-R?B?7snLz8zByiDzxc3Fzs/X?=) Date: Wed, 13 Jan 2010 17:01:06 +0300 Subject: [Pardus-translators] YALI & 2009.1 translations In-Reply-To: <201001131555.33383.mete@pardus.org.tr> References: <201001131555.33383.mete@pardus.org.tr> Message-ID: <1919ab0a1001130601i3fe3fc57o2cfa8ebe60106e84@mail.gmail.com> Hi all! I'm one of translators of Yali (right now to russian). How can I update my ru.po file? Or Where can I find some info about it? With Best Regards, Nikolay Semenov 2010/1/13 Mete Alpaslan > Merhaba / Hello; > > Before 2009.1 release, I fixed some bugs and made translation changes in > uludag/branches/yali/2009. > > Please look over YALI 2009 branch and update translations in your > localization > until tomorrow. > > Mete Alpaslan > _______________________________________________ > Pardus-translators mailing list > Pardus-translators at pardus.org.tr > http://liste.pardus.org.tr/mailman/listinfo/pardus-translators > -------------- next part -------------- An HTML attachment was scrubbed... URL: From atolboo at gmail.com Wed Jan 13 18:25:52 2010 From: atolboo at gmail.com (Antoon Tolboom) Date: Wed, 13 Jan 2010 17:25:52 +0100 Subject: [Pardus-translators] YALI & 2009.1 translations In-Reply-To: <201001131555.33383.mete@pardus.org.tr> References: <201001131555.33383.mete@pardus.org.tr> Message-ID: <201001131725.52342.atolboo@gmail.com> On Wednesday 13 January 2010 14:55:33 Mete Alpaslan wrote: > Merhaba / Hello; > > Before 2009.1 release, I fixed some bugs and made translation changes in > uludag/branches/yali/2009. > > Please look over YALI 2009 branch and update translations in your > localization until tomorrow. > > Mete Alpaslan Dutch version changed/commited. Antoon Tolboom From philsvet at gmail.com Wed Jan 13 18:27:02 2010 From: philsvet at gmail.com (Philippe Svetoslavsky) Date: Wed, 13 Jan 2010 17:27:02 +0100 Subject: [Pardus-translators] YALI & 2009.1 translations In-Reply-To: <201001131555.33383.mete@pardus.org.tr> References: <201001131555.33383.mete@pardus.org.tr> Message-ID: Done. By the way, can you tell me what is the difference between branches and trunk, please ? 2010/1/13 Mete Alpaslan > Merhaba / Hello; > > Before 2009.1 release, I fixed some bugs and made translation changes in > uludag/branches/yali/2009. > > Please look over YALI 2009 branch and update translations in your > localization > until tomorrow. > > Mete Alpaslan > _______________________________________________ > Pardus-translators mailing list > Pardus-translators at pardus.org.tr > http://liste.pardus.org.tr/mailman/listinfo/pardus-translators > -------------- next part -------------- An HTML attachment was scrubbed... URL: From atolboo at gmail.com Wed Jan 13 23:27:28 2010 From: atolboo at gmail.com (Antoon Tolboom) Date: Wed, 13 Jan 2010 22:27:28 +0100 Subject: [Pardus-translators] Predefined bookmarks for Firefox. Message-ID: <201001132227.28189.atolboo@gmail.com> I have made an updated Dutch version for broken/outdated/new bookmarks for http://svn.pardus.org.tr/pardus/2009/devel/network/web/firefox/files/pardus/pardus_bookmark-nl.html The result of svn diff > pardus-bookmark-nl-svndiff.txt is in the attachment. I would highly appreciate it if somebody would apply the svndiff file. Thanks. regards, Antoon Tolboom -------------- next part -------------- Index: pardus_bookmark-nl.html =================================================================== --- pardus_bookmark-nl.html (revision 84655) +++ pardus_bookmark-nl.html (working copy) @@ -7,12 +7,9 @@

Bladwijzermenu

-

-
-

Bladwijzerwerkbalk

+

Bladwijzerwerkbalk

-

Meest bezocht -

Pardus

+

Pardus

Alles over Pardus

Pardus NL @@ -22,14 +19,17 @@
In de Pardus wiki kunt u veel informatie vinden
Forum pardus NL
Worldforum Pardus -
Bugzilla Main Page +
PardusUser.de Forum +
PardusUser.de Forum - Index +
Bugzilla Main Page
Pardus op Last.fm
Last.fm is een site voor muziekliefhebbers, dit is de Pardus groep

-

-

Computers

+

Computers

+

DistroWatch.com +
News and feature lists of Linux and BSD distributions.
Webwereld
Tweakers.net
AllesLinux.com forum @@ -37,6 +37,23 @@
Linux Online
Comprehensive information and resources about the Linux Operating System.

+

Nieuws

+

+

Nu.nl +
NU.nl geeft dagelijks algemeen-, financieel-, sport-, internet-, film en TV nieuws. Tevens staan er columns, interviews, ingezonden brieven. +
Algemeen Dagblad +
nrc +
NRC Handelsblad +
Telegraaf.nl +
Het laaste binnenland, buitenland, sport, prive en financieel nieuws +
Trouw +
Trouw de Verdieping op internet, voor het laatste nieuws en verdieping over zorg en gezondheid, opvoeding en onderwijs, religie en filosofie en natuur(tochten) en milieu, met de dagelijkse katernen deVerdieping en deGids, en op zaterdag Letter&Geest. +
Volkskrant +
NOS Teletekst +
WeerOnline +
Buienradar.nl +
Buienradar.be +

Informatie

Als u iets wilt opzoeken, van telefoonnummer tot satelietfoto

@@ -114,21 +131,6 @@

Margriet

-

Nieuws

-

-

Nu.nl -
NU.nl geeft dagelijks algemeen-, financieel-, sport-, internet-, film en TV nieuws. Tevens staan er columns, interviews, ingezonden brieven. -
Algemeen Dagblad -
nrc -
NRC Handelsblad -
Trouw -
Trouw de Verdieping op internet, voor het laatste nieuws en verdieping over zorg en gezondheid, opvoeding en onderwijs, religie en filosofie en natuur(tochten) en milieu, met de dagelijkse katernen deVerdieping en deGids, en op zaterdag Letter&Geest. -
Volkskrant -
NOS Teletekst -
WeerOnline -
Buienradar.nl -
Buienradar.be -

Winkelen

T?rk?e ?zg?r Yaz?l?m i?eri?i...

From khaeckel at hotmail.com Thu Jan 14 03:34:39 2010 From: khaeckel at hotmail.com (=?iso-8859-1?B?S2xlbWVucyBI5GNrZWw=?=) Date: Wed, 13 Jan 2010 22:34:39 -0300 Subject: [Pardus-translators] translation in /branches directory In-Reply-To: References: Message-ID: Hi Mete, I usually ignore all directories outside of "trunk". I will try what i can do, but i am possibly late for the spanish and german fixes or additions. greetings, Klemens H?ckel > ------------------------------ > > Message: 3 > Date: Wed, 13 Jan 2010 15:55:33 +0200 > From: Mete Alpaslan > To: pardus-translators at pardus.org.tr > Subject: [Pardus-translators] YALI & 2009.1 translations > Message-ID: <201001131555.33383.mete at pardus.org.tr> > Content-Type: Text/Plain; charset="utf-8" > > Merhaba / Hello; > > Before 2009.1 release, I fixed some bugs and made translation changes in > uludag/branches/yali/2009. > > Please look over YALI 2009 branch and update translations in your localization > until tomorrow. > > Mete Alpaslan > > > ------------------------------ _________________________________________________________________ News, entertainment and everything you care about at Live.com. Get it now! http://www.live.com/getstarted.aspx -------------- sonraki b?l?m -------------- Bir HTML eklentisi temizlendi... URL: From atolboo at gmail.com Thu Jan 14 11:16:23 2010 From: atolboo at gmail.com (Antoon Tolboom) Date: Thu, 14 Jan 2010 10:16:23 +0100 Subject: [Pardus-translators] YALI & 2009.1 translations In-Reply-To: <1919ab0a1001130601i3fe3fc57o2cfa8ebe60106e84@mail.gmail.com> References: <201001131555.33383.mete@pardus.org.tr> <1919ab0a1001130601i3fe3fc57o2cfa8ebe60106e84@mail.gmail.com> Message-ID: <201001141016.23903.atolboo@gmail.com> On Wednesday 13 January 2010 15:01:06 ??????? ??????? wrote: > Hi all! I'm one of translators of Yali (right now to russian). > How can I update my ru.po file? > Or Where can I find some info about it? > > With Best Regards, Nikolay Semenov > To do this you must write access to the apropriate data base. A recent copy of the data base will be needed/made with: svn update Requirement for using KWrite: The mark in KWrite > Settings > Configure Editor.. > Open/Save > Backup on Save > Local Files MUST BE REMOVED. Open a konsole in the apropriate directory (/branches/yali/2009/po/ in this case) and enter the command: SVN_EDITOR="kwrite" svn ci ("SVN_EDITOR="kwrite" svn ci ru.po" in this case) Kwrite will be opened and enter in the first line the reason for the change: ("Russian language update of /branches/yali/2009/po/ru.po" in this case) Save and Close Kwrite and in the konsole the file will be send to the data base. This is my short manual. regards, Antoon Tolboom From tribunal2000 at gmail.com Thu Jan 14 11:47:46 2010 From: tribunal2000 at gmail.com (=?KOI8-R?B?7snLz8zByiDzxc3Fzs/X?=) Date: Thu, 14 Jan 2010 12:47:46 +0300 Subject: [Pardus-translators] YALI & 2009.1 translations In-Reply-To: <201001141016.23903.atolboo@gmail.com> References: <201001131555.33383.mete@pardus.org.tr> <1919ab0a1001130601i3fe3fc57o2cfa8ebe60106e84@mail.gmail.com> <201001141016.23903.atolboo@gmail.com> Message-ID: <1919ab0a1001140147n1e1f9f51g13cb4ee12525486b@mail.gmail.com> Thank you :) But as I usnderstand, I cannot create all translations till 2009.1 :( I just don't have enough time. So, my question is how to update ru.po file after updating source file (english translation) using Lokalize? Or I need somethng different? With Best Regards, Nikolay Semenov 2010/1/14 Antoon Tolboom > On Wednesday 13 January 2010 15:01:06 ??????? ??????? wrote: > > Hi all! I'm one of translators of Yali (right now to russian). > > How can I update my ru.po file? > > Or Where can I find some info about it? > > > > With Best Regards, Nikolay Semenov > > > To do this you must write access to the apropriate data base. > > A recent copy of the data base will be needed/made with: > svn update > > Requirement for using KWrite: > The mark in KWrite > Settings > Configure Editor.. > Open/Save > Backup on > Save > Local Files MUST BE REMOVED. > > Open a konsole in the apropriate directory (/branches/yali/2009/po/ in > this case) and enter the command: > SVN_EDITOR="kwrite" svn ci ("SVN_EDITOR="kwrite" svn ci ru.po" > in this case) > > Kwrite will be opened and enter in the first line the reason for the > change: > ("Russian language update of /branches/yali/2009/po/ru.po" in this case) > Save and Close Kwrite and in the konsole the file will be send to the data > base. > > This is my short manual. > > regards, > Antoon Tolboom > _______________________________________________ > Pardus-translators mailing list > Pardus-translators at pardus.org.tr > http://liste.pardus.org.tr/mailman/listinfo/pardus-translators > -------------- next part -------------- An HTML attachment was scrubbed... URL: From atolboo at gmail.com Thu Jan 14 13:50:32 2010 From: atolboo at gmail.com (Antoon Tolboom) Date: Thu, 14 Jan 2010 12:50:32 +0100 Subject: [Pardus-translators] YALI & 2009.1 translations In-Reply-To: <1919ab0a1001140147n1e1f9f51g13cb4ee12525486b@mail.gmail.com> References: <201001131555.33383.mete@pardus.org.tr> <201001141016.23903.atolboo@gmail.com> <1919ab0a1001140147n1e1f9f51g13cb4ee12525486b@mail.gmail.com> Message-ID: <201001141250.32312.atolboo@gmail.com> On Thursday 14 January 2010 10:47:46 ??????? ??????? wrote: > Thank you :) > But as I usnderstand, I cannot create all translations till 2009.1 :( > I just don't have enough time. > So, my question is how to update ru.po file after updating source file > (english translation) You can update the ru.po file at any time. But for Yali it will only have affect until the next release of the .iso file. For all other applications have alook in: http://worldforum.pardus-linux.nl/index.php?topic=3029.msg14772#msg14772 This is for K3b and maybe also works for other application. > using Lokalize? Or I need somethng different? To make your changes you can use: For KDE4 = Lokalize For KDE3 = KBabel Save changes and use SVN_EDITOR="kwrite" svn ci to send to the database. > > With Best Regards, Nikolay Semenov > regards, Antoon Tolboom From bahadir at pardus.org.tr Thu Jan 14 14:41:41 2010 From: bahadir at pardus.org.tr (=?utf-8?q?Bahad=C4=B1r_Kandemir?=) Date: Thu, 14 Jan 2010 14:41:41 +0200 Subject: [Pardus-translators] Packed All *-Managers Message-ID: <201001141441.45810.bahadir@pardus.org.tr> Hello, I've re-packed all manager applications (that i maintain ofc.). All translations will be in release. Thanks everyone! -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. URL: From ozan at pardus.org.tr Thu Jan 14 14:46:24 2010 From: ozan at pardus.org.tr (=?UTF-8?B?T3phbiDDh2HEn2xheWFu?=) Date: Thu, 14 Jan 2010 14:46:24 +0200 Subject: [Pardus-translators] 1 new string to translate for sysinfo Message-ID: <4B4F1220.1080306@pardus.org.tr> Hi, I've updated messages for trunk/kde/sysinfo, there's 1 new string to translate: "Swap: Not in use" I already translated to French and Turkish so It would be nice if you can commit this translation for 2009.1. From atolboo at gmail.com Thu Jan 14 15:03:25 2010 From: atolboo at gmail.com (Antoon Tolboom) Date: Thu, 14 Jan 2010 14:03:25 +0100 Subject: [Pardus-translators] 1 new string to translate for sysinfo In-Reply-To: <4B4F1220.1080306@pardus.org.tr> References: <4B4F1220.1080306@pardus.org.tr> Message-ID: <201001141403.25734.atolboo@gmail.com> On Thursday 14 January 2010 13:46:24 Ozan ?a?layan wrote: > Hi, > > I've updated messages for trunk/kde/sysinfo, there's 1 new string to > translate: > > "Swap: Not in use" > > I already translated to French and Turkish so It would be nice if you can > commit this translation for 2009.1. > Dutch update is done! regards, Antoon Tolboom From atolboo at gmail.com Thu Jan 14 15:07:45 2010 From: atolboo at gmail.com (Antoon Tolboom) Date: Thu, 14 Jan 2010 14:07:45 +0100 Subject: [Pardus-translators] Packed All *-Managers In-Reply-To: <201001141441.45810.bahadir@pardus.org.tr> References: <201001141441.45810.bahadir@pardus.org.tr> Message-ID: <201001141407.45420.atolboo@gmail.com> On Thursday 14 January 2010 13:41:41 Bahad?r Kandemir wrote: > Hello, > > I've re-packed all manager applications (that i maintain ofc.). All > translations will be in release. > > Thanks everyone! Thank you, and I hope this will solve http://liste.pardus.org.tr/pardus-translators/2010-January/000490.html regards, Antoon Tolboom From tribunal2000 at gmail.com Thu Jan 14 15:35:27 2010 From: tribunal2000 at gmail.com (=?KOI8-R?B?7snLz8zByiDzxc3Fzs/X?=) Date: Thu, 14 Jan 2010 16:35:27 +0300 Subject: [Pardus-translators] YALI & 2009.1 translations In-Reply-To: <201001141250.32312.atolboo@gmail.com> References: <201001131555.33383.mete@pardus.org.tr> <201001141016.23903.atolboo@gmail.com> <1919ab0a1001140147n1e1f9f51g13cb4ee12525486b@mail.gmail.com> <201001141250.32312.atolboo@gmail.com> Message-ID: <1919ab0a1001140535m3c2d7dd7lab5ee6be52b9132e@mail.gmail.com> Thank you! But I think we are talking about different problems. To work with SVN I use KDESVN - nice app. It is not a problem. And as I understand, something has changed in Yali and Yali source translations (original .po file) Only source translations have changed, but I need to update ru.po file - russian translation of Yali. So, the question is how using original .po file update my own ru.po to add/change some strings in it. With Best Regards, Nikolay Semenov 2010/1/14 Antoon Tolboom > On Thursday 14 January 2010 10:47:46 ??????? ??????? wrote: > > Thank you :) > > But as I usnderstand, I cannot create all translations till 2009.1 :( > > I just don't have enough time. > > So, my question is how to update ru.po file after updating source file > > (english translation) > You can update the ru.po file at any time. > But for Yali it will only have affect until the next release of the .iso > file. > For all other applications have alook in: > http://worldforum.pardus-linux.nl/index.php?topic=3029.msg14772#msg14772 > This is for K3b and maybe also works for other application. > > using Lokalize? Or I need somethng different? > To make your changes you can use: > For KDE4 = Lokalize > For KDE3 = KBabel > Save changes and use SVN_EDITOR="kwrite" svn ci to send to the > database. > > > > With Best Regards, Nikolay Semenov > > > > regards, > Antoon Tolboom > _______________________________________________ > Pardus-translators mailing list > Pardus-translators at pardus.org.tr > http://liste.pardus.org.tr/mailman/listinfo/pardus-translators > -------------- next part -------------- An HTML attachment was scrubbed... URL: From philsvet at gmail.com Thu Jan 14 16:10:52 2010 From: philsvet at gmail.com (Philippe Svetoslavsky) Date: Thu, 14 Jan 2010 15:10:52 +0100 Subject: [Pardus-translators] YALI & 2009.1 translations In-Reply-To: <1919ab0a1001140535m3c2d7dd7lab5ee6be52b9132e@mail.gmail.com> References: <201001131555.33383.mete@pardus.org.tr> <201001141016.23903.atolboo@gmail.com> <1919ab0a1001140147n1e1f9f51g13cb4ee12525486b@mail.gmail.com> <201001141250.32312.atolboo@gmail.com> <1919ab0a1001140535m3c2d7dd7lab5ee6be52b9132e@mail.gmail.com> Message-ID: You don't have to add any strings, they have already been added. 2010/1/14 ??????? ??????? > Thank you! > But I think we are talking about different problems. > To work with SVN I use KDESVN - nice app. It is not a problem. > And as I understand, something has changed in Yali and Yali source > translations (original .po file) > Only source translations have changed, but I need to update ru.po file - > russian translation of Yali. > So, the question is how using original .po file update my own ru.po to > add/change some strings in it. > > > With Best Regards, Nikolay Semenov > > 2010/1/14 Antoon Tolboom > >> On Thursday 14 January 2010 10:47:46 ??????? ??????? wrote: >> >> > Thank you :) >> > But as I usnderstand, I cannot create all translations till 2009.1 :( >> > I just don't have enough time. >> > So, my question is how to update ru.po file after updating source file >> > (english translation) >> You can update the ru.po file at any time. >> But for Yali it will only have affect until the next release of the .iso >> file. >> For all other applications have alook in: >> http://worldforum.pardus-linux.nl/index.php?topic=3029.msg14772#msg14772 >> This is for K3b and maybe also works for other application. >> > using Lokalize? Or I need somethng different? >> To make your changes you can use: >> For KDE4 = Lokalize >> For KDE3 = KBabel >> Save changes and use SVN_EDITOR="kwrite" svn ci to send to the >> database. >> > >> > With Best Regards, Nikolay Semenov >> > >> >> regards, >> Antoon Tolboom >> _______________________________________________ >> Pardus-translators mailing list >> Pardus-translators at pardus.org.tr >> http://liste.pardus.org.tr/mailman/listinfo/pardus-translators >> > > > _______________________________________________ > Pardus-translators mailing list > Pardus-translators at pardus.org.tr > http://liste.pardus.org.tr/mailman/listinfo/pardus-translators > -------------- next part -------------- An HTML attachment was scrubbed... URL: From atolboo at gmail.com Thu Jan 14 16:36:25 2010 From: atolboo at gmail.com (Antoon Tolboom) Date: Thu, 14 Jan 2010 15:36:25 +0100 Subject: [Pardus-translators] YALI & 2009.1 translations In-Reply-To: References: <201001131555.33383.mete@pardus.org.tr> <1919ab0a1001140535m3c2d7dd7lab5ee6be52b9132e@mail.gmail.com> Message-ID: <201001141536.25345.atolboo@gmail.com> On Thursday 14 January 2010 15:10:52 Philippe Svetoslavsky wrote: > You don't have to add any strings, they have already been added. That's correct. > > 2010/1/14 ??????? ??????? > > > Thank you! > > But I think we are talking about different problems. > > To work with SVN I use KDESVN - nice app. It is not a problem. > > And as I understand, something has changed in Yali and Yali source > > translations (original .po file) > > Only source translations have changed, but I need to update ru.po file - > > russian translation of Yali. > > So, the question is how using original .po file update my own ru.po to > > add/change some strings in it. > > You only have to open /branches/yali/2009/po.ru.po in Lokalize or KBabel and then you will see (at this moment) Fuzzy: 3 Untranslated : 42. And the Untranslated : 42 are the added lines. After translating Save ru.po and do a ".....svn ci ru.po" That's all there is todo. regards, Antoon Tolboom From atolboo at gmail.com Thu Jan 14 16:39:26 2010 From: atolboo at gmail.com (Antoon Tolboom) Date: Thu, 14 Jan 2010 15:39:26 +0100 Subject: [Pardus-translators] YALI & 2009.1 translations In-Reply-To: References: <201001131555.33383.mete@pardus.org.tr> Message-ID: <201001141539.26868.atolboo@gmail.com> On Wednesday 13 January 2010 17:27:02 Philippe Svetoslavsky wrote: > Done. > By the way, can you tell me what is the difference between branches and > trunk, please ? > > 2010/1/13 Mete Alpaslan > > > Merhaba / Hello; > > > > Before 2009.1 release, I fixed some bugs and made translation changes in > > uludag/branches/yali/2009. > > > > Please look over YALI 2009 branch and update translations in your > > localization > > until tomorrow. > > > > Mete Alpaslan I also would like to know the difference! regards, Antoon Tolboom From tribunal2000 at gmail.com Thu Jan 14 17:56:10 2010 From: tribunal2000 at gmail.com (=?KOI8-R?B?7snLz8zByiDzxc3Fzs/X?=) Date: Thu, 14 Jan 2010 18:56:10 +0300 Subject: [Pardus-translators] YALI & 2009.1 translations In-Reply-To: References: <201001131555.33383.mete@pardus.org.tr> <201001141016.23903.atolboo@gmail.com> <1919ab0a1001140147n1e1f9f51g13cb4ee12525486b@mail.gmail.com> <201001141250.32312.atolboo@gmail.com> <1919ab0a1001140535m3c2d7dd7lab5ee6be52b9132e@mail.gmail.com> Message-ID: <1919ab0a1001140756i29f468d3j4115cca6228af525@mail.gmail.com> So all *.po files have been patched (including ru.po)? 2010/1/14 Philippe Svetoslavsky > You don't have to add any strings, they have already been added. > > 2010/1/14 ??????? ??????? > > Thank you! >> But I think we are talking about different problems. >> To work with SVN I use KDESVN - nice app. It is not a problem. >> And as I understand, something has changed in Yali and Yali source >> translations (original .po file) >> Only source translations have changed, but I need to update ru.po file - >> russian translation of Yali. >> So, the question is how using original .po file update my own ru.po to >> add/change some strings in it. >> >> >> With Best Regards, Nikolay Semenov >> >> 2010/1/14 Antoon Tolboom >> >>> On Thursday 14 January 2010 10:47:46 ??????? ??????? wrote: >>> >>> > Thank you :) >>> > But as I usnderstand, I cannot create all translations till 2009.1 :( >>> > I just don't have enough time. >>> > So, my question is how to update ru.po file after updating source file >>> > (english translation) >>> You can update the ru.po file at any time. >>> But for Yali it will only have affect until the next release of the .iso >>> file. >>> For all other applications have alook in: >>> http://worldforum.pardus-linux.nl/index.php?topic=3029.msg14772#msg14772 >>> This is for K3b and maybe also works for other application. >>> > using Lokalize? Or I need somethng different? >>> To make your changes you can use: >>> For KDE4 = Lokalize >>> For KDE3 = KBabel >>> Save changes and use SVN_EDITOR="kwrite" svn ci to send to the >>> database. >>> > >>> > With Best Regards, Nikolay Semenov >>> > >>> >>> regards, >>> Antoon Tolboom >>> _______________________________________________ >>> Pardus-translators mailing list >>> Pardus-translators at pardus.org.tr >>> http://liste.pardus.org.tr/mailman/listinfo/pardus-translators >>> >> >> >> _______________________________________________ >> Pardus-translators mailing list >> Pardus-translators at pardus.org.tr >> http://liste.pardus.org.tr/mailman/listinfo/pardus-translators >> > > > _______________________________________________ > Pardus-translators mailing list > Pardus-translators at pardus.org.tr > http://liste.pardus.org.tr/mailman/listinfo/pardus-translators > -------------- next part -------------- An HTML attachment was scrubbed... URL: From philsvet at gmail.com Thu Jan 14 20:37:31 2010 From: philsvet at gmail.com (Philippe Svetoslavsky) Date: Thu, 14 Jan 2010 19:37:31 +0100 Subject: [Pardus-translators] YALI & 2009.1 translations In-Reply-To: <1919ab0a1001140756i29f468d3j4115cca6228af525@mail.gmail.com> References: <201001131555.33383.mete@pardus.org.tr> <201001141016.23903.atolboo@gmail.com> <1919ab0a1001140147n1e1f9f51g13cb4ee12525486b@mail.gmail.com> <201001141250.32312.atolboo@gmail.com> <1919ab0a1001140535m3c2d7dd7lab5ee6be52b9132e@mail.gmail.com> <1919ab0a1001140756i29f468d3j4115cca6228af525@mail.gmail.com> Message-ID: Normally, yes. You can check for yourself in Lokalize. 2010/1/14 ??????? ??????? > So all *.po files have been patched (including ru.po)? > > 2010/1/14 Philippe Svetoslavsky > > You don't have to add any strings, they have already been added. >> >> 2010/1/14 ??????? ??????? >> >> Thank you! >>> But I think we are talking about different problems. >>> To work with SVN I use KDESVN - nice app. It is not a problem. >>> And as I understand, something has changed in Yali and Yali source >>> translations (original .po file) >>> Only source translations have changed, but I need to update ru.po file - >>> russian translation of Yali. >>> So, the question is how using original .po file update my own ru.po to >>> add/change some strings in it. >>> >>> >>> With Best Regards, Nikolay Semenov >>> >>> 2010/1/14 Antoon Tolboom >>> >>>> On Thursday 14 January 2010 10:47:46 ??????? ??????? wrote: >>>> >>>> > Thank you :) >>>> > But as I usnderstand, I cannot create all translations till 2009.1 :( >>>> > I just don't have enough time. >>>> > So, my question is how to update ru.po file after updating source file >>>> > (english translation) >>>> You can update the ru.po file at any time. >>>> But for Yali it will only have affect until the next release of the .iso >>>> file. >>>> For all other applications have alook in: >>>> http://worldforum.pardus-linux.nl/index.php?topic=3029.msg14772#msg14772 >>>> This is for K3b and maybe also works for other application. >>>> > using Lokalize? Or I need somethng different? >>>> To make your changes you can use: >>>> For KDE4 = Lokalize >>>> For KDE3 = KBabel >>>> Save changes and use SVN_EDITOR="kwrite" svn ci to send to >>>> the database. >>>> > >>>> > With Best Regards, Nikolay Semenov >>>> > >>>> >>>> regards, >>>> Antoon Tolboom >>>> _______________________________________________ >>>> Pardus-translators mailing list >>>> Pardus-translators at pardus.org.tr >>>> http://liste.pardus.org.tr/mailman/listinfo/pardus-translators >>>> >>> >>> >>> _______________________________________________ >>> Pardus-translators mailing list >>> Pardus-translators at pardus.org.tr >>> http://liste.pardus.org.tr/mailman/listinfo/pardus-translators >>> >> >> >> _______________________________________________ >> Pardus-translators mailing list >> Pardus-translators at pardus.org.tr >> http://liste.pardus.org.tr/mailman/listinfo/pardus-translators >> > > > _______________________________________________ > Pardus-translators mailing list > Pardus-translators at pardus.org.tr > http://liste.pardus.org.tr/mailman/listinfo/pardus-translators > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tribunal2000 at gmail.com Thu Jan 14 21:14:27 2010 From: tribunal2000 at gmail.com (=?KOI8-R?B?7snLz8zByiDzxc3Fzs/X?=) Date: Thu, 14 Jan 2010 22:14:27 +0300 Subject: [Pardus-translators] YALI & 2009.1 translations In-Reply-To: References: <201001131555.33383.mete@pardus.org.tr> <201001141016.23903.atolboo@gmail.com> <1919ab0a1001140147n1e1f9f51g13cb4ee12525486b@mail.gmail.com> <201001141250.32312.atolboo@gmail.com> <1919ab0a1001140535m3c2d7dd7lab5ee6be52b9132e@mail.gmail.com> <1919ab0a1001140756i29f468d3j4115cca6228af525@mail.gmail.com> Message-ID: <1919ab0a1001141114s15b94313ma04d97affba38b64@mail.gmail.com> The last revision (excluding my own) was at 27.10.09 Is it right? With Best Regards, Nikolay Semenov 2010/1/14 Philippe Svetoslavsky > Normally, yes. You can check for yourself in Lokalize. > > > 2010/1/14 ??????? ??????? > >> So all *.po files have been patched (including ru.po)? >> >> 2010/1/14 Philippe Svetoslavsky >> >> You don't have to add any strings, they have already been added. >>> >>> 2010/1/14 ??????? ??????? >>> >>> Thank you! >>>> But I think we are talking about different problems. >>>> To work with SVN I use KDESVN - nice app. It is not a problem. >>>> And as I understand, something has changed in Yali and Yali source >>>> translations (original .po file) >>>> Only source translations have changed, but I need to update ru.po file - >>>> russian translation of Yali. >>>> So, the question is how using original .po file update my own ru.po to >>>> add/change some strings in it. >>>> >>>> >>>> With Best Regards, Nikolay Semenov >>>> >>>> 2010/1/14 Antoon Tolboom >>>> >>>>> On Thursday 14 January 2010 10:47:46 ??????? ??????? wrote: >>>>> >>>>> > Thank you :) >>>>> > But as I usnderstand, I cannot create all translations till 2009.1 :( >>>>> > I just don't have enough time. >>>>> > So, my question is how to update ru.po file after updating source >>>>> file >>>>> > (english translation) >>>>> You can update the ru.po file at any time. >>>>> But for Yali it will only have affect until the next release of the >>>>> .iso file. >>>>> For all other applications have alook in: >>>>> >>>>> http://worldforum.pardus-linux.nl/index.php?topic=3029.msg14772#msg14772 >>>>> This is for K3b and maybe also works for other application. >>>>> > using Lokalize? Or I need somethng different? >>>>> To make your changes you can use: >>>>> For KDE4 = Lokalize >>>>> For KDE3 = KBabel >>>>> Save changes and use SVN_EDITOR="kwrite" svn ci to send to >>>>> the database. >>>>> > >>>>> > With Best Regards, Nikolay Semenov >>>>> > >>>>> >>>>> regards, >>>>> Antoon Tolboom >>>>> _______________________________________________ >>>>> Pardus-translators mailing list >>>>> Pardus-translators at pardus.org.tr >>>>> http://liste.pardus.org.tr/mailman/listinfo/pardus-translators >>>>> >>>> >>>> >>>> _______________________________________________ >>>> Pardus-translators mailing list >>>> Pardus-translators at pardus.org.tr >>>> http://liste.pardus.org.tr/mailman/listinfo/pardus-translators >>>> >>> >>> >>> _______________________________________________ >>> Pardus-translators mailing list >>> Pardus-translators at pardus.org.tr >>> http://liste.pardus.org.tr/mailman/listinfo/pardus-translators >>> >> >> >> _______________________________________________ >> Pardus-translators mailing list >> Pardus-translators at pardus.org.tr >> http://liste.pardus.org.tr/mailman/listinfo/pardus-translators >> > > > _______________________________________________ > Pardus-translators mailing list > Pardus-translators at pardus.org.tr > http://liste.pardus.org.tr/mailman/listinfo/pardus-translators > -------------- next part -------------- An HTML attachment was scrubbed... URL: From philsvet at gmail.com Thu Jan 14 21:51:51 2010 From: philsvet at gmail.com (Philippe Svetoslavsky) Date: Thu, 14 Jan 2010 20:51:51 +0100 Subject: [Pardus-translators] YALI & 2009.1 translations In-Reply-To: <1919ab0a1001141114s15b94313ma04d97affba38b64@mail.gmail.com> References: <201001131555.33383.mete@pardus.org.tr> <201001141016.23903.atolboo@gmail.com> <1919ab0a1001140147n1e1f9f51g13cb4ee12525486b@mail.gmail.com> <201001141250.32312.atolboo@gmail.com> <1919ab0a1001140535m3c2d7dd7lab5ee6be52b9132e@mail.gmail.com> <1919ab0a1001140756i29f468d3j4115cca6228af525@mail.gmail.com> <1919ab0a1001141114s15b94313ma04d97affba38b64@mail.gmail.com> Message-ID: I don't think so. Why are you asking ? 2010/1/14 ??????? ??????? > The last revision (excluding my own) was at 27.10.09 > Is it right? > > > With Best Regards, Nikolay Semenov > > 2010/1/14 Philippe Svetoslavsky > >> Normally, yes. You can check for yourself in Lokalize. >> >> >> 2010/1/14 ??????? ??????? >> >>> So all *.po files have been patched (including ru.po)? >>> >>> 2010/1/14 Philippe Svetoslavsky >>> >>> You don't have to add any strings, they have already been added. >>>> >>>> 2010/1/14 ??????? ??????? >>>> >>>> Thank you! >>>>> But I think we are talking about different problems. >>>>> To work with SVN I use KDESVN - nice app. It is not a problem. >>>>> And as I understand, something has changed in Yali and Yali source >>>>> translations (original .po file) >>>>> Only source translations have changed, but I need to update ru.po file >>>>> - russian translation of Yali. >>>>> So, the question is how using original .po file update my own ru.po to >>>>> add/change some strings in it. >>>>> >>>>> >>>>> With Best Regards, Nikolay Semenov >>>>> >>>>> 2010/1/14 Antoon Tolboom >>>>> >>>>>> On Thursday 14 January 2010 10:47:46 ??????? ??????? wrote: >>>>>> >>>>>> > Thank you :) >>>>>> > But as I usnderstand, I cannot create all translations till 2009.1 >>>>>> :( >>>>>> > I just don't have enough time. >>>>>> > So, my question is how to update ru.po file after updating source >>>>>> file >>>>>> > (english translation) >>>>>> You can update the ru.po file at any time. >>>>>> But for Yali it will only have affect until the next release of the >>>>>> .iso file. >>>>>> For all other applications have alook in: >>>>>> >>>>>> http://worldforum.pardus-linux.nl/index.php?topic=3029.msg14772#msg14772 >>>>>> This is for K3b and maybe also works for other application. >>>>>> > using Lokalize? Or I need somethng different? >>>>>> To make your changes you can use: >>>>>> For KDE4 = Lokalize >>>>>> For KDE3 = KBabel >>>>>> Save changes and use SVN_EDITOR="kwrite" svn ci to send to >>>>>> the database. >>>>>> > >>>>>> > With Best Regards, Nikolay Semenov >>>>>> > >>>>>> >>>>>> regards, >>>>>> Antoon Tolboom >>>>>> _______________________________________________ >>>>>> Pardus-translators mailing list >>>>>> Pardus-translators at pardus.org.tr >>>>>> http://liste.pardus.org.tr/mailman/listinfo/pardus-translators >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Pardus-translators mailing list >>>>> Pardus-translators at pardus.org.tr >>>>> http://liste.pardus.org.tr/mailman/listinfo/pardus-translators >>>>> >>>> >>>> >>>> _______________________________________________ >>>> Pardus-translators mailing list >>>> Pardus-translators at pardus.org.tr >>>> http://liste.pardus.org.tr/mailman/listinfo/pardus-translators >>>> >>> >>> >>> _______________________________________________ >>> Pardus-translators mailing list >>> Pardus-translators at pardus.org.tr >>> http://liste.pardus.org.tr/mailman/listinfo/pardus-translators >>> >> >> >> _______________________________________________ >> Pardus-translators mailing list >> Pardus-translators at pardus.org.tr >> http://liste.pardus.org.tr/mailman/listinfo/pardus-translators >> > > > _______________________________________________ > Pardus-translators mailing list > Pardus-translators at pardus.org.tr > http://liste.pardus.org.tr/mailman/listinfo/pardus-translators > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tribunal2000 at gmail.com Thu Jan 14 23:10:30 2010 From: tribunal2000 at gmail.com (=?KOI8-R?B?7snLz8zByiDzxc3Fzs/X?=) Date: Fri, 15 Jan 2010 00:10:30 +0300 Subject: [Pardus-translators] YALI & 2009.1 translations In-Reply-To: References: <201001131555.33383.mete@pardus.org.tr> <201001141016.23903.atolboo@gmail.com> <1919ab0a1001140147n1e1f9f51g13cb4ee12525486b@mail.gmail.com> <201001141250.32312.atolboo@gmail.com> <1919ab0a1001140535m3c2d7dd7lab5ee6be52b9132e@mail.gmail.com> <1919ab0a1001140756i29f468d3j4115cca6228af525@mail.gmail.com> <1919ab0a1001141114s15b94313ma04d97affba38b64@mail.gmail.com> Message-ID: <1919ab0a1001141310m475a89f4vfb620cd89b1b35e2@mail.gmail.com> I have seen, that Pardus 2009.1 comes soon, so I have thought, that Yali should be updated too. And This is my question: After updating Yali4.pot should all *.po files be updated? I mean untranslated part. Translation will be made by translators. Sorry, but I am not a professional translator - it seems there are only 2 active russian users of Pardus (who knows english, of course). 2010/1/14 Philippe Svetoslavsky > I don't think so. Why are you asking ? > > > 2010/1/14 ??????? ??????? > >> The last revision (excluding my own) was at 27.10.09 >> Is it right? >> >> >> With Best Regards, Nikolay Semenov >> >> 2010/1/14 Philippe Svetoslavsky >> >>> Normally, yes. You can check for yourself in Lokalize. >>> >>> >>> 2010/1/14 ??????? ??????? >>> >>>> So all *.po files have been patched (including ru.po)? >>>> >>>> 2010/1/14 Philippe Svetoslavsky >>>> >>>> You don't have to add any strings, they have already been added. >>>>> >>>>> 2010/1/14 ??????? ??????? >>>>> >>>>> Thank you! >>>>>> But I think we are talking about different problems. >>>>>> To work with SVN I use KDESVN - nice app. It is not a problem. >>>>>> And as I understand, something has changed in Yali and Yali source >>>>>> translations (original .po file) >>>>>> Only source translations have changed, but I need to update ru.po file >>>>>> - russian translation of Yali. >>>>>> So, the question is how using original .po file update my own ru.po to >>>>>> add/change some strings in it. >>>>>> >>>>>> >>>>>> With Best Regards, Nikolay Semenov >>>>>> >>>>>> 2010/1/14 Antoon Tolboom >>>>>> >>>>>>> On Thursday 14 January 2010 10:47:46 ??????? ??????? wrote: >>>>>>> >>>>>>> > Thank you :) >>>>>>> > But as I usnderstand, I cannot create all translations till 2009.1 >>>>>>> :( >>>>>>> > I just don't have enough time. >>>>>>> > So, my question is how to update ru.po file after updating source >>>>>>> file >>>>>>> > (english translation) >>>>>>> You can update the ru.po file at any time. >>>>>>> But for Yali it will only have affect until the next release of the >>>>>>> .iso file. >>>>>>> For all other applications have alook in: >>>>>>> >>>>>>> http://worldforum.pardus-linux.nl/index.php?topic=3029.msg14772#msg14772 >>>>>>> This is for K3b and maybe also works for other application. >>>>>>> > using Lokalize? Or I need somethng different? >>>>>>> To make your changes you can use: >>>>>>> For KDE4 = Lokalize >>>>>>> For KDE3 = KBabel >>>>>>> Save changes and use SVN_EDITOR="kwrite" svn ci to send to >>>>>>> the database. >>>>>>> > >>>>>>> > With Best Regards, Nikolay Semenov >>>>>>> > >>>>>>> >>>>>>> regards, >>>>>>> Antoon Tolboom >>>>>>> _______________________________________________ >>>>>>> Pardus-translators mailing list >>>>>>> Pardus-translators at pardus.org.tr >>>>>>> http://liste.pardus.org.tr/mailman/listinfo/pardus-translators >>>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Pardus-translators mailing list >>>>>> Pardus-translators at pardus.org.tr >>>>>> http://liste.pardus.org.tr/mailman/listinfo/pardus-translators >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Pardus-translators mailing list >>>>> Pardus-translators at pardus.org.tr >>>>> http://liste.pardus.org.tr/mailman/listinfo/pardus-translators >>>>> >>>> >>>> >>>> _______________________________________________ >>>> Pardus-translators mailing list >>>> Pardus-translators at pardus.org.tr >>>> http://liste.pardus.org.tr/mailman/listinfo/pardus-translators >>>> >>> >>> >>> _______________________________________________ >>> Pardus-translators mailing list >>> Pardus-translators at pardus.org.tr >>> http://liste.pardus.org.tr/mailman/listinfo/pardus-translators >>> >> >> >> _______________________________________________ >> Pardus-translators mailing list >> Pardus-translators at pardus.org.tr >> http://liste.pardus.org.tr/mailman/listinfo/pardus-translators >> > > > _______________________________________________ > Pardus-translators mailing list > Pardus-translators at pardus.org.tr > http://liste.pardus.org.tr/mailman/listinfo/pardus-translators > -------------- next part -------------- An HTML attachment was scrubbed... URL: From philsvet at gmail.com Thu Jan 14 23:34:08 2010 From: philsvet at gmail.com (Philippe Svetoslavsky) Date: Thu, 14 Jan 2010 22:34:08 +0100 Subject: [Pardus-translators] YALI & 2009.1 translations In-Reply-To: <1919ab0a1001141310m475a89f4vfb620cd89b1b35e2@mail.gmail.com> References: <201001131555.33383.mete@pardus.org.tr> <1919ab0a1001140147n1e1f9f51g13cb4ee12525486b@mail.gmail.com> <201001141250.32312.atolboo@gmail.com> <1919ab0a1001140535m3c2d7dd7lab5ee6be52b9132e@mail.gmail.com> <1919ab0a1001140756i29f468d3j4115cca6228af525@mail.gmail.com> <1919ab0a1001141114s15b94313ma04d97affba38b64@mail.gmail.com> <1919ab0a1001141310m475a89f4vfb620cd89b1b35e2@mail.gmail.com> Message-ID: Translators don't have to edit .pot files. When an edition is made on a .pot file by an application developper, all .po files are automatically updated accordingly, so that translators only have to deal with these .po files. 2010/1/14 ??????? ??????? > I have seen, that Pardus 2009.1 comes soon, so I have thought, that Yali > should be updated too. > And This is my question: > After updating Yali4.pot should all *.po files be updated? > I mean untranslated part. Translation will be made by translators. > Sorry, but I am not a professional translator - it seems there are only 2 > active russian users of Pardus (who knows english, of course). > > > 2010/1/14 Philippe Svetoslavsky > >> I don't think so. Why are you asking ? >> >> >> 2010/1/14 ??????? ??????? >> >>> The last revision (excluding my own) was at 27.10.09 >>> Is it right? >>> >>> >>> With Best Regards, Nikolay Semenov >>> >>> 2010/1/14 Philippe Svetoslavsky >>> >>>> Normally, yes. You can check for yourself in Lokalize. >>>> >>>> >>>> 2010/1/14 ??????? ??????? >>>> >>>>> So all *.po files have been patched (including ru.po)? >>>>> >>>>> 2010/1/14 Philippe Svetoslavsky >>>>> >>>>> You don't have to add any strings, they have already been added. >>>>>> >>>>>> 2010/1/14 ??????? ??????? >>>>>> >>>>>> Thank you! >>>>>>> But I think we are talking about different problems. >>>>>>> To work with SVN I use KDESVN - nice app. It is not a problem. >>>>>>> And as I understand, something has changed in Yali and Yali source >>>>>>> translations (original .po file) >>>>>>> Only source translations have changed, but I need to update ru.po >>>>>>> file - russian translation of Yali. >>>>>>> So, the question is how using original .po file update my own ru.po >>>>>>> to add/change some strings in it. >>>>>>> >>>>>>> >>>>>>> With Best Regards, Nikolay Semenov >>>>>>> >>>>>>> 2010/1/14 Antoon Tolboom >>>>>>> >>>>>>>> On Thursday 14 January 2010 10:47:46 ??????? ??????? wrote: >>>>>>>> >>>>>>>> > Thank you :) >>>>>>>> > But as I usnderstand, I cannot create all translations till 2009.1 >>>>>>>> :( >>>>>>>> > I just don't have enough time. >>>>>>>> > So, my question is how to update ru.po file after updating source >>>>>>>> file >>>>>>>> > (english translation) >>>>>>>> You can update the ru.po file at any time. >>>>>>>> But for Yali it will only have affect until the next release of the >>>>>>>> .iso file. >>>>>>>> For all other applications have alook in: >>>>>>>> >>>>>>>> http://worldforum.pardus-linux.nl/index.php?topic=3029.msg14772#msg14772 >>>>>>>> This is for K3b and maybe also works for other application. >>>>>>>> > using Lokalize? Or I need somethng different? >>>>>>>> To make your changes you can use: >>>>>>>> For KDE4 = Lokalize >>>>>>>> For KDE3 = KBabel >>>>>>>> Save changes and use SVN_EDITOR="kwrite" svn ci to send >>>>>>>> to the database. >>>>>>>> > >>>>>>>> > With Best Regards, Nikolay Semenov >>>>>>>> > >>>>>>>> >>>>>>>> regards, >>>>>>>> Antoon Tolboom >>>>>>>> _______________________________________________ >>>>>>>> Pardus-translators mailing list >>>>>>>> Pardus-translators at pardus.org.tr >>>>>>>> http://liste.pardus.org.tr/mailman/listinfo/pardus-translators >>>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Pardus-translators mailing list >>>>>>> Pardus-translators at pardus.org.tr >>>>>>> http://liste.pardus.org.tr/mailman/listinfo/pardus-translators >>>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Pardus-translators mailing list >>>>>> Pardus-translators at pardus.org.tr >>>>>> http://liste.pardus.org.tr/mailman/listinfo/pardus-translators >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Pardus-translators mailing list >>>>> Pardus-translators at pardus.org.tr >>>>> http://liste.pardus.org.tr/mailman/listinfo/pardus-translators >>>>> >>>> >>>> >>>> _______________________________________________ >>>> Pardus-translators mailing list >>>> Pardus-translators at pardus.org.tr >>>> http://liste.pardus.org.tr/mailman/listinfo/pardus-translators >>>> >>> >>> >>> _______________________________________________ >>> Pardus-translators mailing list >>> Pardus-translators at pardus.org.tr >>> http://liste.pardus.org.tr/mailman/listinfo/pardus-translators >>> >> >> >> _______________________________________________ >> Pardus-translators mailing list >> Pardus-translators at pardus.org.tr >> http://liste.pardus.org.tr/mailman/listinfo/pardus-translators >> > > > _______________________________________________ > Pardus-translators mailing list > Pardus-translators at pardus.org.tr > http://liste.pardus.org.tr/mailman/listinfo/pardus-translators > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tribunal2000 at gmail.com Fri Jan 15 08:02:25 2010 From: tribunal2000 at gmail.com (=?KOI8-R?B?7snLz8zByiDzxc3Fzs/X?=) Date: Fri, 15 Jan 2010 09:02:25 +0300 Subject: [Pardus-translators] YALI & 2009.1 translations In-Reply-To: References: <201001131555.33383.mete@pardus.org.tr> <201001141250.32312.atolboo@gmail.com> <1919ab0a1001140535m3c2d7dd7lab5ee6be52b9132e@mail.gmail.com> <1919ab0a1001140756i29f468d3j4115cca6228af525@mail.gmail.com> <1919ab0a1001141114s15b94313ma04d97affba38b64@mail.gmail.com> <1919ab0a1001141310m475a89f4vfb620cd89b1b35e2@mail.gmail.com> Message-ID: <1919ab0a1001142202q755a32c3h2d1aa6835dbfaa1b@mail.gmail.com> Thank you :) That's that I want to find out! I hope Pardus 2010 or 2009.2 will have russian versions. With Best Regards, Nikolay Semenov 2010/1/15 Philippe Svetoslavsky > Translators don't have to edit .pot files. When an edition is made on a > .pot file by an application developper, all .po files are automatically > updated accordingly, so that translators only have to deal with these .po > files. > > > 2010/1/14 ??????? ??????? > >> I have seen, that Pardus 2009.1 comes soon, so I have thought, that Yali >> should be updated too. >> And This is my question: >> After updating Yali4.pot should all *.po files be updated? >> > I mean untranslated part. Translation will be made by translators. >> Sorry, but I am not a professional translator - it seems there are only 2 >> active russian users of Pardus (who knows english, of course). >> >> >> 2010/1/14 Philippe Svetoslavsky >> >>> I don't think so. Why are you asking ? >>> >>> >>> 2010/1/14 ??????? ??????? >>> >>>> The last revision (excluding my own) was at 27.10.09 >>>> Is it right? >>>> >>>> >>>> With Best Regards, Nikolay Semenov >>>> >>>> 2010/1/14 Philippe Svetoslavsky >>>> >>>>> Normally, yes. You can check for yourself in Lokalize. >>>>> >>>>> >>>>> 2010/1/14 ??????? ??????? >>>>> >>>>>> So all *.po files have been patched (including ru.po)? >>>>>> >>>>>> 2010/1/14 Philippe Svetoslavsky >>>>>> >>>>>> You don't have to add any strings, they have already been added. >>>>>>> >>>>>>> 2010/1/14 ??????? ??????? >>>>>>> >>>>>>> Thank you! >>>>>>>> But I think we are talking about different problems. >>>>>>>> To work with SVN I use KDESVN - nice app. It is not a problem. >>>>>>>> And as I understand, something has changed in Yali and Yali source >>>>>>>> translations (original .po file) >>>>>>>> Only source translations have changed, but I need to update ru.po >>>>>>>> file - russian translation of Yali. >>>>>>>> So, the question is how using original .po file update my own ru.po >>>>>>>> to add/change some strings in it. >>>>>>>> >>>>>>>> >>>>>>>> With Best Regards, Nikolay Semenov >>>>>>>> >>>>>>>> 2010/1/14 Antoon Tolboom >>>>>>>> >>>>>>>>> On Thursday 14 January 2010 10:47:46 ??????? ??????? wrote: >>>>>>>>> >>>>>>>>> > Thank you :) >>>>>>>>> > But as I usnderstand, I cannot create all translations till >>>>>>>>> 2009.1 :( >>>>>>>>> > I just don't have enough time. >>>>>>>>> > So, my question is how to update ru.po file after updating source >>>>>>>>> file >>>>>>>>> > (english translation) >>>>>>>>> You can update the ru.po file at any time. >>>>>>>>> But for Yali it will only have affect until the next release of the >>>>>>>>> .iso file. >>>>>>>>> For all other applications have alook in: >>>>>>>>> >>>>>>>>> http://worldforum.pardus-linux.nl/index.php?topic=3029.msg14772#msg14772 >>>>>>>>> This is for K3b and maybe also works for other application. >>>>>>>>> > using Lokalize? Or I need somethng different? >>>>>>>>> To make your changes you can use: >>>>>>>>> For KDE4 = Lokalize >>>>>>>>> For KDE3 = KBabel >>>>>>>>> Save changes and use SVN_EDITOR="kwrite" svn ci to send >>>>>>>>> to the database. >>>>>>>>> > >>>>>>>>> > With Best Regards, Nikolay Semenov >>>>>>>>> > >>>>>>>>> >>>>>>>>> regards, >>>>>>>>> Antoon Tolboom >>>>>>>>> _______________________________________________ >>>>>>>>> Pardus-translators mailing list >>>>>>>>> Pardus-translators at pardus.org.tr >>>>>>>>> http://liste.pardus.org.tr/mailman/listinfo/pardus-translators >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Pardus-translators mailing list >>>>>>>> Pardus-translators at pardus.org.tr >>>>>>>> http://liste.pardus.org.tr/mailman/listinfo/pardus-translators >>>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Pardus-translators mailing list >>>>>>> Pardus-translators at pardus.org.tr >>>>>>> http://liste.pardus.org.tr/mailman/listinfo/pardus-translators >>>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Pardus-translators mailing list >>>>>> Pardus-translators at pardus.org.tr >>>>>> http://liste.pardus.org.tr/mailman/listinfo/pardus-translators >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Pardus-translators mailing list >>>>> Pardus-translators at pardus.org.tr >>>>> http://liste.pardus.org.tr/mailman/listinfo/pardus-translators >>>>> >>>> >>>> >>>> _______________________________________________ >>>> Pardus-translators mailing list >>>> Pardus-translators at pardus.org.tr >>>> http://liste.pardus.org.tr/mailman/listinfo/pardus-translators >>>> >>> >>> >>> _______________________________________________ >>> Pardus-translators mailing list >>> Pardus-translators at pardus.org.tr >>> http://liste.pardus.org.tr/mailman/listinfo/pardus-translators >>> >> >> >> _______________________________________________ >> Pardus-translators mailing list >> Pardus-translators at pardus.org.tr >> http://liste.pardus.org.tr/mailman/listinfo/pardus-translators >> > > > _______________________________________________ > Pardus-translators mailing list > Pardus-translators at pardus.org.tr > http://liste.pardus.org.tr/mailman/listinfo/pardus-translators > -------------- next part -------------- An HTML attachment was scrubbed... URL: From onur at pardus.org.tr Fri Jan 15 20:07:50 2010 From: onur at pardus.org.tr (Onur =?UTF-8?B?S8O8w6fDvGs=?=) Date: Fri, 15 Jan 2010 20:07:50 +0200 Subject: [Pardus-translators] Pardus 2009.1 Anthropoides virgo Message-ID: <20100115200750.8d0144c1.onur@pardus.org.tr> Hello, Latest stable release of the 2009 family, Pardus 2009.1 is ready ! You can download this release from Pardus FTP servers; * Multilanguage Installation image ftp://ftp.pardus.org.tr/pub/pardus/kurulan/2009.1/Pardus_2009.1_Anthropoides_virgo_International.iso * Turkish and English Installation image ftp://ftp.pardus.org.tr/pub/pardus/kurulan/2009.1/Pardus_2009.1_Anthropoides_virgo.iso * Turkish and English Live image ftp://ftp.pardus.org.tr/pub/pardus/calisan/2009.1/Pardus_Calisan_2009.1_Anthropoides_virgo.iso Users of Pardus 2009 will automatically switch to 2009.1 with tonight's package updates. Pardus 2009.1 comes with the latest stable KDE release, enhanced hardware support, bigger software archive with up to date packages such as; KDE 4.3.4 Linux kernel 2.6.31.11 OpenOffice.Org 3.1.1.5 Mozilla Firefox 3.5.7 Gimp 2.6.8 Xorg 1.6.5 Python 2.6.4 and many more in just one CD. With the 2009.1 series, Pardus ISO files are generated as Hybrid Images. The same Hybrid Image can be burned to a CD, DVD or dumped to a harddisk like media, like a USB stick. More info can be found in the README file next to ISO images. For a smooth Pardus experience, please verify the checksum of the ISO files after you have downloaded, and if you will burn the images to CD, use quality CD's and burn the CD in DAO mode with 16x speed. Pardus Team thanks to you all who has developed, tested, translated and supported Pardus. -- Onur K???k Knowledge speaks, but wisdom listens From atolboo at gmail.com Sat Jan 16 12:08:59 2010 From: atolboo at gmail.com (Antoon Tolboom) Date: Sat, 16 Jan 2010 11:08:59 +0100 Subject: [Pardus-translators] Packed All *-Managers In-Reply-To: <201001141441.45810.bahadir@pardus.org.tr> References: <201001141441.45810.bahadir@pardus.org.tr> Message-ID: <201001161108.59459.atolboo@gmail.com> On Thursday 14 January 2010 13:41:41 Bahad?r Kandemir wrote: > Hello, > > I've re-packed all manager applications (that i maintain ofc.). All > translations will be in release. > > Thanks everyone! As you can see in http://bugs.pardus.org.tr/show_bug.cgi?id=11219#c13 this has solved the Dutch string problem. THANKS! regards, Antoon Tolboom From ozan at pardus.org.tr Sat Jan 16 20:48:49 2010 From: ozan at pardus.org.tr (=?UTF-8?B?T3phbiDDh2HEn2xheWFu?=) Date: Sat, 16 Jan 2010 20:48:49 +0200 Subject: [Pardus-translators] Frequently asked questions about translations Message-ID: <4B520A11.6070301@pardus.org.tr> Hi, First of all I must say that We really appreciate the contribution that you're giving Pardus as volunteer translators, you're doing a great job by giving support to your native languages! Now I dediced to write down a looong e-mail which could possibly be published as an introductory guide to all translators. Feel free to ask more questions about the parts that are not clear to you. When I complete this text with the answers to your additional questions, I'll make the document public. -- 1. Internationalization (i18n) ------------------------------ Internationalization is the process of designing a software application so that it can be adapted to various languages and regions without engineering changes. This is actually what we are doing when we write the software components like Managers, YALI, Kaptan, sysinfo, etc, so this isn't a process that you're directly involved. In terms of programming, all the strings in an application presented to the user are wrapped with a function call like i18n(), ki18n(), etc. That's all. Say that you're printing a welcome message on the screen in Python: print "Hello" This isn't at all translatable to any language as it doesn't support i18n. But if I import the relevant module and wrap that string by the relevant function like: print i18n("Hello") the text will be replaced by the meaning of "Hello" in the corresponding language when a user runs the application. When the whole software is internationalized, a translation catalogue (a file with an extension .pot) is generated by browsing all the source code files of that software. The catalogue is actually a plain text file which keeps the strings to be translated and their corresponding translations in a 2-line format: .. .. # Some comments about where this string is actually # coming from in terms of source code file and line number msgid "string to be translated 1" msgstr "" and it goes like this. 2. Localization (l10n) ---------------------- Localization is the process of adapting internationalized software for a specific region or language by adding locale-specific components and translating text. Localization is actually what you are doing: Translating the English strings in the translation catalogue to another language. 3. Workflow between i18n and l10n ---------------------------------- - The developer writes its software with i18n support, - Once he/she thinks that it's ready for localization, he/she generates a translation catalogue from it, basically a .pot file and makes it publicly available to you (through SVN in our case), - The translator takes that .pot file and creates a copy of it which he/she calls LANGUAGE.po, e.g. If I'm translating the software to Turkish, I take that .pot file and create a copy of it called tr.po. - I use vi, nano, mcedit, lokalize, kbabel, or another application to edit that tr.po file for translating the strings in it, - Once I think that it's enough for that day, I commit it back to where it belongs in the SVN tree. Some more practical rules and advises are below: - You never touch/modify the .pot file once you copy it as your LANGUAGE.po file, - If there's already a LANGUAGE.po file then it means that somebody has already started working on it OR the developer of the software had created empty LANGUAGE.po files for your convenience. All you have to do is to edit it to fix broken or missing translations and commit it back! 4. What happens when I translate and commit the LANGUAGE.po file to SVN? ------------------------------------------------------------------------- The developers creates a tarball/archive of their project source codes including the po/ directory which contains all of the translation work done by you. Once the application becomes a pisi package and you install/upgrade it on your system, the new translations will immediately be available to you. If you think that you translated all the strings correctly and committed the LANGUAGE.po file to SVN, you may sit back and enjoy seeing your translation work on your screen as you use the related software. 5. Oh, I thought I already completed the translation of Kaptan but there are still English messages in it! ----------------------------------------------------------------------------------------------------------------------- Okay, there could be more than one possible cause for this problem. Let's learn about them: - You really completed the LANGUAGE.po file and committed it but the maintainer of the project wasn't concerned at all to create a new tarball and push that as a pisi update to the repository. So your works aren't reflected at all to the package. Just send an e-mail to the pardus-translators list as early as possible OR fire a bug report in bugzilla to poke us, - You really completed the LANGUAGE.po file and committed it but to the wrong directory under SVN. We'll talk about different directory hierarchies in SVN a little bit later so keep reading, - You really think you're completed the LANGUAGE.po file but actually there are translations which are marked as fuzzy. When a translation is marked as fuzzy, the English string is displayed instead of the fuzzy translation. You have to correct that translation and remove the fuzzy mark in the .po file. Let's see an example: #, fuzzy msgid "Network settings" msgstr "A not-really correct phrase about the original string" As you can see, that translation is marked as fuzzy and you'll just see "Network settings" instead of the not-really correct fuzzy translation. If you're using a graphical tool, re-translating it correctly should be sufficient to mark it as non-fuzzy. If you're using a text editor, just remove that ", fuzzy" from the line above, that's all, - You really completed the LANGUAGE.po file but the developer has just added a new string and you didn't notice it at all. In that case your LANGUAGE.po file will miss the translation for that new string which will cause it to be displayed in English. Just open the LANGUAGE.po file, translate the newly added strings and commit it. 6. At the bottom of my LANGUAGE.po file there a lot of translations all starting with #. What am I supposed to do with them? ----------------------------------------------------------------------------------------------------------------------------- Nothing! Those are old translations that you've made a while ago but which are not currently used by the application because the developer decided to not make them appear on the screen. When the developer updates the POT and PO files (Don't panic we'll talk about that too), the removed strings and their translations will be moved to the bottom of the PO files and be commented out with # characters so that they are not used at all. 7. I sometimes see that the POT file and all the PO files are modified, what does it mean? ------------------------------------------------------------------------------------------- When a developer adds/removes/modifies some strings in its project source codes, he runs an automated script which reflects that change to the POT and PO files: - If there is/are new string(s), you just have to translate it/them in LANGUAGE.po and commit your changes back, - If there is/are removed string(s), its/theirs translation(s) for it/them in the PO file is/are moved to the bottom of the file and each commented out with an # character. You don't have to do anything in this case, - If there is/are modified string(s), its/theirs translation becomes fuzzy. When you open the LANGUAGE.po file with your favourite localization tool or a text editor, you'll see that the relevant translations is/are marked as fuzzy (has a # ,fuzzy line above it). You now have to fix its/their translation(s) to unmark it/them as fuzzy. Note that you'll see the original English strings instead of fuzzy marked translations when you run an application. 8. How can I understand that there are new additions/modifications to the catalogue files? ------------------------------------------------------------------------------------------- First of all you have to follow the pardus-translators and uludag-commits mailing-lists. From time to time, the developers will send e-mails informing you that you have to update your translations for a given project. uludag-commits is a mailing-list that only an automated script is allowed to push commit notifications about repository changes. You must follow that list because if you do so you'll easily notice when someone updates the PO/POT files because he added/removed/modified some strings from them. A typical commit mail which should poke you is something like that: ------------------------------------ Author: ozan.caglayan Date: Thu Jan 14 14:42:38 2010 New Revision: 27511 Modified: trunk/kde/sysinfo/po/ca.po trunk/kde/sysinfo/po/de.po trunk/kde/sysinfo/po/es.po trunk/kde/sysinfo/po/fr.po trunk/kde/sysinfo/po/it.po trunk/kde/sysinfo/po/nl.po trunk/kde/sysinfo/po/pl.po trunk/kde/sysinfo/po/pt_BR.po trunk/kde/sysinfo/po/sv.po trunk/kde/sysinfo/po/sysinfo.pot trunk/kde/sysinfo/po/tr.po Log: Update messages There's one new string to translate ------------------------------------- You can easily see that I updated the PO/POT files because I just added a new string to the sysinfo application about swap memory usage. Now you should update the relevant LANGUAGE.po files to translate that new string and then commit it back to the SVN repository, that's all. So make sure that you follow uludag-commits list to be able to react as immediately as possible to the translation updates. 9. I'm really confused about the branch/ and trunk/ hierarchy in Pardus SVN repository. What are they used for? Where should I commit my translation updates? ---------------------------------------------------------------------------------------- You're basically working in uludag repository (http://svn.pardus.org.tr/uludag) which contains the source codes for Pardus technologies. An SVN project repository is generally divided into three folders: - trunk/ - branches/ - tags/ "trunk" is the directory under which the main project development occurs, "branches" is the directory in which you create various named branches of the main development line, "tags" is a directory of branches that are created, and perhaps destroyed but never changed. Now let's forget about tags directory and focus over the other ones. In trunk, there are several directories for several projects like Kaptan, YALI, comar, pisi, kde, etc. This where the main development takes place. For example, when I found a bug in Kaptan, trunk/kde/kaptan is *generally* the first place where I commit my fix. If I plan to do radical changes to Kaptan e.g. to add different features to it that will be used in Pardus 2011 but which will not appear in Pardus 2009, I create a branch in branches/kde/kaptan called for example 2011 and I continue the development in trunk/kde/kaptan and branches/kde/kaptan/2011 separately. So, If I add a new string to the 2011 branch of Kaptan and update the POT/PO files, you have to update the relevant PO files in branches/kde/kaptan/2011/po directory. Currently we have two main branches for every project: 2009 and Corporate2. Both are active and maintained so you should generally be updating both branches for every project if you see a translation update in uludag-commits. If there are no modifications to the strings in a specific branch of Kaptan, and you continue to improve the current translations in trunk/kde/kaptan, this is the developer's responsibility to take what you changed in trunk/kde/kaptan and apply them over the relevant branches of Kaptan. 10. It is quite possible to see untranslated strings in KDE applications. Since KDE isn't maintained in uludag/ repository, where should I update the translations? ----------------------------------------------------------------------------------------------- Nice question! This is one of the mysteries for translators. From time to time, we add new features to the KDE applications that needs for example a button in the user interface of that application. The PO files for KDE applications are either coming from the package itself or from kde-l10n-LANGUAGE packages in the repository. For example, we recently added a new item in the right-click menu of KMix (The speaker icon in your system tray) which opens pavucontrol for advanced sound settings. The feature was added to KMix shipped within the kdemultimedia package. As kdemultimedia is a base KDE package, all of its PO files comes from kde-l10n-LANGUAGE packages. This is the patch applied to kdemultimedia package which adds that item to KMix: http://svn.pardus.org.tr/pardus/2009/devel/desktop/kde/base/kdemultimedia/files/kmix-add-pavucontrol-shortcut.patch Index: kdemultimedia-4.3.3/kmix/kmixdockwidget.cpp =================================================================== --- kdemultimedia-4.3.3.orig/kmix/kmixdockwidget.cpp +++ kdemultimedia-4.3.3/kmix/kmixdockwidget.cpp @@ -33,6 +33,8 @@ #include #include #include +#include +#include #include #include #include @@ -98,6 +100,13 @@ void KMixDockWidget::createActions() if ( a ) menu->addAction( a ); } + // Add pavucontrol shortcut to the context menu + QAction *paction = actionCollection()->addAction( "run_pavucontrol" ); + paction->setText( i18n ("Advanced Sound Control") ); <-- A new string wrapped by i18n() --> + connect(paction, SIGNAL(triggered(bool) ), SLOT (runPavucontrol() )); + QAction *a1 = actionCollection()->action ("run_pavucontrol" ); + if ( a1 ) menu->addAction( a1 ); + // Put "Select Master Channel" dialog in context menu if ( m_mixer != 0 ) { QAction *action = actionCollection()->addAction( "select_master" ); @@ -158,6 +167,17 @@ void KMixDockWidget::selectMaster() // !! The dialog is modal. Does it delete itself? } +void KMixDockWidget::runPavucontrol() +{ + KProcess *pulse_proc = new KProcess(); + pulse_proc->setProgram("/usr/bin/pavucontrol"); + + if ( pulse_proc->startDetached() == 0 ) { + // Error + KMessageBox::error(0, i18n("Failed launching pavucontrol, make sure the pavucontrol package is correctly installed."), + i18n("Error launching pavucontrol")); <-- Two new strings wrapped by i18n() --> + } +} So when I add this feature to KMix, I also patch the kde-l10n-tr package to add the translations for those 3 new strings. Let's see this patch: http://svn.pardus.org.tr/pardus/2009/devel/desktop/kde/l10n/kde-l10n-tr/files/kmix-add-pavucontrol-i18n.patch Index: kde-l10n-tr-4.3.3/messages/kdemultimedia/kmix.po =================================================================== --- kde-l10n-tr-4.3.3.orig/messages/kdemultimedia/kmix.po +++ kde-l10n-tr-4.3.3/messages/kdemultimedia/kmix.po @@ -712,5 +712,14 @@ msgstr "Ayg?t Ayarlar?" msgid "Mixer" msgstr "Kar??t?r?c?" +msgid "Advanced Sound Control" +msgstr "Geli?mi? Ses Denetimi" + +msgid "Failed launching pavucontrol, make sure the pavucontrol package is correctly installed." +msgstr "pavucontrol ba?lat?lamad?, pavucontrol paketinin y?kl? oldu?undan emin olun." + +msgid "Error launching pavucontrol" +msgstr "pavucontrol ba?lat?lamad?" + #~ msgid "Current Mixer" #~ msgstr "Ge?erli Kar??t?r?c?" The patch is pretty trivial! The main problem is that if you don't dig into the paketler-commits list, you won't notice that right-click menu action addition to KMix until you saw it on your desktop. We're planning an automated notification system for this kind of modifications that'll send an e-mail to pardus-translators which will tell which package you have to patch and what are the added/modified strings in it. As you don't have access to pardus/ repositories for now, you can't directly patch packages but if you attach your translation patches in a bug report that you'll open, we'll apply them as soon as possible to pardus/ repository. Thanks, Ozan Caglayan From patrik at pardus.nu Sat Jan 16 23:56:24 2010 From: patrik at pardus.nu (Patrik Karlsson) Date: Sat, 16 Jan 2010 22:56:24 +0100 (CET) Subject: [Pardus-translators] Frequently asked questions about translations In-Reply-To: <4B520A11.6070301@pardus.org.tr> References: <4B520A11.6070301@pardus.org.tr> Message-ID: <55695.83.248.7.83.1263678984.squirrel@webmail.pardus.nu> >... > Now I dediced to write down a looong e-mail which could possibly be > published as an introductory guide to all translators. >... Thank you for a really nice introduction, now I know some more about the process. I recently ran into a related problem as I was working on a translation. I did a 'svn up', and since some changes were made by the some one else too (the developer, some strings were added/changed) it resulted in a conflict. The first thing I did was to make a 'svn di' of my changes so I could save my local, not commited changes. After that I reviewed the conflict and there was no direct collision so I decided to merge them. That resulted in a po Lokalize could not read, so I deleted the po and made a new 'svn up'. Then I just copy and paste from my recently made diff file. Could you tell us how to handle this kind of situation in a better way? From sw1976de at googlemail.com Sun Jan 17 00:52:39 2010 From: sw1976de at googlemail.com (Stefan Wilhelm) Date: Sat, 16 Jan 2010 23:52:39 +0100 Subject: [Pardus-translators] Frequently asked questions about translations In-Reply-To: <4B520A11.6070301@pardus.org.tr> References: <4B520A11.6070301@pardus.org.tr> Message-ID: Hi Ozan, thanks a lot for your wonderful explanation! >>> 10. It is quite possible to see untranslated strings in KDE applications. >>> Since KDE isn't maintained in uludag/ repository, where should I update the translations? >>> We're planning an automated notification system for this kind of modifications that'll send an e-mail >>> to pardus-translators which will tell which package you have to patch and what are the added/modified strings in it. A automated notification system would be great an very helpful! ------------------------------------------------------------------------ What I?am missing is your HOWTO are the following basics: *svn co https://svn.pardus.org.tr/uludag/trunk/ * *svn ci XX.po* *svn add filename* *export SVN_EDITOR=kwrite* ------------------------------------------------------------------------ And my most importand question: How can I translate the Packagedescribtion shown inside the GUI of PiSi? Is there a single PO file available, or must I translate each single "translation.xml"? Thanks for your effort! --Stefan 2010/1/16 Ozan ?a?layan > Hi, > > First of all I must say that We really appreciate the contribution that > you're giving Pardus as volunteer translators, you're doing > a great job by giving support to your native languages! > > Now I dediced to write down a looong e-mail which could possibly be > published as an introductory guide to all translators. > > Feel free to ask more questions about the parts that are not clear to you. > > When I complete this text with the answers to your additional questions, > I'll make the document public. > > > -- > > 1. Internationalization (i18n) > ------------------------------ > > Internationalization is the process of designing a software application so > that it can be adapted to various languages and regions without engineering > changes. > This is actually what we are doing when we write the software components > like Managers, YALI, Kaptan, sysinfo, etc, so this isn't a process that > you're directly involved. > > In terms of programming, all the strings in an application presented to the > user are wrapped with a function call like i18n(), ki18n(), etc. That's all. > Say that you're printing a welcome message on the screen in Python: > > print "Hello" > > This isn't at all translatable to any language as it doesn't support i18n. > But if I import the relevant module and wrap that string by the relevant > function like: > > print i18n("Hello") > > the text will be replaced by the meaning of "Hello" in the corresponding > language when a user runs the application. > > When the whole software is internationalized, a translation catalogue (a > file with an extension .pot) is generated by browsing all the source code > files of that software. > The catalogue is actually a plain text file which keeps the strings to be > translated and their corresponding translations in a 2-line format: > > .. > .. > > # Some comments about where this string is actually > # coming from in terms of source code file and line number > msgid "string to be translated 1" > msgstr "" > > and it goes like this. > > > 2. Localization (l10n) > ---------------------- > > Localization is the process of adapting internationalized software for a > specific region or language by adding locale-specific components and > translating text. > > Localization is actually what you are doing: Translating the English > strings in the translation catalogue to another language. > > > 3. Workflow between i18n and l10n > ---------------------------------- > > - The developer writes its software with i18n support, > > - Once he/she thinks that it's ready for localization, he/she generates a > translation catalogue from it, basically a .pot file and makes it publicly > available > to you (through SVN in our case), > > - The translator takes that .pot file and creates a copy of it which > he/she calls LANGUAGE.po, e.g. > If I'm translating the software to Turkish, I take that .pot file and > create a copy of it called tr.po. > > - I use vi, nano, mcedit, lokalize, kbabel, or another application to edit > that tr.po file for translating the > strings in it, > > - Once I think that it's enough for that day, I commit it back to where it > belongs in the SVN tree. > > > Some more practical rules and advises are below: > > - You never touch/modify the .pot file once you copy it as your > LANGUAGE.po file, > > - If there's already a LANGUAGE.po file then it means that somebody has > already started working on it OR the > developer of the software had created empty LANGUAGE.po files for your > convenience. > All you have to do is to edit it to fix broken or missing translations > and commit it back! > > > 4. What happens when I translate and commit the LANGUAGE.po file to SVN? > ------------------------------------------------------------------------- > > The developers creates a tarball/archive of their project source codes > including the po/ directory which contains > all of the translation work done by you. Once the application becomes a > pisi package and you install/upgrade it on your system, > the new translations will immediately be available to you. > > If you think that you translated all the strings correctly and committed > the LANGUAGE.po file to SVN, you may sit back > and enjoy seeing your translation work on your screen as you use the > related software. > > > 5. Oh, I thought I already completed the translation of Kaptan but there > are still English messages in it! > > ----------------------------------------------------------------------------------------------------------------------- > > Okay, there could be more than one possible cause for this problem. Let's > learn about them: > > - You really completed the LANGUAGE.po file and committed it but the > maintainer of the project wasn't concerned at all > to create a new tarball and push that as a pisi update to the > repository. So your works aren't reflected at all to > the package. Just send an e-mail to the pardus-translators list as early > as possible OR fire a bug report in bugzilla > to poke us, > > - You really completed the LANGUAGE.po file and committed it but to the > wrong directory under SVN. We'll talk about > different directory hierarchies in SVN a little bit later so keep > reading, > > - You really think you're completed the LANGUAGE.po file but actually > there are translations which are marked as fuzzy. > When a translation is marked as fuzzy, the English string is displayed > instead of the fuzzy translation. You have > to correct that translation and remove the fuzzy mark in the .po file. > Let's see an example: > > #, fuzzy > msgid "Network settings" > msgstr "A not-really correct phrase about the original string" > > As you can see, that translation is marked as fuzzy and you'll just see > "Network settings" instead of the not-really > correct fuzzy translation. If you're using a graphical tool, > re-translating it correctly should be sufficient to mark > it as non-fuzzy. If you're using a text editor, just remove that ", > fuzzy" from the line above, that's all, > > - You really completed the LANGUAGE.po file but the developer has just > added a new string and you didn't notice it at all. > In that case your LANGUAGE.po file will miss the translation for that > new string which will cause it to be displayed in > English. Just open the LANGUAGE.po file, translate the newly added > strings and commit it. > > > 6. At the bottom of my LANGUAGE.po file there a lot of translations all > starting with #. What am I supposed to do with them? > > ----------------------------------------------------------------------------------------------------------------------------- > > Nothing! Those are old translations that you've made a while ago but which > are not currently used by the application because the > developer decided to not make them appear on the screen. > > When the developer updates the POT and PO files (Don't panic we'll talk > about that too), the removed strings and their translations > will be moved to the bottom of the PO files and be commented out with # > characters so that they are not used at all. > > > 7. I sometimes see that the POT file and all the PO files are modified, > what does it mean? > > ------------------------------------------------------------------------------------------- > > When a developer adds/removes/modifies some strings in its project source > codes, he runs an automated script which reflects that > change to the POT and PO files: > > - If there is/are new string(s), you just have to translate it/them in > LANGUAGE.po and commit your changes back, > > - If there is/are removed string(s), its/theirs translation(s) for it/them > in the PO file is/are moved to the bottom of the file > and each commented out with an # character. You don't have to do anything > in this case, > > - If there is/are modified string(s), its/theirs translation becomes > fuzzy. When you open the LANGUAGE.po file with your favourite > localization tool or a text editor, you'll see that the relevant > translations is/are marked as fuzzy (has a # ,fuzzy line above it). > You now have to fix its/their translation(s) to unmark it/them as fuzzy. > > Note that you'll see the original English strings instead of fuzzy marked > translations when you run an application. > > > 8. How can I understand that there are new additions/modifications to the > catalogue files? > > ------------------------------------------------------------------------------------------- > > First of all you have to follow the pardus-translators and uludag-commits > mailing-lists. From time to time, the developers will send > e-mails informing you that you have to update your translations for a given > project. > > uludag-commits is a mailing-list that only an automated script is allowed > to push commit notifications about repository changes. You must > follow that list because if you do so you'll easily notice when someone > updates the PO/POT files because he added/removed/modified some > strings from them. A typical commit mail which should poke you is something > like that: > > ------------------------------------ > Author: ozan.caglayan > Date: Thu Jan 14 14:42:38 2010 > New Revision: 27511 > > Modified: > trunk/kde/sysinfo/po/ca.po > trunk/kde/sysinfo/po/de.po > trunk/kde/sysinfo/po/es.po > trunk/kde/sysinfo/po/fr.po > trunk/kde/sysinfo/po/it.po > trunk/kde/sysinfo/po/nl.po > trunk/kde/sysinfo/po/pl.po > trunk/kde/sysinfo/po/pt_BR.po > trunk/kde/sysinfo/po/sv.po > trunk/kde/sysinfo/po/sysinfo.pot > trunk/kde/sysinfo/po/tr.po > Log: > Update messages > > There's one new string to translate > ------------------------------------- > > You can easily see that I updated the PO/POT files because I just added a > new string to the sysinfo application about swap memory usage. > Now you should update the relevant LANGUAGE.po files to translate that new > string and then commit it back to the SVN repository, that's all. > > So make sure that you follow uludag-commits list to be able to react as > immediately as possible to the translation updates. > > > 9. I'm really confused about the branch/ and trunk/ hierarchy in Pardus SVN > repository. > What are they used for? Where should I commit my translation updates? > > ---------------------------------------------------------------------------------------- > > You're basically working in uludag repository ( > http://svn.pardus.org.tr/uludag) which contains the source codes for > Pardus technologies. > > An SVN project repository is generally divided into three folders: > - trunk/ > - branches/ > - tags/ > > "trunk" is the directory under which the main project development occurs, > "branches" is the directory in which you create various named branches of > the main development line, > "tags" is a directory of branches that are created, and perhaps destroyed > but never changed. > > Now let's forget about tags directory and focus over the other ones. > > In trunk, there are several directories for several projects like Kaptan, > YALI, comar, pisi, kde, etc. This where the main development takes place. > For example, when I found a bug in Kaptan, trunk/kde/kaptan is *generally* > the first place where I commit my fix. > > If I plan to do radical changes to Kaptan e.g. to add different features to > it that will be used in Pardus 2011 but which will not appear > in Pardus 2009, I create a branch in branches/kde/kaptan called for example > 2011 and I continue the development in trunk/kde/kaptan and > branches/kde/kaptan/2011 separately. > > So, If I add a new string to the 2011 branch of Kaptan and update the > POT/PO files, you have to update the relevant PO files in > branches/kde/kaptan/2011/po directory. > > Currently we have two main branches for every project: 2009 and Corporate2. > Both are active and maintained so you should generally be updating > both branches for every project if you see a translation update in > uludag-commits. > > If there are no modifications to the strings in a specific branch of > Kaptan, and you continue to improve the current translations in > trunk/kde/kaptan, > this is the developer's responsibility to take what you changed in > trunk/kde/kaptan and apply them over the relevant branches of Kaptan. > > > 10. It is quite possible to see untranslated strings in KDE applications. > Since KDE isn't maintained in uludag/ repository, where should I update > the translations? > > ----------------------------------------------------------------------------------------------- > > Nice question! This is one of the mysteries for translators. From time to > time, we add new features to the KDE applications that needs for example a > button > in the user interface of that application. > > The PO files for KDE applications are either coming from the package itself > or from kde-l10n-LANGUAGE packages in the repository. > > For example, we recently added a new item in the right-click menu of KMix > (The speaker icon in your system tray) which opens pavucontrol for advanced > sound settings. The feature was added to KMix shipped within the > kdemultimedia package. As kdemultimedia is a base KDE package, all of its PO > files > comes from kde-l10n-LANGUAGE packages. > > This is the patch applied to kdemultimedia package which adds that item to > KMix: > > http://svn.pardus.org.tr/pardus/2009/devel/desktop/kde/base/kdemultimedia/files/kmix-add-pavucontrol-shortcut.patch > > Index: kdemultimedia-4.3.3/kmix/kmixdockwidget.cpp > =================================================================== > --- kdemultimedia-4.3.3.orig/kmix/kmixdockwidget.cpp > +++ kdemultimedia-4.3.3/kmix/kmixdockwidget.cpp > @@ -33,6 +33,8 @@ > #include > #include > #include > +#include > +#include > #include > #include > #include > @@ -98,6 +100,13 @@ void KMixDockWidget::createActions() > if ( a ) menu->addAction( a ); > } > > + // Add pavucontrol shortcut to the context menu > + QAction *paction = actionCollection()->addAction( "run_pavucontrol" ); > + paction->setText( i18n ("Advanced Sound Control") ); > <-- A new string wrapped by i18n() --> > + connect(paction, SIGNAL(triggered(bool) ), SLOT (runPavucontrol() )); > + QAction *a1 = actionCollection()->action ("run_pavucontrol" ); > + if ( a1 ) menu->addAction( a1 ); > + > // Put "Select Master Channel" dialog in context menu > if ( m_mixer != 0 ) { > QAction *action = actionCollection()->addAction( "select_master" ); > @@ -158,6 +167,17 @@ void KMixDockWidget::selectMaster() > // !! The dialog is modal. Does it delete itself? > } > > +void KMixDockWidget::runPavucontrol() > +{ > + KProcess *pulse_proc = new KProcess(); > + pulse_proc->setProgram("/usr/bin/pavucontrol"); > + > + if ( pulse_proc->startDetached() == 0 ) { > + // Error > + KMessageBox::error(0, i18n("Failed launching pavucontrol, make > sure the pavucontrol package is correctly installed."), > + i18n("Error launching pavucontrol")); > <-- Two new strings wrapped by i18n() --> > + } > +} > > > So when I add this feature to KMix, I also patch the kde-l10n-tr package to > add the translations for those 3 new strings. Let's see > this patch: > > http://svn.pardus.org.tr/pardus/2009/devel/desktop/kde/l10n/kde-l10n-tr/files/kmix-add-pavucontrol-i18n.patch > > Index: kde-l10n-tr-4.3.3/messages/kdemultimedia/kmix.po > =================================================================== > --- kde-l10n-tr-4.3.3.orig/messages/kdemultimedia/kmix.po > +++ kde-l10n-tr-4.3.3/messages/kdemultimedia/kmix.po > @@ -712,5 +712,14 @@ msgstr "Ayg?t Ayarlar?" > msgid "Mixer" > msgstr "Kar??t?r?c?" > > +msgid "Advanced Sound Control" > +msgstr "Geli?mi? Ses Denetimi" > + > +msgid "Failed launching pavucontrol, make sure the pavucontrol package is > correctly installed." > +msgstr "pavucontrol ba?lat?lamad?, pavucontrol paketinin y?kl? oldu?undan > emin olun." > + > +msgid "Error launching pavucontrol" > +msgstr "pavucontrol ba?lat?lamad?" > + > #~ msgid "Current Mixer" > #~ msgstr "Ge?erli Kar??t?r?c?" > > The patch is pretty trivial! > > The main problem is that if you don't dig into the paketler-commits list, > you won't notice that right-click menu action addition to KMix > until you saw it on your desktop. We're planning an automated notification > system for this kind of modifications that'll send an e-mail > to pardus-translators which will tell which package you have to patch and > what are the added/modified strings in it. > > As you don't have access to pardus/ repositories for now, you can't > directly patch packages but if you attach your translation patches in a > bug report that you'll open, we'll apply them as soon as possible to > pardus/ repository. > > > Thanks, > Ozan Caglayan > > _______________________________________________ > Pardus-translators mailing list > Pardus-translators at pardus.org.tr > http://liste.pardus.org.tr/mailman/listinfo/pardus-translators -------------- next part -------------- An HTML attachment was scrubbed... URL: From ozan at pardus.org.tr Sun Jan 17 10:47:07 2010 From: ozan at pardus.org.tr (=?UTF-8?B?T3phbiDDh2HEn2xheWFu?=) Date: Sun, 17 Jan 2010 10:47:07 +0200 Subject: [Pardus-translators] Frequently asked questions about translations In-Reply-To: References: <4B520A11.6070301@pardus.org.tr> Message-ID: <4B52CE8B.2010004@pardus.org.tr> Stefan Wilhelm wrote: > > And my most importand question: > > How can I translate the Packagedescribtion shown inside the GUI of PiSi? > Is there a single PO file available, or must I translate each single > "translation.xml"? > > Thanks for your effort! > > --Stefan > Hi, I totally forgot to explain about that. Every package has a translations.xml file which you can translate the package summary & description. Once upon a time, there were a script which were ran periodically to generate a whole large PO file from all the translations.xml. Once people updates that PO file, we were updating the translations.xml from that large PO file. But we didn't use that method for now I don't know why. We need an easy way to translate package summary & descriptions, I'll think about it. From ozan at pardus.org.tr Sun Jan 17 10:56:28 2010 From: ozan at pardus.org.tr (=?UTF-8?B?T3phbiDDh2HEn2xheWFu?=) Date: Sun, 17 Jan 2010 10:56:28 +0200 Subject: [Pardus-translators] Frequently asked questions about translations In-Reply-To: <55695.83.248.7.83.1263678984.squirrel@webmail.pardus.nu> References: <4B520A11.6070301@pardus.org.tr> <55695.83.248.7.83.1263678984.squirrel@webmail.pardus.nu> Message-ID: <4B52D0BC.6080302@pardus.org.tr> Patrik Karlsson wrote: > Thank you for a really nice introduction, now I know some more about the > process. > > I recently ran into a related problem as I was working on a translation. > > I did a 'svn up', and since some changes were made by the some one else > too (the developer, some strings were added/changed) it resulted in a > conflict. > The first thing I did was to make a 'svn di' of my changes so I could save > my local, not commited changes. After that I reviewed the conflict and > there was no direct collision so I decided to merge them. That resulted in > a po Lokalize could not read, so I deleted the po and made a new 'svn up'. > Then I just copy and paste from my recently made diff file. > > Could you tell us how to handle this kind of situation in a better way? First of all to avoid these kind of problems always run "svn up" before starting to work, and always commit your changes when you're done. If there's no direct collision after svn up, the conflicted file will be marked with a G: $ svn up U po/tr.po U po/it.po U po/sv.po U po/es.po G po/de.po something like that. This won't avoid you from committing your local changes. If there's a real conflict the file will be marked with a C and SVN will ask you what to do when you ran svn up.: $ svn up U po/tr.po Conflict discovered in 'po/es.po'. Select: (p) postpone, (df) diff-full, (e) edit, (s) show all options: s (p) postpone - mark the conflict to be resolved later (df) diff-full - show all changes made to merged file (e) edit - change merged file in an editor (r) resolved - accept merged version of file (mf) mine-full - accept my version of entire file (ignore their changes) (tf) theirs-full - accept their version of entire file (lose my changes) (l) launch - launch external tool to resolve conflict (s) show all - show this list If you choose postpone, you'll have to resolve the conflict later diff-full will show the total diff to the file edit is the one you'll choose to resolve the conflict. It will show both your local changes and the committed changes to the file separating them with lines like: <<<<<<<<<<<<<<< merge.right.rXXXXX >>>>>>>>>>>>>>> working lines between 'working' marks are the local changes you have on your computer, the merge.right ones are the committed and conflicted changes. You have to decide which ones to use and merge them by removing all that >>>>>>>>>> <<<<<<<<<< lines. Once you cleaned up those lines and fusioned the changes manually with your hand, you can save&exit from edit mode, and then press 'r' to say that "hey I'm resolved the conflict". Now you'll be able to commit your fusioned changes back to the repository if you run "svn ci". mine-full discards all the committed-and-conflicted changes and uses your local version as the new file, theirs-full discards all your changes and uses the committed version as the new file. From atolboo at gmail.com Sun Jan 17 11:56:51 2010 From: atolboo at gmail.com (Antoon Tolboom) Date: Sun, 17 Jan 2010 10:56:51 +0100 Subject: [Pardus-translators] Frequently asked questions about translations In-Reply-To: <4B520A11.6070301@pardus.org.tr> References: <4B520A11.6070301@pardus.org.tr> Message-ID: <201001171056.51154.atolboo@gmail.com> Thanks for this explanation. On Saturday 16 January 2010 19:48:49 Ozan ?a?layan wrote: > Now I dediced to write down a looong e-mail which could possibly be > published as an introductory guide to all translators. > > Feel free to ask more questions about the parts that are not clear to you. > > When I complete this text with the answers to your additional questions, > I'll make the document public. > I agree with Stefan Wilhelm that: svn co https://svn.pardus.org.tr/uludag/......./ svn ci XX.po svn add filename export SVN_EDITOR=kwrite and/or SVN_EDITOR="kwrite" svn ci (<< I always use this one) and the associated specification (f.i. Dutch language update of /trunk/....) should be included in the introduction guide/manual. And another chapter is the "Localized Firefox bookmarks" in http://svn.pardus.org.tr/pardus/2009/devel/network/web/firefox/files/pardus/. I know this has nothing to do with translations but with localization. Antoon Tolboom From ozan at pardus.org.tr Sun Jan 17 17:21:54 2010 From: ozan at pardus.org.tr (=?UTF-8?B?T3phbiDDh2HEn2xheWFu?=) Date: Sun, 17 Jan 2010 17:21:54 +0200 Subject: [Pardus-translators] Frequently asked questions about translations In-Reply-To: <201001171056.51154.atolboo@gmail.com> References: <4B520A11.6070301@pardus.org.tr> <201001171056.51154.atolboo@gmail.com> Message-ID: <4B532B12.1010204@pardus.org.tr> Antoon Tolboom wrote: > Thanks for this explanation. > I agree with Stefan Wilhelm that: > svn co https://svn.pardus.org.tr/uludag/......./ > svn ci XX.po > svn add filename > export SVN_EDITOR=kwrite > and/or > SVN_EDITOR="kwrite" svn ci (<< I always use this one) > and the associated specification (f.i. Dutch language update of /trunk/....) > should be included in the introduction guide/manual. OK I'll write down an introductory SVN section, too. > > And another chapter is the "Localized Firefox bookmarks" in http://svn.pardus.org.tr/pardus/2009/devel/network/web/firefox/files/pardus/. Actually this can be explained in KDE/KMix example part. From sw1976de at googlemail.com Sun Jan 17 18:10:09 2010 From: sw1976de at googlemail.com (Stefan Wilhelm) Date: Sun, 17 Jan 2010 17:10:09 +0100 Subject: [Pardus-translators] Frequently asked questions about translations In-Reply-To: <4B52CE8B.2010004@pardus.org.tr> References: <4B520A11.6070301@pardus.org.tr> <4B52CE8B.2010004@pardus.org.tr> Message-ID: Hi Ozan, >>>>> Hi, I totally forgot to explain about that. Really no problem! :-) >>>>> We need an easy way to translate package summary & descriptions, I'll think about it. Could you please keep us informed about this progress? That would be fine! At least the geman translator-team would like to translate the package describtions. >>>>> to generate a whole large PO file from all the translations.xml. Can You tell me/us, where we can find this large PO-file? Is it save ore helpfull when we start working on that "large" PO-file, or should we better wait for your solution? We of don?t want to waste our time, of course. :o) Thank you again for your friendly support! Cheers, Stefan 2010/1/17 Ozan ?a?layan > Stefan Wilhelm wrote: > > > > > And my most importand question: > > > > How can I translate the Packagedescribtion shown inside the GUI of PiSi? > > Is there a single PO file available, or must I translate each single > > "translation.xml"? > > > > Thanks for your effort! > > > > --Stefan > > > > Hi, I totally forgot to explain about that. > > Every package has a translations.xml file which you can translate the > package summary & description. > > Once upon a time, there were a script which were ran periodically to > generate a whole large PO file from > all the translations.xml. Once people updates that PO file, we were > updating the translations.xml from that > large PO file. But we didn't use that method for now I don't know why. > > We need an easy way to translate package summary & descriptions, I'll think > about it. > _______________________________________________ > Pardus-translators mailing list > Pardus-translators at pardus.org.tr > http://liste.pardus.org.tr/mailman/listinfo/pardus-translators > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sw1976de at googlemail.com Sun Jan 17 18:39:46 2010 From: sw1976de at googlemail.com (Stefan Wilhelm) Date: Sun, 17 Jan 2010 17:39:46 +0100 Subject: [Pardus-translators] Frequently asked questions about translations In-Reply-To: References: <4B520A11.6070301@pardus.org.tr> <4B52CE8B.2010004@pardus.org.tr> Message-ID: Hi Ozan, another translation question! Actuallay in the Firefox Links of a fresh german Pardus installation, there is a Bookmark to www.pardus-linux.de This is ridiculous because this page is still promoting Pardus 2008.2! :-( Can you tell me, who is responsible for http://www.pardus.org.tr/de/ Maybe we can translate the text of the englisch site into german and send this text to the right person! BTW: The Site http://www.pardus.org.tr/eng/ is *still *providing Pardus 2009 for download. I?am missing a list of contact names who is the best contact for a few generall things. Would be great, if the Pardus Developer-Team could provide such list for the public or at least for the developers oder translators. E.g. I was sending a text thru the available Contact form ( http://www.pardus.org.tr/eng/contact/ ) and i was getting a turkish automaitic info text answer-Email whitch was senseless for me. Bye, Stefan -------------- next part -------------- An HTML attachment was scrubbed... URL: From patrik at pardus.nu Thu Jan 28 18:54:57 2010 From: patrik at pardus.nu (Patrik Karlsson) Date: Thu, 28 Jan 2010 17:54:57 +0100 Subject: [Pardus-translators] Request of a Swedish /pspec-translations/po/ Message-ID: <201001281754.57068.patrik@pardus.nu> Hi, I would like to have a sv.po for the pspec-translations. From ozan at pardus.org.tr Thu Jan 28 19:14:00 2010 From: ozan at pardus.org.tr (=?UTF-8?B?T3phbiDDh2HEn2xheWFu?=) Date: Thu, 28 Jan 2010 19:14:00 +0200 Subject: [Pardus-translators] Request of a Swedish /pspec-translations/po/ In-Reply-To: <201001281754.57068.patrik@pardus.nu> References: <201001281754.57068.patrik@pardus.nu> Message-ID: <4B61C5D8.8000303@pardus.org.tr> Patrik Karlsson wrote: > Hi, > I would like to have a sv.po for the pspec-translations. Currently that mechanism isn't online e.g. we don't update package translations from .po files. I'd like to keep that translations in a separate package like pspec-translations, and update that package instead of updating translations.xml files. Be patient for a while before starting package translations, Regards, From patrik at pardus.nu Thu Jan 28 19:19:43 2010 From: patrik at pardus.nu (Patrik Karlsson) Date: Thu, 28 Jan 2010 18:19:43 +0100 Subject: [Pardus-translators] Request of a Swedish /pspec-translations/po/ In-Reply-To: <4B61C5D8.8000303@pardus.org.tr> References: <201001281754.57068.patrik@pardus.nu> <4B61C5D8.8000303@pardus.org.tr> Message-ID: <201001281819.43488.patrik@pardus.nu> torsdagen den 28 januari 2010 18.14.00 skrev Ozan ?a?layan: > Patrik Karlsson wrote: > > Hi, > > I would like to have a sv.po for the pspec-translations. > > Currently that mechanism isn't online e.g. we don't update package > translations from .po files. > > I'd like to keep that translations in a separate package like > pspec-translations, and update that package instead of updating > translations.xml files. > > Be patient for a while before starting package translations, That is ok, I will wait.