From taljurf at fedoraproject.org Fri Jan 1 18:01:12 2010 From: taljurf at fedoraproject.org (Tareq Al Jurf) Date: Fri, 1 Jan 2010 21:01:12 +0300 Subject: Patch a po? Message-ID: <12d8a2fa1001011001m4fb151ccj9c3ce8d199dc6f68@mail.gmail.com> How can i apply a patch to a po file? Regards -- Tareq Al Jurf Fedora Ambassador Riyadh, Saudi Arabia taljurf at fedoraproject.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From noriko at redhat.com Mon Jan 4 00:47:12 2010 From: noriko at redhat.com (Noriko Mizumoto) Date: Mon, 04 Jan 2010 10:47:12 +1000 Subject: Updated Fedora 13 Schedules In-Reply-To: <4B3A3255.4090901@redhat.com> References: <4B3A3255.4090901@redhat.com> Message-ID: <4B413A90.40409@redhat.com> John Poelstra ????????: > I have updated the schedules based on our meeting on 2009-12-22. Let me > know if there are any parts of it that still need to be adjusted by > telling me the task number and schedule you are referring to. Thank you so much for your great work. Just a bit, but it must be straight forward :-) > -= Translation =- > http://poelstra.fedorapeople.org/schedules/f-13/f-13-trans-tasks.html Existing Translate Final Release Banners Fri 2010-04-30 Fri 2010-05-07 Deadline: Final Release Banners Fri 2010-05-07 Fri 2010-05-07 => Please remove them * We have found that Banners usually does not require Translation. Mostly Banners are simply images. New Translation Deadline: GA Announcement Fri 2010-05-07 Fri 2010-05-07 => Please add * Entry missing. noriko From noriko at redhat.com Tue Jan 5 05:43:13 2010 From: noriko at redhat.com (Noriko Mizumoto) Date: Tue, 05 Jan 2010 15:43:13 +1000 Subject: QA test for L10N Message-ID: <4B42D171.9070703@redhat.com> Hi translators and testers Regarding the following task entries of F13, recently I have contacted QA team (f-test-l) for live image creation and heard positive replies. So I like to reopen different thread to discuss entire picture with QA team and L10N team together. Please throw your idea and improve this event better. If any doubt/question, pls do ask. As you can notice, it is my bad expressing this in several way such as 'QA test for L10N', 'Review task', 'QA event' etc. What is the best to describe? For newer translators and testers, this event has just started since Fedora 12. The background is that translators are usually working on PO file only and unable to check the quality of translation how it appears in GUI. Thus to allow translators to review translation in GUI for high quality translation, this event has been added with FESCo approval. [f13-trans-tasks] * Build F-13 collection packages for all language translators (Wed 2010-03-03 Fri 2010-03-05) * Review and correct software translation in built UI (Mon 2010-03-08 Tue 2010-03-16) [Steps] 1. Remind devel-announce for building F13 packages with latest translation by 2010-03-04. 2. QA team places nightly-compose of 2010-03-05 at specific location, and make it available during review period. 3. Translators and testers start QA test (review) during 2010-03-08 and 2010-03-16. 4. Packagers fix bugs to include them into final build for GA. I am thinking to create simple packages list with how-to-access-gui. Any finding which needs packager's action should be reported as a bug [1]. [1]:https://bugzilla.redhat.com/show_bug.cgi?id=522431 noriko From noriko at redhat.com Tue Jan 5 06:06:04 2010 From: noriko at redhat.com (Noriko Mizumoto) Date: Tue, 05 Jan 2010 16:06:04 +1000 Subject: Page not found Message-ID: <4B42D6CC.3040404@redhat.com> Hi, Some translators have been experiencing the problem 'Page not found' when viewing/downloading system-config-firewall. There was some discussion on #fedora-admin on irc today. This problem has been looked in, and to be notified once fixed [1]. [1]:https://fedorahosted.org/fedora-infrastructure/ticket/1872#comment:2 noriko From domingobecker at gmail.com Tue Jan 5 12:05:43 2010 From: domingobecker at gmail.com (Domingo Becker) Date: Tue, 5 Jan 2010 09:05:43 -0300 Subject: untranslated component for F12 and F13 Message-ID: <4818cd81001050405h3c49d658u253e8a301f6cb548@mail.gmail.com> There are some untranslated component for F12 [1] and F13 [2] for the Spanish language, that I guess it's an error. For other releases, when activating the next release in Transifex, the packages that will be present in that release reuse translations from the last one. But for F13, some of these packages passed from 100% translated to 0% (untranslated). I didn't report it before because I thought Transifex would be updated and this issue would be probably solved. But the problem is there since last year. [1] https://translate.fedoraproject.org/languages/es/collection/fedora/fedora-12/ [2] https://translate.fedoraproject.org/languages/es/collection/fedora/fedora-13/ kind regards Domingo Becker (es) From jlaska at redhat.com Tue Jan 5 13:48:38 2010 From: jlaska at redhat.com (James Laska) Date: Tue, 05 Jan 2010 08:48:38 -0500 Subject: QA test for L10N In-Reply-To: <4B42D171.9070703@redhat.com> References: <4B42D171.9070703@redhat.com> Message-ID: <1262699318.2401.44.camel@localhost> On Tue, 2010-01-05 at 15:43 +1000, Noriko Mizumoto wrote: > Hi translators and testers > > Regarding the following task entries of F13, recently I have contacted > QA team (f-test-l) for live image creation and heard positive replies. > So I like to reopen different thread to discuss entire picture with QA > team and L10N team together. Please throw your idea and improve this > event better. If any doubt/question, pls do ask. My first thought when seeing the previous thread where to ask whether your testing instructions were documented already. We have test cases for the Fedora 12 i18n test day [1], so if this is a common sequence of tasks that you'd like to encourage others to follow, this might help. If you have more than just a series of test cases (perhaps a higher strategy, organization and pass/fail criteria), I might suggest a lightweight test plan [2]. > As you can notice, it is my bad expressing this in several way such as > 'QA test for L10N', 'Review task', 'QA event' etc. What is the best to > describe? We hosted i18n focused Test Days in previous releases and I believe they worked rather well to organize folks around a common goal. I don't see any problems using that vehicle for Fedora 13 if there is a sufficient amount of work that can be distributed. If you'd like more information, take a look at https://fedoraproject.org/wiki/QA/SOP_Test_Day_management. We'll be happy to assist in setting up an event. > For newer translators and testers, this event has just started since > Fedora 12. The background is that translators are usually working on PO > file only and unable to check the quality of translation how it appears > in GUI. Thus to allow translators to review translation in GUI for high > quality translation, this event has been added with FESCo approval. > > [f13-trans-tasks] > * Build F-13 collection packages for all language translators > (Wed 2010-03-03 Fri 2010-03-05) > > * Review and correct software translation in built UI > (Mon 2010-03-08 Tue 2010-03-16) > > [Steps] > 1. Remind devel-announce for building F13 packages with latest > translation by 2010-03-04. > 2. QA team places nightly-compose of 2010-03-05 at specific location, > and make it available during review period. > 3. Translators and testers start QA test (review) during 2010-03-08 and > 2010-03-16. > 4. Packagers fix bugs to include them into final build for GA. > > I am thinking to create simple packages list with how-to-access-gui. Any > finding which needs packager's action should be reported as a bug [1]. Would this be useful information to document on the wiki? Perhaps as a QA [3] or L10N SOP? Thanks, James [1] https://fedoraproject.org/wiki/Category:I18n_Test_Cases [2] http://fedoraproject.org/wiki/Category:Test_Plans [3] https://fedoraproject.org/wiki/Category:QA_SOPs -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: From stickster at gmail.com Tue Jan 5 14:14:49 2010 From: stickster at gmail.com (Paul W. Frields) Date: Tue, 5 Jan 2010 09:14:49 -0500 Subject: Transifex upgrade In-Reply-To: <4B2052B3.6080005@redhat.com> References: <4B0B62F8.5090601@redhat.com> <4B14BEDA.9030504@gmail.com> <4B15C3A7.2020405@redhat.com> <6d4237680912012347t5f53cc1apba4e5682465b3e84@mail.gmail.com> <4B174117.7070606@redhat.com> <6d4237680912040051k15738b01x4b310e36a47eb83d@mail.gmail.com> <20091209235809.GH9741@victoria.internal.frields.org> <4B2052B3.6080005@redhat.com> Message-ID: <20100105141449.GJ4449@victoria.internal.frields.org> On Thu, Dec 10, 2009 at 11:45:23AM +1000, Noriko Mizumoto wrote: > Paul W. Frields ????????: > >Diego posted the summary of what needs to be done here: > > > >https://fedorahosted.org/fedora-infrastructure/ticket/1455#comment:10 > > > >In short, we need a few people to step up and help with the process > >Diego posted. > > > >We already do have a L10n Admin group[1] that should be overseeing and > >managing this process, to ensure a successful rollout for translators. > >Their charter is to maintain the infrastructure for translators, and > >this clearly falls into that area. I've heard from two of the people > >in that group that they can't do all this work themselves, but haven't > >heard from Ankit or Asgeir about it. > > > >What I would suggest is that Diego should help with bullet #4 on that > >list, as it probably requires the greatest degree of specific > >technical knowledge, in this case a database upgrade. The rest of the > >work on that ticket could likely be done entirely by the remainder of > >the team, maybe with limited input from Diego. It would be helpful > >for Asgeir or Ankit to help manage this set of tasks in collaboration > >with Diego, who has appropriate package access. (I'm cc'ing Ignacio > >directly as well, so he can add appropriate CVS access for any other > >people who are willing to help maintain the EL-5 package used on our > >Infrastructure.) > > > >Without help, it's doubtful there will be a new Transifex rolled out, > >and that means some of the problems people are experiencing will > >continue, even though they're already fixed upstream. I'm cc'ing the > >docs, devel, and infrastructure lists to see if any of the people in > >areas well served by translators are willing to help see this project > >through. It's time to pull together, guys, and see if we can help the > >translators who give so much across the whole Fedora Project. > > >[1] https://fedoraproject.org/wiki/L10N/Tools#Website > > > Thanks Paul, > We are very much appreciated if any of you guys can give a hand to > L10n team this time, as by coincidence both of Ankit and Asgeir are > having leave (most likely traveling) and they might not be able have > connection at all. > > I like to add brother i18n team as well. Quick note -- if you look at the Trac ticket: https://fedorahosted.org/fedora-infrastructure/ticket/1455 ...you'll see that thanks to a number of excellent Fedorans including Diego, Rakesh, Toshio, Ricky, Jens, and Dimitris, the upgrade is proceeding apace. There was a short break for the holidays but it looks like we're on our way to an upgraded Transifex. Thank you to everyone who continues to help with this. As of the latest update: https://fedorahosted.org/fedora-infrastructure/ticket/1455#comment:33 Toshio has some questions that need to be resolved to continue the upgrade process. If you want to get involved, visit the ticket and then stop by #fedora-admin if you are able to lend a hand. -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug From poelstra at redhat.com Tue Jan 5 21:44:09 2010 From: poelstra at redhat.com (John Poelstra) Date: Tue, 05 Jan 2010 13:44:09 -0800 Subject: Updated Fedora 13 Schedules In-Reply-To: <4B413A90.40409@redhat.com> References: <4B3A3255.4090901@redhat.com> <4B413A90.40409@redhat.com> Message-ID: <4B43B2A9.1060203@redhat.com> Noriko Mizumoto said the following on 01/03/2010 04:47 PM Pacific Time: > John Poelstra ????????: >> I have updated the schedules based on our meeting on 2009-12-22. Let >> me know if there are any parts of it that still need to be adjusted by >> telling me the task number and schedule you are referring to. > > Thank you so much for your great work. > Just a bit, but it must be straight forward :-) > >> -= Translation =- >> http://poelstra.fedorapeople.org/schedules/f-13/f-13-trans-tasks.html > > Existing > Translate Final Release Banners Fri 2010-04-30 Fri 2010-05-07 > Deadline: Final Release Banners Fri 2010-05-07 Fri 2010-05-07 > => Please remove them > * We have found that Banners usually does not require Translation. > Mostly Banners are simply images. > > New > Translation Deadline: GA Announcement Fri 2010-05-07 Fri 2010-05-07 > => Please add > * Entry missing. > All changes made. John From yulia.poyarkova at redhat.com Tue Jan 5 22:23:33 2010 From: yulia.poyarkova at redhat.com (Yuliya Poyarkova) Date: Wed, 06 Jan 2010 09:23:33 +1100 Subject: untranslated component for F12 and F13 In-Reply-To: <4818cd81001050405h3c49d658u253e8a301f6cb548@mail.gmail.com> References: <4818cd81001050405h3c49d658u253e8a301f6cb548@mail.gmail.com> Message-ID: <4B43BBE5.3070702@redhat.com> Hi Domingo, Are you referring to comps, desktop-backgrounds, and other packages? Looks like it's not limited to Spanish, I also noticed that. Hope previous translation can be restored, there is a lot of work put into that. Yulia (ru) > There are some untranslated component for F12 [1] and F13 [2] for the > Spanish language, that I guess it's an error. > For other releases, when activating the next release in Transifex, the > packages that will be present in that release reuse translations from > the last one. > But for F13, some of these packages passed from 100% translated to 0% > (untranslated). > I didn't report it before because I thought Transifex would be updated > and this issue would be probably solved. > But the problem is there since last year. > > [1] https://translate.fedoraproject.org/languages/es/collection/fedora/fedora-12/ > > [2] https://translate.fedoraproject.org/languages/es/collection/fedora/fedora-13/ > > kind regards > > Domingo Becker (es) > > -- > Fedora-trans-list mailing list > Fedora-trans-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-trans-list > -- Yuliya Poyarkova Red Hat APAC http://apac.redhat.com/disclaimer From piotrdrag at gmail.com Tue Jan 5 22:33:12 2010 From: piotrdrag at gmail.com (=?UTF-8?B?UGlvdHIgRHLEhWc=?=) Date: Tue, 05 Jan 2010 23:33:12 +0100 Subject: untranslated component for F12 and F13 In-Reply-To: <4B43BBE5.3070702@redhat.com> References: <4818cd81001050405h3c49d658u253e8a301f6cb548@mail.gmail.com> <4B43BBE5.3070702@redhat.com> Message-ID: <4B43BE28.4030008@gmail.com> W dniu 05.01.2010 23:23, Yuliya Poyarkova pisze: > Are you referring to comps, desktop-backgrounds, and other packages? > Looks like it's not limited to Spanish, I also noticed that. > Hope previous translation can be restored, there is a lot of work put > into that. > None of the translations are lost, they are still safe in repositories. We just have a problem with connection from Transifex to CVS repos. Ticket on Infra's Trac should help probably. -- Piotr Dr?g http://raven.pmail.pl From noriko at redhat.com Tue Jan 5 23:58:52 2010 From: noriko at redhat.com (Noriko Mizumoto) Date: Wed, 06 Jan 2010 09:58:52 +1000 Subject: QA test for L10N In-Reply-To: <1262699318.2401.44.camel@localhost> References: <4B42D171.9070703@redhat.com> <1262699318.2401.44.camel@localhost> Message-ID: <4B43D23C.1060905@redhat.com> James Laska ????????: > On Tue, 2010-01-05 at 15:43 +1000, Noriko Mizumoto wrote: >> Hi translators and testers >> >> Regarding the following task entries of F13, recently I have contacted >> QA team (f-test-l) for live image creation and heard positive replies. >> So I like to reopen different thread to discuss entire picture with QA >> team and L10N team together. Please throw your idea and improve this >> event better. If any doubt/question, pls do ask. > > My first thought when seeing the previous thread where to ask whether > your testing instructions were documented already. We have test cases > for the Fedora 12 i18n test day [1], so if this is a common sequence of > tasks that you'd like to encourage others to follow, this might help. > If you have more than just a series of test cases (perhaps a higher > strategy, organization and pass/fail criteria), I might suggest a > lightweight test plan [2]. > We only had very tiny window to organize this review event for F12, and there was no instruction documented. I joined F12 i18n test day and learned all well documented. i18n test day is good example and l10n should have similar documentation. For F13, something like "https://fedoraproject.org/wiki/Category:L10n_Test_Cases" to be written. L10n test day (this is our review process) is different from i18n. My original mail has followed " Template:QA/Test Plan" [1]. [1]:https://www.redhat.com/archives/fedora-test-list/2009-December/msg00352.html >> As you can notice, it is my bad expressing this in several way such as >> 'QA test for L10N', 'Review task', 'QA event' etc. What is the best to >> describe? > > We hosted i18n focused Test Days in previous releases and I believe they > worked rather well to organize folks around a common goal. I don't see > any problems using that vehicle for Fedora 13 if there is a sufficient > amount of work that can be distributed. If you'd like more information, > take a look at > https://fedoraproject.org/wiki/QA/SOP_Test_Day_management. We'll be > happy to assist in setting up an event. Thanks for the pointer! Here is L10n SOP. 1 Get people on board => Translators and testers 2 Set a date => 2010-03-08 to 2010-03-16 3 Create the Wiki page o 3.1 Create test cases => I do have some draft not published yet (how-to-access-gui) o 3.2 Set up the results table => it was bug tracker for F12 4 Build a live CD => We need "nightly compose 2010-03-05" somewhere accessible between 2010-03-08 to 2010-03-16 5 Promote the Test Day => reminder of task schedule to be sent by John 6 Pre-event reminder => same the above 7 Update Test_Day:Current => same with 3.2 bug tracker 8 Do a post-event review => any idea? noriko > >> For newer translators and testers, this event has just started since >> Fedora 12. The background is that translators are usually working on PO >> file only and unable to check the quality of translation how it appears >> in GUI. Thus to allow translators to review translation in GUI for high >> quality translation, this event has been added with FESCo approval. >> >> [f13-trans-tasks] >> * Build F-13 collection packages for all language translators >> (Wed 2010-03-03 Fri 2010-03-05) >> >> * Review and correct software translation in built UI >> (Mon 2010-03-08 Tue 2010-03-16) >> >> [Steps] >> 1. Remind devel-announce for building F13 packages with latest >> translation by 2010-03-04. >> 2. QA team places nightly-compose of 2010-03-05 at specific location, >> and make it available during review period. >> 3. Translators and testers start QA test (review) during 2010-03-08 and >> 2010-03-16. >> 4. Packagers fix bugs to include them into final build for GA. >> >> I am thinking to create simple packages list with how-to-access-gui. Any >> finding which needs packager's action should be reported as a bug [1]. > > Would this be useful information to document on the wiki? Perhaps as a > QA [3] or L10N SOP? > > Thanks, > James > > [1] https://fedoraproject.org/wiki/Category:I18n_Test_Cases > [2] http://fedoraproject.org/wiki/Category:Test_Plans > [3] https://fedoraproject.org/wiki/Category:QA_SOPs > From alexeymorin at gmail.com Wed Jan 6 01:40:52 2010 From: alexeymorin at gmail.com (Alexey Morin) Date: Wed, 6 Jan 2010 04:40:52 +0300 Subject: Self-Introduction: Alexey Morin Message-ID: <7b145a541001051740x6f34580h82df86b54db0e6c6@mail.gmail.com> Name: Alexey Morin Inhabitation: Stavropol, Russia Login: morin, En-Ru Job: IT Specialist I'm working for a bank, Stavropol, Russia I'd like to contribute Fedora Project in documentation translation What else I'd like to do are websites, Fedora packages deployment Any project related to Fedora development to the extent it relates to administration, programming and configuration. I first met linux about 4 yrs. ago. Experience: documentation, operating systems documentation translation, IT projects, specifications and quotations translation What level and type of computer skills do you have? Linux (Fedora, Debian/Ubuntu) and Windows servers administration, virtualization (VMware), programming (C++, Qt) GPG KEYID and fingerprint pub 1024D/5F7D7CB7 2009-12-31 Key fingerprint = E13A 5FB0 55B9 8B26 EA01 07B0 9036 8067 5F7D 7CB7 uid Alexey Morin (Alexey Morin) sub 4096g/C3B5BC30 2009-12-31 -------------- next part -------------- An HTML attachment was scrubbed... URL: From noriko at redhat.com Wed Jan 6 02:24:27 2010 From: noriko at redhat.com (Noriko Mizumoto) Date: Wed, 06 Jan 2010 12:24:27 +1000 Subject: QA test for L10N In-Reply-To: <4B43D23C.1060905@redhat.com> References: <4B42D171.9070703@redhat.com> <1262699318.2401.44.camel@localhost> <4B43D23C.1060905@redhat.com> Message-ID: <4B43F45B.8090900@redhat.com> For F13, something like > "https://fedoraproject.org/wiki/Category:L10n_Test_Cases" to be written. Done :-) https://fedoraproject.org/wiki/Category:L10n_Test_Cases This is still incomplete, and I wish everyone to have a look and complete this list and to add any idea. I meant 'built status' is if package was built by specified date. noriko From yulia.poyarkova at redhat.com Wed Jan 6 04:16:27 2010 From: yulia.poyarkova at redhat.com (Yuliya Poyarkova) Date: Wed, 06 Jan 2010 15:16:27 +1100 Subject: Self-Introduction: Alexey Morin In-Reply-To: <7b145a541001051740x6f34580h82df86b54db0e6c6@mail.gmail.com> References: <7b145a541001051740x6f34580h82df86b54db0e6c6@mail.gmail.com> Message-ID: <4B440E9B.40105@redhat.com> Welcome Alexey, You account have been sponsored. Please add your name to the team list [1] and refer to page [2] to get the general idea of current tasks. If you are not sure where to start after you decide what exactly you would like to help with, please feel free to ask in fedora-trans-ru at redhat.com (in Russian) or contact me directly. Yulia (ru) [1] http://fedoraproject.org/wiki/L10N/Teams/Russian [2] https://fedoraproject.org/wiki/Ru_RU/MonthlyTasks [3] https://translate.fedoraproject.org/languages/ru/collection/fedora/websites/ > Name: Alexey Morin From igorsoares at gmail.com Wed Jan 6 04:31:10 2010 From: igorsoares at gmail.com (Igor Pires Soares) Date: Wed, 06 Jan 2010 02:31:10 -0200 Subject: QA test for L10N In-Reply-To: <4B43F45B.8090900@redhat.com> References: <4B42D171.9070703@redhat.com> <1262699318.2401.44.camel@localhost> <4B43D23C.1060905@redhat.com> <4B43F45B.8090900@redhat.com> Message-ID: <1262752270.2118.58.camel@localhost> Em Qua, 2010-01-06 ?s 12:24 +1000, Noriko Mizumoto escreveu: > For F13, something like > > "https://fedoraproject.org/wiki/Category:L10n_Test_Cases" to be written. > Done :-) > https://fedoraproject.org/wiki/Category:L10n_Test_Cases > > This is still incomplete, and I wish everyone to have a look and > complete this list and to add any idea. I meant 'built status' is if > package was built by specified date. Noriko, I suggest the inclusion of a test case for Anaconda using the Installation Media in addition to the Live Media. Of course, we would have to use an additional build. The Installation Media has a different set of strings and IMHO they are worth to be tested. For instance, on Fedora 12, Anaconda was 100% translated for Brazilian Portuguese but some strings remained in English on the Installation Media, although everything was OK on the Live Media. Regards, Igor Pires Soares From jlaska at redhat.com Wed Jan 6 13:42:43 2010 From: jlaska at redhat.com (James Laska) Date: Wed, 06 Jan 2010 08:42:43 -0500 Subject: QA test for L10N In-Reply-To: <4B43F45B.8090900@redhat.com> References: <4B42D171.9070703@redhat.com> <1262699318.2401.44.camel@localhost> <4B43D23C.1060905@redhat.com> <4B43F45B.8090900@redhat.com> Message-ID: <1262785363.2401.91.camel@localhost> On Wed, 2010-01-06 at 12:24 +1000, Noriko Mizumoto wrote: > For F13, something like > > "https://fedoraproject.org/wiki/Category:L10n_Test_Cases" to be written. > Done :-) > https://fedoraproject.org/wiki/Category:L10n_Test_Cases > > This is still incomplete, and I wish everyone to have a look and > complete this list and to add any idea. I meant 'built status' is if > package was built by specified date. Greetings Noriko, Typically, the category wiki pages are mostly a method for organizing related content on the wiki. So for the [[Category:L10n_Test_Cases]], you might use that to organize different wiki test case pages that have instructions for the l10n testing. For other examples, take a look at https://fedoraproject.org/wiki/Category:I18n_Test_Cases or https://fedoraproject.org/wiki/Category:Installer_Test_Cases. These pages aren't used for posting test results, just for grouping related wiki pages together for easier future navigation. It seems like you've already started outlining how you wish to gather test results. Way to get a head start! For that, I might recommend creating a test results wiki page (or pages) similar to https://fedoraproject.org/wiki/QA:Fedora_13_Install_Results_Template. Good news is that you already have the content for this page ... it's just in the wrong spot. I've moved the content you created into a new page ... https://fedoraproject.org/wiki/QA:Fedora_13_l10n_Results_Template. Hope that helps. From here, one way I could see you proceeding is ... 1. Start defining some basic test cases to guide testers. Be sure to link any created test case pages into [[Category:L10n Test Cases]] 2. When testing starts, create a wiki page for each test run (e.g. Test_Results:Fedora 13 L10n Alpha Test Results]]. Results will be posted to this page, not your template. Some of this is touched on by two of our existing SOP's [1][2], but if this is a process you'd like to repeat throughout the release (and future releases), I'd recommend taking your instructions above and creating a new [[SOP L10n Test Management]]. Thanks, James [1] https://fedoraproject.org/wiki/User:Liam/Draft_Install_Test_SOP [2] https://fedoraproject.org/wiki/QA/SOP_Test_Day_management -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: From domingobecker at gmail.com Wed Jan 6 14:11:19 2010 From: domingobecker at gmail.com (Domingo Becker) Date: Wed, 6 Jan 2010 11:11:19 -0300 Subject: QA test for L10N In-Reply-To: <1262752270.2118.58.camel@localhost> References: <4B42D171.9070703@redhat.com> <1262699318.2401.44.camel@localhost> <4B43D23C.1060905@redhat.com> <4B43F45B.8090900@redhat.com> <1262752270.2118.58.camel@localhost> Message-ID: <4818cd81001060611p36fba8bdgb64cc57a89fcadd8@mail.gmail.com> 2010/1/6 Igor Pires Soares : > The Installation Media has a different set of strings and IMHO they are > worth to be tested. For instance, on Fedora 12, Anaconda was 100% > translated for Brazilian Portuguese but some strings remained in English > on the Installation Media, although everything was OK on the Live Media. > The same happened for Spanish, but next time I will also test the the dvd installation media during alpha phase. Last time I only tested the live cd. kind regards Domingo Becker (es) From jensm at fedoraproject.org Wed Jan 6 15:48:01 2010 From: jensm at fedoraproject.org (Jens Maucher) Date: Wed, 06 Jan 2010 16:48:01 +0100 Subject: Translations sur git Message-ID: <4B44B0B1.1010200@fedoraproject.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, is there a documentation about doing translations using git? In the wiki i only found something about cvs https://fedoraproject.org/wiki/L10N/Tools#CVS_of_the_Fedora_Localization_Project I think it will be a good thing (especially for beginners), to know how it works adding translations sur git(me implied). Something off-topic.. A few days ago i read something about updating transifex, nice idea. When will transifex be updated and is in more languages available? - -- Jens - -- jensm at fedoraproject.org https://fedoraproject.org/wiki/JensMaucher -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAktEsLEACgkQzZrucUT/VOpBsQCgja6BEQgI7x3gG7EDQZkWSpzs EPMAoIX4eC9qn8WhTNdcV+fN7oYmtEp6 =SBRW -----END PGP SIGNATURE----- From r.landmann at redhat.com Wed Jan 6 22:42:44 2010 From: r.landmann at redhat.com (Ruediger Landmann) Date: Thu, 07 Jan 2010 08:42:44 +1000 Subject: Translations sur git In-Reply-To: <4B44B0B1.1010200@fedoraproject.org> References: <4B44B0B1.1010200@fedoraproject.org> Message-ID: <4B4511E4.6050504@redhat.com> On 01/07/2010 01:48 AM, Jens Maucher wrote: > is there a documentation about doing translations using git? > In the wiki i only found something about cvs > > https://fedoraproject.org/wiki/L10N/Tools#CVS_of_the_Fedora_Localization_Project > > I think it will be a good thing (especially for beginners), to know how > it works adding translations sur git(me implied). > To submit translations directly to the repo via git, you would need commit access to each document or software component itself. Transifex streamlines this by acting as an intermediary between the translator and the document or software project ? the project maintainers only have to give commit access to Transifex, and every translator automatically has access to the project. Is there a particular project that you're thinking of? And why not use Transifex? > A few days ago i read something about updating transifex, nice idea. > When will transifex be updated and is in more languages available? > > The work is currently underway, but there's no precise timeline because several issues need to be solved one after the other, and then of course tested. You can monitor the progress here: https://fedorahosted.org/fedora-infrastructure/ticket/1455 Fedora is upgrading from version 0.5 to version 0.7, but I don't know whether this will make the interface available in more languages. Cheers Ruediger From noriko at redhat.com Wed Jan 6 23:25:58 2010 From: noriko at redhat.com (Noriko Mizumoto) Date: Thu, 07 Jan 2010 09:25:58 +1000 Subject: QA test for L10N In-Reply-To: <1262785363.2401.91.camel@localhost> References: <4B42D171.9070703@redhat.com> <1262699318.2401.44.camel@localhost> <4B43D23C.1060905@redhat.com> <4B43F45B.8090900@redhat.com> <1262785363.2401.91.camel@localhost> Message-ID: <4B451C06.8090806@redhat.com> James Laska ????????: > On Wed, 2010-01-06 at 12:24 +1000, Noriko Mizumoto wrote: >> For F13, something like >>> "https://fedoraproject.org/wiki/Category:L10n_Test_Cases" to be written. >> Done :-) >> https://fedoraproject.org/wiki/Category:L10n_Test_Cases >> >> This is still incomplete, and I wish everyone to have a look and >> complete this list and to add any idea. I meant 'built status' is if >> package was built by specified date. > > Greetings Noriko, > > Typically, the category wiki pages are mostly a method for organizing > related content on the wiki. So for the [[Category:L10n_Test_Cases]], > you might use that to organize different wiki test case pages that have > instructions for the l10n testing. For other examples, take a look at > https://fedoraproject.org/wiki/Category:I18n_Test_Cases or > https://fedoraproject.org/wiki/Category:Installer_Test_Cases. These > pages aren't used for posting test results, just for grouping related > wiki pages together for easier future navigation. Hi James, I doubt if translators need further instructions. The one created worked so far for F12 internally. But this is just incomplete and need a help to improve. Once translators know how to get gui, they know what they want to see or check. The idea I draw in my mind is that one wiki page to be created per release, as packages to test may increase/decrease. This is just idea and can be improved in anyway. > > It seems like you've already started outlining how you wish to gather > test results. Way to get a head start! For that, I might recommend > creating a test results wiki page (or pages) similar to > https://fedoraproject.org/wiki/QA:Fedora_13_Install_Results_Template. > Good news is that you already have the content for this page ... it's > just in the wrong spot. I've moved the content you created into a new > page ... > https://fedoraproject.org/wiki/QA:Fedora_13_l10n_Results_Template. Hope > that helps. > > From here, one way I could see you proceeding is ... > > 1. Start defining some basic test cases to guide testers. Be sure > to link any created test case pages into [[Category:L10n Test > Cases]] > 2. When testing starts, create a wiki page for each test run (e.g. > Test_Results:Fedora 13 L10n Alpha Test Results]]. Results will > be posted to this page, not your template. > > Some of this is touched on by two of our existing SOP's [1][2], but if > this is a process you'd like to repeat throughout the release (and > future releases), I'd recommend taking your instructions above and > creating a new [[SOP L10n Test Management]]. There are two goals for this review process. One is to have a chance to review own work of translation in GUI and check the quality. Second is to check if latest translation done reflected in the package. In short frame of one week, we filed loads of bugs last time for second goal. Those bugs push the thing forwards. Honestly I like to avoid to create too much wiki pages specially in that period. But I am happy to create any page required. What I am really looking for is "nightly compose of 2010-03-05" available during 2010-03-08 to 2010-03-16 from QA team. With separate thread, yet installation media request comes up for reviewing. Thanks a lot noriko From noriko at redhat.com Wed Jan 6 23:30:42 2010 From: noriko at redhat.com (Noriko Mizumoto) Date: Thu, 07 Jan 2010 09:30:42 +1000 Subject: QA test for L10N In-Reply-To: <4818cd81001060611p36fba8bdgb64cc57a89fcadd8@mail.gmail.com> References: <4B42D171.9070703@redhat.com> <1262699318.2401.44.camel@localhost> <4B43D23C.1060905@redhat.com> <4B43F45B.8090900@redhat.com> <1262752270.2118.58.camel@localhost> <4818cd81001060611p36fba8bdgb64cc57a89fcadd8@mail.gmail.com> Message-ID: <4B451D22.5050308@redhat.com> Domingo Becker ????????: > 2010/1/6 Igor Pires Soares : >> The Installation Media has a different set of strings and IMHO they are >> worth to be tested. For instance, on Fedora 12, Anaconda was 100% >> translated for Brazilian Portuguese but some strings remained in English >> on the Installation Media, although everything was OK on the Live Media. >> > > The same happened for Spanish, but next time I will also test the the > dvd installation media during alpha phase. Last time I only tested the > live cd. I am not sure if installation media is available for us in this review period. But it is good to know the cause why this happens. From noriko at redhat.com Wed Jan 6 23:43:02 2010 From: noriko at redhat.com (Noriko Mizumoto) Date: Thu, 07 Jan 2010 09:43:02 +1000 Subject: QA test for L10N In-Reply-To: <4B451D22.5050308@redhat.com> References: <4B42D171.9070703@redhat.com> <1262699318.2401.44.camel@localhost> <4B43D23C.1060905@redhat.com> <4B43F45B.8090900@redhat.com> <1262752270.2118.58.camel@localhost> <4818cd81001060611p36fba8bdgb64cc57a89fcadd8@mail.gmail.com> <4B451D22.5050308@redhat.com> Message-ID: <4B452006.8050308@redhat.com> Noriko Mizumoto ????????: > Domingo Becker ????????: >> 2010/1/6 Igor Pires Soares : >>> The Installation Media has a different set of strings and IMHO they are >>> worth to be tested. For instance, on Fedora 12, Anaconda was 100% >>> translated for Brazilian Portuguese but some strings remained in English >>> on the Installation Media, although everything was OK on the Live Media. >>> >> >> The same happened for Spanish, but next time I will also test the the >> dvd installation media during alpha phase. Last time I only tested the >> live cd. > > I am not sure if installation media is available for us in this review > period. But it is good to know the cause why this happens. > Sorry replied myself. I will be holiday traveling between 8th to 27th January. Due to the place to visit, no internet no mobile available. It would be nice that many of you keep this ball rolling. noriko From jensm at fedoraproject.org Thu Jan 7 08:12:10 2010 From: jensm at fedoraproject.org (Jens Maucher) Date: Thu, 07 Jan 2010 09:12:10 +0100 Subject: Translations sur git In-Reply-To: <4B4511E4.6050504@redhat.com> References: <4B44B0B1.1010200@fedoraproject.org> <4B4511E4.6050504@redhat.com> Message-ID: <4B45975A.8040408@fedoraproject.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 06.01.2010 23:42, schrieb Ruediger Landmann: > Is there a particular project that you're thinking of? And why not use > Transifex? No, there is no particular project. The question was only to get some infos how it works. - -- Jens -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAktFl1oACgkQzZrucUT/VOq7HQCdGSnt9R7mv3+4Wj1loeld60mC 3JUAn18nVm8BQubrIKuY3EExUjfDsYD9 =wjCe -----END PGP SIGNATURE----- From jlaska at redhat.com Thu Jan 7 19:49:39 2010 From: jlaska at redhat.com (James Laska) Date: Thu, 07 Jan 2010 14:49:39 -0500 Subject: QA test for L10N In-Reply-To: <4B451C06.8090806@redhat.com> References: <4B42D171.9070703@redhat.com> <1262699318.2401.44.camel@localhost> <4B43D23C.1060905@redhat.com> <4B43F45B.8090900@redhat.com> <1262785363.2401.91.camel@localhost> <4B451C06.8090806@redhat.com> Message-ID: <1262893779.2658.228.camel@localhost> On Thu, 2010-01-07 at 09:25 +1000, Noriko Mizumoto wrote: > James Laska ????????: > > On Wed, 2010-01-06 at 12:24 +1000, Noriko Mizumoto wrote: > >> For F13, something like > >>> "https://fedoraproject.org/wiki/Category:L10n_Test_Cases" to be written. > >> Done :-) > >> https://fedoraproject.org/wiki/Category:L10n_Test_Cases > >> > >> This is still incomplete, and I wish everyone to have a look and > >> complete this list and to add any idea. I meant 'built status' is if > >> package was built by specified date. > > > > Greetings Noriko, > > > > Typically, the category wiki pages are mostly a method for organizing > > related content on the wiki. So for the [[Category:L10n_Test_Cases]], > > you might use that to organize different wiki test case pages that have > > instructions for the l10n testing. For other examples, take a look at > > https://fedoraproject.org/wiki/Category:I18n_Test_Cases or > > https://fedoraproject.org/wiki/Category:Installer_Test_Cases. These > > pages aren't used for posting test results, just for grouping related > > wiki pages together for easier future navigation. > > Hi James, > I doubt if translators need further instructions. The one created worked > so far for F12 internally. But this is just incomplete and need a help > to improve. Once translators know how to get gui, they know what they > want to see or check. Is this page available on fp.org/wiki somewhere? It certainly doesn't have to be in the [[Template:QA/Test_Case]] format, just something so that it's clear what work the team _is_ (and isn't) doing. > The idea I draw in my mind is that one wiki page to be created per > release, as packages to test may increase/decrease. This is just idea > and can be improved in anyway. I see. So if I understand correctly, eventually you might have the following set of pages? https://fedoraproject.org/wiki/QA:Fedora_13_l10n_Results https://fedoraproject.org/wiki/QA:Fedora_14_l10n_Results https://fedoraproject.org/wiki/QA:Fedora_15_l10n_Results > > It seems like you've already started outlining how you wish to gather > > test results. Way to get a head start! For that, I might recommend > > creating a test results wiki page (or pages) similar to > > https://fedoraproject.org/wiki/QA:Fedora_13_Install_Results_Template. > > Good news is that you already have the content for this page ... it's > > just in the wrong spot. I've moved the content you created into a new > > page ... > > https://fedoraproject.org/wiki/QA:Fedora_13_l10n_Results_Template. Hope > > that helps. > > > > From here, one way I could see you proceeding is ... > > > > 1. Start defining some basic test cases to guide testers. Be sure > > to link any created test case pages into [[Category:L10n Test > > Cases]] > > 2. When testing starts, create a wiki page for each test run (e.g. > > Test_Results:Fedora 13 L10n Alpha Test Results]]. Results will > > be posted to this page, not your template. > > > > Some of this is touched on by two of our existing SOP's [1][2], but if > > this is a process you'd like to repeat throughout the release (and > > future releases), I'd recommend taking your instructions above and > > creating a new [[SOP L10n Test Management]]. > > There are two goals for this review process. One is to have a chance to > review own work of translation in GUI and check the quality. Second is > to check if latest translation done reflected in the package. In short > frame of one week, we filed loads of bugs last time for second goal. > Those bugs push the thing forwards. Honestly I like to avoid to create > too much wiki pages specially in that period. But I am happy to create > any page required. As I'm understanding the work involved, I don't think you'll need a *lot* of pages. Just a high-level page to describe the workflow/process, a place to record results, and possibly a template for use with future test efforts. Speaking as someone not directly involved, it's nice to have some basic content available so folks on the outside have an idea how the testing is being performed ... and if desired, how to get involved. > What I am really looking for is "nightly compose of 2010-03-05" > available during 2010-03-08 to 2010-03-16 from QA team. With separate > thread, yet installation media request comes up for reviewing. I gather those dates are from task#13 on the Translation schedule [1]? The QA team doesn't provide/build the compose images, that is a service provided by release engineering. Looking at the dates you mention, the current F-13 QA schedule [2] shows that F-13-Alpha will be available for translation testing at that time. Additionally, there are nightly rawhide live images available [3] if testing against more recent updates is desired. Thanks, James [1] http://poelstra.fedorapeople.org/schedules/f-13/f-13-trans-tasks.html [2] http://poelstra.fedorapeople.org/schedules/f-13/f-13-quality-tasks.html [3] https://fedoraproject.org/wiki/Releases/Rawhide#Direct_Rawhide_install_via_Live_installer -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: From domingobecker at gmail.com Thu Jan 7 20:25:54 2010 From: domingobecker at gmail.com (Domingo Becker) Date: Thu, 7 Jan 2010 17:25:54 -0300 Subject: QA test for L10N In-Reply-To: <1262893779.2658.228.camel@localhost> References: <4B42D171.9070703@redhat.com> <1262699318.2401.44.camel@localhost> <4B43D23C.1060905@redhat.com> <4B43F45B.8090900@redhat.com> <1262785363.2401.91.camel@localhost> <4B451C06.8090806@redhat.com> <1262893779.2658.228.camel@localhost> Message-ID: <4818cd81001071225t1afc3fecqb1f823a2194ffc5b@mail.gmail.com> 2010/1/7 James Laska : > > The QA team doesn't provide/build the compose images, that is a service > provided by release engineering. > Looking at the dates you mention, the > current F-13 QA schedule [2] shows that F-13-Alpha will be available for > translation testing at that time. Don't ask translators to build a live image from rawhide. Based on my own experience, it will go wrong. I was never able to make a 'Live CD from rawhide' work. Something always goes wrong when booting. It seems that development people starts from an early installer and uses the update system since then. But if we use the Alpha compose to test, and our corrections and improvements will be present in Alpha 2 or Beta compose to check once more, that's ok and may work well. We will need that packagers pay attention to our commits to their repositories. > Additionally, there are nightly > rawhide live images available [3] if testing against more recent updates > is desired. > If these nightly rawhide live images work, it would be good. But packagers would have to pay attention to our commits in order to rebuild their packages with newer translations as soon as possible. My two cents. kind regards Domingo Becker (es) From r.landmann at redhat.com Thu Jan 7 23:46:50 2010 From: r.landmann at redhat.com (Ruediger Landmann) Date: Fri, 08 Jan 2010 09:46:50 +1000 Subject: Translations sur git In-Reply-To: <4B45975A.8040408@fedoraproject.org> References: <4B44B0B1.1010200@fedoraproject.org> <4B4511E4.6050504@redhat.com> <4B45975A.8040408@fedoraproject.org> Message-ID: <4B46726A.9080103@redhat.com> On 01/07/2010 06:12 PM, Jens Maucher wrote: > > No, there is no particular project. The question was only to get some > infos how it works. > No problem -- very generally, then: Once you have commit access to a project, you would run "git clone" to create a local copy of the remote repository. Depending on how the project is structured, you might also need to set up some extra branches in the local repository to reflect the branches of the remote repository. Then, if you make a change to a file named "de.po", you run the following commands: git add de.po git commit -m"Description of your changes" git push If you want to pull in recent changes by other contributors, you use "git pull". And that's all there is to basic git usage! Cheers Ruediger