Bug 892779 - anaconda manual partitioning yellow banner "raid0 requires at least two disks" not translated to Spanish
Summary: anaconda manual partitioning yellow banner "raid0 requires at least two disks...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 18
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: David Lehman
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-07 20:12 UTC by Reartes Guillermo
Modified: 2014-02-05 14:32 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 14:32:17 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
screenshot showing the untranslated yellow banner (88.83 KB, image/png)
2013-01-07 20:12 UTC, Reartes Guillermo
no flags Details

Description Reartes Guillermo 2013-01-07 20:12:20 UTC
Created attachment 674331 [details]
screenshot showing the untranslated yellow banner

Description of problem:

As the title says, the yellow banner "raid0 requires at least two disks" is currently not translated to spanish

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

How reproducible:
always

Steps to Reproduce:
See screen-shot
  
Actual results:


Expected results:


Additional info:

Comment 1 Chris Lumens 2013-01-14 15:14:51 UTC
This raises a bigger question:  Should we be displaying the messages directly from storage-related exceptions or not?  If so, there's likely a lot of translation and grammar-related work to be done.

Comment 2 Brian Lane 2013-01-15 01:24:07 UTC
I think we probably should be translating storage messages. If we don't then we'll end up needed to add a layer in anaconda to catch and translate them, losing some of the detail in the process.

Comment 3 Fedora End Of Life 2013-12-21 10:14:42 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 
'version' of '18'.

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 prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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 4 Fedora End Of Life 2014-02-05 14:32:19 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.


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