trans May 2012

trans@lists.fedoraproject.org

27 participants
23 discussions

Fedora 17 guides
by Petr Kovar 22 May '12

22 May '12

Hi translators, Just to let you know what Fedora guides have been pushed to Transifex recently. * Burning ISOs: https://www.transifex.net/projects/p/fedora-readme-burning-isos/ * Live Images: https://fedora.transifex.net/projects/p/fedora-readme-live-images/ * Software Collections Guide: https://fedora.transifex.net/projects/p/software-collections-guide/ This is a brand new document, which discusses Software Collections that allow users to concurrently install multiple versions of the same RPM packages on the system. Using the scl utility, users may enable specific versions of RPMs which are installed into the /opt directory. * System Administrator's Guide: https://www.transifex.net/projects/p/system-administrators-guide/ * User Guide: https://www.transifex.net/projects/p/fedora-user-guide/ For more info on guides, refer to: https://fedoraproject.org/wiki/Docs_Project_guides_table Happy translating, Petr Kovar

5 6

Another proposed fix for fedoraproject.org website/POT
by Paul W. Frields 18 May '12

18 May '12

I found some incorrect English style/usage in the previous fix, so I've made a git patch to fix it. Kévin, can you apply this please? Paul

2 4

fedoraproject.org is ready for translation
by Kévin Raymond 18 May '12

18 May '12

Hi there, The today Go/No-Go meeting is a No-Go for RC1, the GA has slipped to May 29th. That is going to let you more time for translations, which is not too bad! We've just managed to have the fedoraproject.org website ready for translations. The content is not fully written yet, but which is aleady written should not change. We just miss a small Clouds section, and changes in the interviews and quotes. But what you are actually able to translate is all that we can give you today. The TXN fedoraproject.org f17-beta release has been locked, and merged in the unlocked master one, at https://fedora.transifex.net/projects/p/fedora-web/resource/fedoraproject-o… Proofreading is made at http://stg.fedoraproject.org/ The spins.fpo is going to be updated ASAP, be aware that some strings will change shortly. Please, report to us any typo. Thanks, happy translating! -- Kévin Raymond (Shaiton)

3 4

Self-Introduction: dago (French)
by Damien Gourbiere 14 May '12

14 May '12

- Name: DaGo - Location: Grenoble, France - Login: dago - Language: French/English bilingual - Profession: Software Engineer - About You: Hi, I am a French national who has lived in the US for several years. Being part of the Fedora translation team seems to me like a great way to learn about Linux and give back to the community at the same time. - You and the Fedora Project: I have a fresh install of Fedora 16 on a VirtualBox. Let the fun begin! - pub 2048R/D4D61E14 2012-04-15 Key fingerprint = 6449 DDF0 9833 497E C3D9 9097 8B02 B47A D4D6 1E14 sub 2048R/BC6A486A 2012-04-15

3 2

64-bit version in Release Notes
by Valentin Laskov 12 May '12

12 May '12

Hi all, In f.p.o website, by default for downloading will be Fedora 17 64-bit version. I think that this must be mentioned in the Release notes. Best regards! Valentin Laskov

2 1

The Future of release names
by Toshio Kuratomi 09 May '12

09 May '12

At the last Board Meeting, the Board looked at the poll results asking whether people felt like continuing to name releases. The results seemed to show that many people do like having a name associated with Fedora releases. However, the discussion before and after has shown there is a desire to improve upon the current method of selecting the names. The Board decided that it would be worthwhile to come up with a new procedure for selecting the name for the Fedora 19 release and beyond to attempt to solve some of the issues that have been brought up. The Board is looking for volunteers who would like to do two things: (1) Answer the following questions: * What benefits does the Project get from the current release naming process? * What changes do people want to see in a revised process? (2) Come up with at least one proposal and analyze it according to the answers to the previous questions. If anyone is interested in coming to a weekly meeting to work on this, please feel free to contact me. If anyone would like to champion this, please contact me ASAP so I know whether there is someone else who's going to champion this or if I need to lead the effort. I've put up a wiki page that tries to summarize the answers to the first two questions that I've seen circulated on the advisory-board mailing list and a link to the only proposal I currently know of (mizmo's proposal to use a single theme for all of the new Fedora releases). Thanks, -Toshio

