There's a string in users-guide:
<application>CD/DVD Creator</application> is an application for
listening to audio CDs in GNOME.
Is it right?
I never used it to listen to audio CD, but to burn CDs or DVDs.
Domingo Becker (es)
* Full legal name: Michel Duquaine
* City, Country: Brussels, Belgium
* FAS username and language to translate: mdu , french
* Profession: programmer
* You and the Fedora Project: I try to do some tests in Rawhide &
updates-testing & create bugs in bugzilla. I would like to
translate the Fedora 11 user guide in french
* GPG KEYID and fingerprint:
pub 1024D/1207E162 2008-07-04
Empreinte de la clé = 8B38 66DA 3C7B 25CD 9164 5A99 C322
uid Duquaine Michel <michelduquaine(a)gmail.com>
sub 2048g/96E12567 2008-07-04
The release date for Fedora 11 is coming close, so it's time for some
coordination between the Ambassadors and the Marketing group! In this
mail, I'm going to address different points, so everyone has a clear
view of what is going on and how we can effectively split up the tasks.
Also any feedback is of course welcome.
1. In the next couple of days, the Documentation team is going to write
an official Release Announcement for Fedora 11 in English.
2. As soon as this document exists in a final form, it is going to be
translated in a couple of languages, if all goes well German, French,
Spanish, Portuguese, Hindi, Italian and Arabic. This will be coordinated
by the Documentation team with the aid of the Translation team. These
translated versions should be available a few days before the final release.
Now with that being done, we need to coordinate around everything else.
Earlier this year, the Marketing group has set up a structure called the
News Distribution Network (NDN) , which aims to distribute Fedora
news to the global media. Some Ambassadors from different languages have
joined this effort and will be pushing news to a list of publication 
Besides that, there are a number of ways in which we need the
1. Track all the Fedora news you see on the web and add it to our press
archive page , this will help us judge the depth of coverage so that
we can focus our messaging more precisely in the future.
2. At release time, and for a couple of days after that, we need you to
follow the comments on news websites. People will probably have
questions there, or you will have Fedora Myths to bust . As much as
some of us might like to flame people, our official policy is to be as
professional and possible while at the same time making our points clear
and well understood. Making members of the community angry us will prove
3. Blog! You can start right now, get vocal about Fedora! Talk about the
upcoming release and what the time table is. Talk about a feature you
care about. Talk about how we got to 11, but most importantly, just
If you feel like there is anything to add to this list, then please feel
free to reply and make sure to cross post to fedora-marketing-list as
well. Also, please let everyone know in what capacity you can help so
that we can coordinate efforts amongst everyone. I hope that everyone
has a better understanding of the process now :)
Have a nice day
There's a new software update program in Fedora 11, gpk-update-veiwer.
Is there any plan to add it to transifex ?
System -> Preferences has no submenus as in Fedora 10.
Is it something that went wrong with F11 Preview menus ?
Anaconda, the version 'Install to hard drive' doesn't let the user
choose the language.
It starts from a GNOME running session, which has the language
selected in the login, but anaconda (install to hard drive) runs in
At least 60% of my installs starts from a live cd, because it's really
fast and easy to get a desktop up and running, ready to use in a
It would be nice that anaconda honours the selected language in the
live cd gnome session, or let the user select the language.
> Message: 10
> Date: Mon, 27 Apr 2009 10:46:24 -0400
> From: "Paul W. Frields" <stickster(a)gmail.com>
> Subject: Re: Please add all the guys who helped in translation to the
> colophon of install-guide
> To: fedora-trans-list(a)redhat.com
> Message-ID: <20090427144624.GB619(a)localhost.localdomain>
> Content-Type: text/plain; charset="us-ascii"
> On Mon, Apr 27, 2009 at 09:06:56AM +0800, Tian Shixiong wrote:
>> I agree with Domingo Becker, his suggestion of adding the people to
>> the colophon.
>> Because many people have contributed to the translation(now or
>> before), but only a few of them were listed in the install-guide.
>> Please consider to do this, if it is possible. :-)
> I have a suggestion -- let's simply include "Fedora Documentation
> Team" and "Fedora Translation Team" on the authorship. The authorship
> could include a link to a specific wiki page where specific
> contributors could be included. That way each team can take care of
> updating the appropriate links, and anyone can help with the updates.
> Otherwise, speaking as someone who used to try to maintain these long
> lists, we're probably creating a headache.
> 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
----- Original Message ----- Date: Wed, 6 May 2009 00:19:45 +0200
From: Xavi Conde <xavi.conde(a)gmail.com>
Subject: Re: Release-note is long and hard for translating
> I see translating release notes as a long term useless effort
To a degree, you are right. Release notes have decreasing utility with
time. But then, so does everything else. The thing that makes the release
notes different than, say, the Installation Guide is that it is (or should
be) 100% new each release.
> I don't see any benefit for the user in knowing that openjdk was
> upgraded to XXX, rarely it will urge him to install Fedora.
This is the real problem. Every change is important to somebody, otherwise
it wouldn't be there. A lot of people are out there waiting for this
particular bug to be fixed, and when it is fixed in the upstream, most
people aren't going to want to compile it from source. So they wait until a
distro has the fixed version. Same with new features in some app or
another. Those features are there because somebody needs them. Those
somebodys are looking for the feature they need.
The problem is that the market is so diverse. We like to highlight
"important" features, but they are important only to us. I would argue that
the only F11 feature that is interesting to a large fraction of users is the
20 second boot, and even there, many people don't reboot for months at a
time, so it is really a non-event. Yes, there are features that are really
cool, but each has a pretty small audience.
That's why I am suggesting that we list ALL the changes, and pick a very few
to highlight. the list would make it easier for people looking for a
particular version to see whether it is there. The list, probably a table,
would consist of the name of the package, the old and new version numbers,
and a link to the upstream notes. None of that would need to be translated.
The description of the small number of cool features would need to be
translated, but that should reduce the amount that needs to be done to a
fraction of what it is today.
That still leaves the question of just how much prose do we want to have,
and how do we select the important changes. I think we often miss the boat
here. The release notes really do need to highlight any case where the user
needs to take action as a result of upgrading, especially if that action has
to occur before the upgrade. We don't do that very well now, and when we
do, it is only for the "important" applications.
But important to who? We are pretty careful, for example, of documenting
any special actions for MySQL or PostgreSQL database upgrades. These are
high profile applications. But I would argue that relatively few people
actually use them. The change is important for those who do use them, and
you could argue that when they are used, they tend to be used in highly
visible situations, but the audience is pretty small.
I don't know how we make these calls. I have some thoughts on ways to help,
but so far I haven't thought of anything that would get us a large fraction
of the way to where I would like us to be. We need a lot of dicsussion
between now and F12 to zero in on the right answer, so I am disappointed
that there has been little discussion on
We really need the discussion. Perhaps some of that will happen at FUDcon.
Ruediger Landmann wrote:
> I've also seen a suggestion that the list of translators should be cut
> down to only show the translators who worked on one particular
> translation of the book. For example, the version of the book in, say,
> Latin would only credit the people who translated it into Latin and none
> of the other translators would get any credit at all in that version. I
> would hate to see that happen, for the same reason I've just given.
> Whether or not a translator has contributed to *your* particular
> language, that person has still made an extremely valuable contribution
> to the project, and should be acknowledged. That's what it means to be
> part of a community, right?
If the format of translators list would be Language +
TranslatorNames + Year then there is not much left to
translate, except the names of languages; which are already
translated somewhere else an could thus be automatically
I recall extensive lists of languages in desktop_l10n.po,
desktop_kdelibs.po, and probably in Gnome's gtranslator,
gspell and maybe elsewhere.
Maybe this is not possible for RTL languages.
Just my 2 centimes.
Sveinn í Felli
Noriko Mizumoto wrote:
> The number of screenshots (how many screenshots) will help L10N team
> to weigh the task.
There are 68 screenshots in the Installation Guide
> The detailed steps to get there (each screen) will speed up
> translators to complete the task, it is usually more complicated task
> than general imagination.
> Is any virtual environment to be provided? Otherwise each translator
> needs to download target Fedora and perform the install process on
> their own machine for this purpose.
Actually, it's even more complicated than that. Remember that this is
the *installation* process we're documenting here, so the screenshots
need to be taken on a different machine (real or virtual) from the one
on which you're performing the installation process. You therefore
either need to install Fedora on one machine while controlling the
installation process and taking screenshots with a second machine (that
is, performing a VNC installation) or install Fedora on a virtual
machine (I use Sun VirtualBox for this).
Given the complexity of organising this, it was just easier for me to
take the screenshots in each language myself. If you look at the test
builds available here:
http://rlandmann.fedorapeople.org/Installation%20Guide/ you will see
that each language has its own set of screenshots (with the exception of
a few languages where the installation process itself has not been
localised yet -- for example, Latvian -- which use the English screenshots).
Additionally, I'm aware that this is a very big book and a very
demanding one for translators. I hope that taking care of the
screenshots is at least one little thing that I can do to make their
lives easier :)
* Noriko Mizumoto (ja)
* Mostafa Daneshvar (bal)
* Francesco Tombolini (it)
* MohsenSaeedi (fa)
1. Update on previous' meeting action items
2. Meeting frequency
=> change to Monthly
3. F11 Software translation review & F12 improvement
* There are some packages seems hardly to follow String Freeze, such as
=> make a complete list and define the solution with engineering
4. F11 Release Notes issue
* Release-note is long and hard for translating
=> need someone out write some added functionality to break a file up in
* There is Colophon issue
5. F11 Other guides issue
* Install guide contains loads of screenshots, and docs team wish to
have them captured in local languages too.
=> More info to be followed
6. L10n Infra team Report
=> not available as no team member attended
7. Open floor / AOB (any other business)
problems (numbers especially) with countdown logo and its translation,
I've mentioned them with guys in web and art
* it doesn't show diffs yet
=> TODO list (http://transifex.org/report/3)
* any reason why tx is not the standard landing page yet on translate.fp.o?
=> we are going to put the banner on the first page (home page :
translate.fedoraproject.org) , which will point to the new Tx
* misses the FLP logo on that page
=> raised to l10n admin by ankit
* Over all new TX
=>All are happy
2. F11 Schedule
* Some packages may change status lately
* No update for anaconda, we will escalate
3. Open floor / AOB (any other business)
* 'fa' members are not satisfied with their coordinator, not offering
sponsorship to users join to 'Fa'.
=> invite the coordinator on #fedora-l10n so that we can discuss it live