| Summary: | Typo mistake in French in g++ | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Olivier Delaune <olivier.delaune> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | minor | ||
| Priority: | Normal | CC: | marja11, rverschelde |
| Version: | 4 | Keywords: | UPSTREAM |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | gcc | CVE: | |
| Status comment: | |||
|
Description
Olivier Delaune
2013-08-31 01:31:06 CEST
looks like you could send a mail to Gregroire Scano: cf http://translationproject.org/team/fr.html and search for GCC (and indeed http://translationproject.org/PO-files/fr/gcc-4.8.0.fr.po is wrong) Keywords:
(none) =>
UPSTREAM Thank you. I§ sent an email to Grégoire Scano. I will keep you inform if I got an answer. It seems it's not fixed in gcc 4.9 either: https://translationproject.org/PO-files/fr/gcc-4.9-b20140202.fr.po But just looking for this string, I spotted some wrong translations (e.g. referring to a different argument than the English string) in the file, so I guess a good proofreading of the gcc translation would not hurt. If you haven't done so yet, I would advise to open a bug report upstream, and then this one can probably be closed, it would be pointless to fix the translation in Mageia and not upstream. CC:
(none) =>
remi No I do not think a bug report was opened. One year ago, I contacted the maintainer of the po file, Grégoire Scano, and he said me that he will fix the mistake ASAP. But it appears it was not done. I will send hime a new email to remind him. At least, the mistake I mention in the first message will be fixed. Of course if someone has time to proofread the file, I think Grégoire will be happy to send you the po file. From the website, I see that Gregoire is not the leader anymore. The new one is Denis Barbier. SO I will contact him. Mageia 3 changed to end-of-life (EOL) status 4 months ago. http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad Status:
NEW =>
RESOLVED This typo is still present in Mageia 4. Status:
RESOLVED =>
REOPENED There's nothing we can do about this one though, it has to be fixed upstream.
Marja Van Waes
2015-03-31 23:09:08 CEST
CC:
(none) =>
marja11 Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/ Closing as WONTFIX, we won't start patching gcc translations anyway, this should be fixed upstream. Status:
REOPENED =>
RESOLVED |