1 0

Self-Introduction: Jiro Matsuzawa, Japanese
by Jiro Matsuzawa 08 May '12

08 May '12

Name: Jiro Matsuzawa Location: Japan Login: jmatsuzawa Launguage: jmatsuzawa About me: I am a member of the GNOME Foundation. I translate GNOME into Japanese. Me and the Fedora Project: I am a Fedora user. I hope to contribute to Fedora. GPG Key ID: ECC442E9 GPG Key Fingerprint: E086 C14A 869F BB0E 3541 19EB E370 B08B ECC4 42E9

2 1

Release Notes - Ukranian and Bulgarian translations
by John J. McDonough 08 May '12

08 May '12

Please visit https://admin.fedoraproject.org/updates/fedora-release-notes-17.0.0-1.fc17 Check out the RPM and the translations and give karma. This corrects all the outstanding bugs. There are a few new untranslated strings. - I added a revision history entry for 17.0 but Publican seems to think this is already translated. - I added the Bulgarian and Ukranian translators names to the contributors - these shouldn't need to be translated. I will continue to build new RPMs as new translations become available. --McD

1 0

Release Notes update
by John J. McDonough 08 May '12

08 May '12

We had a rash of bugs to the release notes, many from translators -- thank you very much. We appreciate that. However, that did result in having to push updated POTs. Most are tiny typo changes, but in one case there is an entirely new section, Installation. My apologies for the late change, especially to the Ukranian team who was complete. Most of those I should have caught earlier, although there is no way I would have caught the installation change. --McD

4 5

Fwd: Please check your sources for strings not marked for translation before release
by Ankit Patel 08 May '12

08 May '12

Thought of forwarding it here as it also occurs with us in most of the Fedora packages where Fedora is upstream. We (translators) always try to find out where did we miss the translations when we find that a particular package has something viewed in English during the testing phase. So, developers, please please check or make sure that you are marking all translatable messages as translatable, otherwise it would never come to us (translators) and would never go to end users as localized messages. Thanks a lot! Ankit http://www.ankit644.com/ -------- Original Message -------- Subject: Please check your sources for strings not marked for translation before release Date: Mon, 07 May 2012 13:59:45 +0200 From: Kenneth Nielsen <k.nielsen81(a)gmail.com> To: gnome-i18n(a)gnome.org, desktop-devel-list(a)gnome.org Hallo developers. Since the release of GNOME 3.4 we have received a steady stream of emails saying "This is not a string freeze break, we just forgot to mark the strings for translation". So much so, that the statistics e.g. for my language (which has not been touched since release) now counts 63* untranslated or fuzzy strings in a source that was at 0 at release time, three weeks ago. I understand the reason for not counting marking existing strings as a string freeze break. But please understand that even though you are in your right to fix things like this post release, and even though it off course makes sense to do it, it does not mean that it is not annoying and a burden for translators. The reason for this is that we concentrate large amounts of work in the period just before release (where string changes are relatively quiet), so therefore it is also an advantage for us if we can finish as much of it as possible in that period (of course also because a lot of us has an extra hat as distribution translators for distributions that follow within a month or so of the gnome release). On top of that, small updates are uncharacteristically expensive in a work/string-sense because they involve the same amount of emails back and forth for proofreading and git work. So please... If you could make a bit more of an effort of checking your sources for non-internationalized strings before release that would be great. IMHO 63 is just a bit on the high side of where this number should be Regards Kenneth * These 63 off course also include genuinely new strings due e.g. to bug fixes. _______________________________________________ gnome-i18n mailing list gnome-i18n(a)gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

trans May 2012