Bug 952113

Summary: [ja_JP] Duplicate string 'Usage' and unlocalized string 'Options'.
Product: [Fedora] Fedora Reporter: Lijun Li <lijli>
Component: authconfigAssignee: Tomas Mraz <tmraz>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 25CC: abdel.g.martinez.l, mshao, noriko, rlandman, swgoswam, tmraz
Target Milestone: ---Keywords: Translation
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: F19L10nTestday
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-12 10:26:40 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 958376    
Bug Blocks:    
Attachments:
Description Flags
Duplicate string 'Usage' and unlocalized string 'Options' none

Description Lijun Li 2013-04-15 08:36:58 UTC
Description of problem:
Duplicate string 'Usage' and unlocalized string 'Options'.


Version-Release number of selected component (if applicable):
Fedora19 l10n test day iso

How reproducible:
100%

Steps to Reproduce:
1. Run command authconfig 
2. Check translations on terminal 
  
Actual results:
Duplicate string 'Usage' and unlocalized string 'Options'.

Expected results:
1. Please remove the English string 'Usage' as it's already translated.
2. Please translate the string 'Options'

Additional info:

Comment 1 Lijun Li 2013-04-15 08:39:24 UTC
Created attachment 735829 [details]
Duplicate string 'Usage' and unlocalized string 'Options'

Comment 2 Noriko Mizumoto 2013-05-01 05:34:37 UTC
Ping Tomas or anyone, any update?

Comment 3 Tomas Mraz 2013-05-02 06:33:05 UTC
Unfortunately these strings are coming from python OptParse and I can't see how to localize them.

Comment 4 Noriko Mizumoto 2013-08-19 07:06:25 UTC
*** Bug 953820 has been marked as a duplicate of this bug. ***

Comment 5 Noriko Mizumoto 2013-12-11 06:38:51 UTC
Ping,
Is any progress on this bug?

Comment 6 Tomas Mraz 2013-12-11 08:43:20 UTC
Unfortunately no.

Comment 7 Fedora End Of Life 2015-01-09 17:53:37 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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 Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 8 Jaroslav Reznik 2015-03-03 14:54:55 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Comment 9 Piotr Drąg 2015-09-03 16:54:48 UTC
*** Bug 1255226 has been marked as a duplicate of this bug. ***

Comment 10 Jan Kurik 2016-02-24 15:34:44 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase

Comment 11 Tomas Mraz 2016-03-31 07:38:41 UTC
*** Bug 1322192 has been marked as a duplicate of this bug. ***

Comment 12 Jan Kurik 2016-07-26 05:09:25 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle.
Changing version to '25'.

Comment 13 Fedora End Of Life 2017-11-16 19:23:00 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

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 Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

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 Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 14 Fedora End Of Life 2017-12-12 10:26:40 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.