Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 135298 - Some tabs of the firstboot are not in Bulgarian
Some tabs of the firstboot are not in Bulgarian
Product: Fedora
Classification: Fedora
Component: firstboot (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Chris Lumens
Depends On:
  Show dependency treegraph
Reported: 2004-10-11 16:06 EDT by Nikolay
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-09-23 10:59:55 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Nikolay 2004-10-11 16:06:58 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3)
Gecko/20040929 Epiphany/1.4.0

Description of problem:
Some of the tabs in first boot are not in Bulgarian (not the titles -
they are fine but the text inside)
Actually besides the <Screen>, Date Time - all others are in English
like <add user>, Test Sound, Additional CDs and the button Installs...

it is odd but the other button Play Test Sound is in Bulgarian.

I did not notice that bug in Test2 - although I am not sure about it.

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

How reproducible:

Steps to Reproduce:
1.Install Fedora Core 3 Test 3 (Bulgarian)
2.First boot
3. see the screens - after Screen all others are in English

Actual Results:  All tabs after Screen are in English

Expected Results:  should be in Bulgarian

Additional info:
Comment 1 Jeremy Katz 2005-07-06 17:53:49 EDT
Is this better in FC4?
Comment 2 Chris Lumens 2005-09-23 10:59:55 EDT
Since there are insufficient details provided in this report for us to
investigate the issue further, and we have not received the feedback we
requested, we will assume the problem was not reproduceable or has been fixed in
a later update for this product.  If you have further details, feel free to
reopen the report with the additional details attached.

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