For the sake of clarity, should
set name=facet.locale.{name} value=true
correspond to files in
/usr/lib/locale/{name}/...
/usr/share/locale/{name}/...
?
I ask because it doesn't seem like a 1:1 correspondence is necessarily
right here, but perhaps it is.
/usr/lib/locale/en_AU
/usr/lib/locale/en_AU.ISO8859-1
/usr/lib/locale/en_AU.UTF-8
/usr/lib/locale/en_BW.UTF-8
/usr/lib/locale/en_CA
/usr/lib/locale/en_CA.ISO8859-1
/usr/lib/locale/en_CA.UTF-8
/usr/lib/locale/en_GB
/usr/lib/locale/en_GB.ISO8859-1
/usr/lib/locale/en_GB.ISO8859-15
/usr/lib/locale/en_gb.iso8859...@euro
/usr/lib/locale/en_GB.UTF-8
/usr/lib/locale/en_HK.UTF-8
/usr/lib/locale/en_IE
/usr/lib/locale/en_IE.ISO8859-1
/usr/lib/locale/en_IE.ISO8859-15
/usr/lib/locale/en_IE.UTF-8
/usr/lib/locale/en_IN.UTF-8
/usr/lib/locale/en_MT.UTF-8
/usr/lib/locale/en_NZ
/usr/lib/locale/en_NZ.ISO8859-1
/usr/lib/locale/en_NZ.UTF-8
/usr/lib/locale/en_PH.UTF-8
/usr/lib/locale/en_SG.UTF-8
/usr/lib/locale/en_US
/usr/lib/locale/en_US.ISO8859-1
/usr/lib/locale/en_US.ISO8859-15
/usr/lib/locale/en_us.iso8859...@euro
/usr/lib/locale/en_US.UTF-8
/usr/lib/locale/en_ZW.UTF-8
/usr/share/locale/en
/usr/share/locale/en_CA
/usr/share/locale/en_GB
/usr/share/locale/en_US
/usr/share/locale/e...@boldquot
/usr/share/locale/e...@quot
What do these equate to in facet.locale speak?
-Norm
Takeshi Asano wrote:
Hi all,
There are two portions facets are specified:
(a) server (package) side; to indicate which langs/locales an action
is for
(b) client side; to indicate which langs/locales user wants to install
From package provider's point of view i.e. (a), l10n facets can be
specified
like:
Language specific action (e.g. French)
set name=facet.locale.fr value=true
Locale specific action (e.g. French in France)
set name=facet.locale.fr_FR value=true
From client's point of view i.e. (b), in core IPS part facets are
specified
as described in the
http://src.opensolaris.org/source/xref/pkg/gate/doc/facets.txt
and as Bart said UI should provide it user-friendly.
As Bart already said, migration to use facets is targeting after the
next release. Core part of facet support is implemented but
related softwares e.g. packagemanager and installers/DC need to be
capable of handling facets. I'll update with plans by confirming plans
for such
enhancements.
Thanks,
Takeshi
On 2009年12月16日 06:40, Bart Smaalders wrote:
Norm Jacobs wrote:
Bart Smaalders wrote:
Norm Jacobs wrote:
So let me ask a couple of questions.
* Is there an expectation for each of the consolidations to adjust
their packaging to associate facets with sets of files in the
packages they deliver by build 137?
* Is
http://src.opensolaris.org/source/xref/pkg/gate/doc/facets.txt
intended to describe the canonical facets to be used in package
actions?
This likely represents a significant amount of work for each
consolidation. It will need to be planned for and relayed to
their various contributors.
Note that this work can be done incrementally; the default (current)
behavior is to install everything.
Since we're not planning on making the next release w/ this
functionality, getting the various consolidations on-board
during the next dev cycle seems appropriate.
Makes sense to me. I just wanted to be sure that there wasn't a
firedrill on the near horizon. Well, that and I want to be sure of
the canonical facet names so that the work doesn't end up having to
be redone later.
-Norm
I discussed the facet naming w/ the localization folks; the names are
up to them; I just implemented the mechanism :-). We do need to figure
out a nice user interface, as the individual facets names are a little
"programtical".
- Bart
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
