Bug 128838 - Faroese keyboard layout not available during install
Faroese keyboard layout not available during install
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2004-07-30 08:23 EDT by Roi a Torkilsheyggi
Modified: 2007-11-30 17:10 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-10-07 15:01:23 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 Roi a Torkilsheyggi 2004-07-30 08:23:49 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7)
Gecko/20040707 Firefox/0.8

Description of problem:
It is not possible to select Faroese as keyboard layout during the
installation of Fedora Core (2).
It would be nice to be able to select Faroese for use both during the
installation and as a system setting.
One can select Faroese using the graphical tool after installation has
finished, but not during the initial setup.

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

How reproducible:

Steps to Reproduce:
1. Start installation.
2. Skip ahead to the language part.
3. Try finding 'Faroese' from the list of languages.

Actual Results:  'Faroese' not an option in the keyboard/language list.

Expected Results:  Being able to select 'Faroese' from the
keyboard/language list.

Additional info:

Support for the Faroese keyboard layout has already been included in
Fedora, but it isn't available during the installation process.
Comment 1 Jeremy Katz 2004-08-03 14:25:07 EDT
What is the console and X keyboard map name?
Comment 2 Jeremy Katz 2004-10-07 15:01:23 EDT
Closing due to inactivity.  Please reopen if you have further
information to add to this report.

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