Bug 433193 - Outdated and wrong French translations
Outdated and wrong French translations
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: system-config-printer (Show other bugs)
rawhide
All All
low Severity low
: ---
: ---
Assigned To: Tim Waugh
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-02-17 07:10 EST by Josselin Mouette
Modified: 2008-02-19 18:09 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-02-17 14:26:26 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Patch for fr.po as of 0.7.81 (36.35 KB, patch)
2008-02-17 07:10 EST, Josselin Mouette
no flags Details | Diff

  None (edit)
Description Josselin Mouette 2008-02-17 07:10:22 EST
Description of problem:

French translation is outdated and has several mistakes.

Version-Release number of selected component (if applicable):

0.7.81

How reproducible:

Set locale to fr_FR*

Steps to Reproduce:
1. See the giant mistake in the menu entry
2. Have fun with the fuzzy translations
3. ... Profit !
Comment 1 Josselin Mouette 2008-02-17 07:10:22 EST
Created attachment 295100 [details]
Patch for fr.po as of 0.7.81
Comment 2 Tim Waugh 2008-02-17 14:26:26 EST
Thanks.  You can also check in translations directly using
translate.fedoraproject.org.
Comment 3 Thomas Canniot 2008-02-19 13:58:36 EST
There was some confusion here... the French team IS working actually on the
translation of this tool.

Why was our work blown away by a simple bug report ? This not the *normal*
process to submit translation _at all_. A message should have been sent to the
fedora translation list and I, as the French Fedora Translation Coordinator
(https://translate.fedoraproject.org/languages/fr?lang=en) should have been warned.

The process of reading over my translation is being done actually on the French
translation List, and as it will be a team effort, it will overwrite Josselin
Mouette translation in few days, by being submitting through the normal
submitting tool (transifex, and not Bz). If Josselin translated strings are
considered as being better, they will be included. 
Comment 4 Josselin Mouette 2008-02-19 14:38:30 EST
If there is actually some translation effort going on, I’m very happy to hear
that (and I couldn’t care less of you dropping my translations if you have
better ones), but you can’t say it is visible.
 * Nothing on translate.fedoraproject.org gives any hint about the status of the
translations, and I couldn’t even find an URL for an open repository.
 * The state of the translations - not only French - is very bad. They are
outdated (only 15/65 have been touched in the last 6 months), and there are many
fuzzy strings which often mean completely unrelated things, meaning the
application is hardly usable in another language than English.
 * There were big mistakes in the French translation, including one in the
desktop file. I don’t think this should happen with a proofreading process.
 * There doesn’t seem to be a string freeze in system-config-printer before a
release. If this doesn’t happen, there is no way the translators can cope up
with the string changes and provide good translations at release time. This is
really something that needs to be integrated in the development process.

Tim, has you considered moving the system-config-printer project to the GNOME
repository? You would gain committed and responsive l10n teams, and, if you
agreed to follow the GNOME development process, almost complete translations at
the time of a major release.

Thomas, I’m sorry to have used Bugzilla instead of transifex for submitting, but
the latter is not open to external contributors. I’m just trying to bring
system-config-printer to an acceptable level of usability for Debian, which is
why I’m feeding our packages with additional translations. If we can find a
process that makes them benefit to upstream (currently being Fedora), that’s
better for all of us. If not, we can keep the translations for us like Ubuntu
does, but this is not the way we are used to work. 
Comment 5 Thomas Canniot 2008-02-19 15:51:08 EST
The state of the translation is not *very* bad. It is related to the state of
the distro development cycle. Fedora 9 is actually in Alpha, then it seems
normal that translation is not yet completed.

Thanks for correcting the mistakes in the .po file.

As fedora is upstream for this package, you can subscribe to the French mailing
list (https://www.redhat.com/mailman/listinfo/fedora-trans-fr) and help us
improve s-c-printer translation. We have, I think, to learn good things from our
translation processes.
Comment 6 Josselin Mouette 2008-02-19 17:22:15 EST
I do not intend to become a translator for the Fedora team. As one of the
maintainers of the Debian package, I want it to be usable *in Debian*. And that
does not include only French translations.

How should I submit subsequent translation improvements, if Bugzilla is not
appropriate?
Comment 7 Thomas Canniot 2008-02-19 17:35:08 EST
By using Transifex, but that means you have to open a Fedora account. :/ Well
then you have to use Bugzilla, but report it against the product « Fedora
localization » and select French (fr) as a component.

I will receive the translation then and could submit it to proofreading. This
will avoid Tim to accept translation out of the translation process :)
Comment 8 Thomas Canniot 2008-02-19 17:37:26 EST
By the way, I proofread my translation looking at yours at the same time. I
think we can have a compromise on that basis.
Comment 9 Josselin Mouette 2008-02-19 17:53:18 EST
OK, I will use the l10n components in Bugzilla.
BTW there is no Vietnamese component. Where should I send vi.po then?
Comment 10 Dimitris Glezos 2008-02-19 18:00:02 EST
There is a componenet "Other languages" for this purpose.
Comment 11 Josselin Mouette 2008-02-19 18:09:45 EST
zomg that was a very stupid question.

Note You need to log in before you can comment on or make changes to this bug.