Hi, Dave,
I didn't find any information about localization packages installation, 
do you have any plan to cover it later?

The current situation is, unless you choose customize install and check 
some or all  GEOs one by one,  only  C locale plus the locales of one of 
the 9 big rules languages (if you manually choose that language instead 
of the default English as the installation language) will be installed.

We have got more and more questions about how to add more non English 
locales to an English only OS and also a lot of complains or even 
escalations, and I think it's the time to revise the localization 
packages install strategy. Localization packages include two different 
sets of packages:
1. Locale enabling packages for locale shared objects, fonts, input 
methods, iconv modules, X11 modules, etc.
2. Pure translation packages for the translations of messages in ON, 
Gnome, Firefox, Thunderbird, Realplayer, etc.

The following are some options of the localization packages installation:

1. Current solution, only C locale will be installed unless you choose 
one of the big rules language as the installation language or manually 
check GEOs from customized install.
2. Install all locales by default, inform customers to deselect some 
only if the disk space is limited
3. Separate locale enabling packages from pure translation packages and 
install all locale enabling packages by default, and install other 
translation packages by manually selection during installation, but this 
should be clearly explained to customers before they choose "Default 
Install" or "Customize Install".
4. Provide downloadable, easily installable and removable locale patches 
or packages so that customers can add/remove locales easily.

Most Linux distros are using the 2nd option, but I prefer the  3rd and 
also the 4th :-)

Thanks,
Brian

Dave Miner wrote:
> Greetings, Installation community members!
> 
> I've just posted for discussion a document that I've been working on 
> for the past couple of months: a draft strategy for Solaris 
> installation.
> 
> The document discusses the current state of Solaris installation in 
> relation to customer requirements, and proposes a set of features and
>  projects designed to address the requirements.
> 
> Please understand that this is a proposal; while it's had some 
> preliminary review by a small number of people in Solaris 
> engineering, this is the first time it's been widely disseminated and
>  thus I expect to receive, and incorporate, a great deal of feedback 
> which will evolve it from this point.
> 
> I would appreciate review comments by April 14.  I encourage posting 
> comments to this list, but private comments are of course equally 
> acceptable.
> 
> http://www.opensolaris.org/os/community/install/files/install_strategy.pdf
> 
> 
> 



Reply via email to