Bug 745750

Summary: Semi-translation of anaconda in 16 Beta / Не полный перевод anaconda в 16-ой бете
Product: [Fedora] Fedora Reporter: Alexei Panov <me>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: anaconda-maint-list, jonathan, trans-ru, vanmeeuwen+fedora, vascom2
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: anaconda-16.22-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-14 02:48:58 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Scrennshot 1 (buttons/кнопки)
none
Screenshot 2 (screen)
none
Screenshot 3 (screen, semi-translation) none

Description Alexei Panov 2011-10-13 09:48:29 UTC
Created attachment 527935 [details]
Scrennshot 1 (buttons/кнопки)

Description of problem:
Some buttons and screens don't translated in the Installation process (anaconda).
For more information, see screenshots.
Некоторые кнопки и экраны мастера устновки не переведны или переведены не полностью.

Version-Release number of selected component (if applicable):
Fedora 16 Beta Install DVD
anaconda-16.20-1.fc16

How reproducible:
Every time
При каждой установке.

Actual results:
Fully translated the Installation process

Expected results:
Semi-tranlation

Additional info:
Original issue - http://redmine.russianfedora.ru/issues/717 (Russian language)

Comment 1 Alexei Panov 2011-10-13 09:49:25 UTC
Created attachment 527937 [details]
Screenshot 2 (screen)

Comment 2 Alexei Panov 2011-10-13 09:50:29 UTC
Created attachment 527938 [details]
Screenshot 3 (screen, semi-translation)

Comment 3 Misha Shnurapet 2011-10-13 15:20:57 UTC
В данный момент все строки переведены на русский.

Comment 4 Misha Shnurapet 2011-10-13 15:28:04 UTC
All the strings reported have been translated. Please pull translations and issue an update. Thanks.

Comment 5 Chris Lumens 2011-10-17 20:03:29 UTC
We'll pick this up should we do another build for F16, which it looks like is going to have to happen.

Comment 6 Fedora End Of Life 2013-01-17 01:32:04 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 '16'.

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 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 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 to click on 
"Clone This Bug" and open it against that version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 7 Fedora End Of Life 2013-02-14 02:49:01 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.

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