Bug 147596 - Improve language selection in anaconda and installed environment
Summary: Improve language selection in anaconda and installed environment
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: dff
URL:
Whiteboard:
Depends On:
Blocks: FC6Blocker 207452
TreeView+ depends on / blocked
 
Reported: 2005-02-09 17:09 UTC by Leon Ho
Modified: 2007-11-30 22:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-09-20 04:57:51 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Leon Ho 2005-02-09 17:09:44 UTC
First Language selection screen
  - Current it is a messy to have same language with different
variants/scripts
  - One idea is to separate it to different pull down widget.
  - Another idea from Bryan is putting pull down widget for variants
into tree widget
  - A issue will be what happen if the translation for the language name
is different?
  - Another thought is merging keyboard setting and timezone setting
with language section screen to generate a "localization setting"

Language package grouping
  - One idea is to remove current confusing "language support" page and
instead adding groups of "language support" in package selection
  - This also provide language package selections in system-config-
packages

Comment 5 Caius Chance 2006-09-11 06:03:02 UTC
Will we sacrifaced user's flexiblity in system configuration when we intend to
add usability?

Comment 6 Caius Chance 2006-09-13 02:18:04 UTC
Could the language of the installation be grouped by locale?

[language[_territory][.codeset][@modifier]]

i.e. by language or territory?

Comment 7 Leon Ho 2006-09-20 04:57:51 UTC
Resolving this as most of the problems here have been fixed. Caius, let's clone
the language group part to a new bug and put this as a low priority. Probably it
is for FC7/FC8. Thanks.


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