Installing language support

[Rahul Sundaram]

Hi,

Following

https://bugzilla.redhat.com/show_bug.cgi?id=496542

Instead of cherry picking individual packages (such as the ones
containing the localized strings, spell checkers, input methods etc)
necessary for locale support, you can either use PackageKit, click on
"Package Collections" and select the appropriate language or just do

# yum install @<language>-support

Example:

# yum install @bengali-support

@ is a short cut for group installs,

Group installs provide not only a quick way to install the necessary
packages but also conditionally install packages on demand.

For example, when you do this, openoffice.org-langpack-bn or
imsettings-xfce will be automatically installed if and only if you have
Openoffice.org or Xfce respectively already installed on your system.

Rahul

[sankarshan]

On Thu, Apr 23, 2009 at 2:25 PM, Rahul Sundaram
<sundaram(a)fedoraproject.org&gt; wrote:

>  Following
>
>  https://bugzilla.redhat.com/show_bug.cgi?id=496542
>
>  Instead of cherry picking individual packages (such as the ones
>  containing the localized strings, spell checkers, input methods etc)
>  necessary for locale support, you can either use PackageKit, click on
>  "Package Collections" and select the appropriate language or just do
>
>  # yum install @<language>-support
>
>  Example:
>
>  # yum install @bengali-support 
<http://runab.livejournal.com/9375.html> was what Runa had written
down some time back.


-- 

http://www.gutenberg.net - Fine literature digitally re-published
http://www.plos.org - Public Library of Science
http://www.creativecommons.org - Flexible copyright for creative work
Sent from Pune, MH, India

[das]

>  On Thu, Apr 23, 2009 at 2:25 PM, Rahul Sundaram
>  <sundaram(a)fedoraproject.org&gt; wrote:
>  
> > Instead of cherry picking individual packages (such as the ones
> >
> > # yum install @<language>-support
> > 
No, doubt it is a better method, it works in one go, and I did not
know of this '@*' command before you wrote about it in the
bug-discussion.

I grew this habit of picking the packages because earlier I had a
severe limitation of disk-space, and I did not want to spend it on
anything other than what I absolutely need, like say, langpack-bn, or
moodle, or something.

And if that was the culprit, how come it worked on Gnome? So there is
something specific to Xfce. Why the input method chooser does not
automatically come with Xfce, like it comes with Gnome? Both Gnome and
Xfce were getting the same set of files, and one was working, while
the other was not. I think im-chooser must be one for the whole
system, and every X-Windows should draw the information from it. In
both Gnome and Xfce I ran 'im-chooser' from the command prompt, and it
popped up the same window, where iBus was already selected.

And the situation was more funny because after I installed the primary
thing from the DVD, Bangla input from iBus was working nice (it was
the default Gnome) and after I installed the Xfce things and logged
into Xfce, 'iBus' was showing alright, but not working. So the
superset was not working while the part was.

-- 
দাশ das
http://ddts.randomink.org/

[Rahul Sundaram]

On 04/24/2009 04:05 PM, das wrote:

>  
>  And if that was the culprit, how come it worked on Gnome? So there is
>  something specific to Xfce. Why the input method chooser does not
>  automatically come with Xfce, like it comes with Gnome? 
imsettings-xfce is a separate sub package. IIRC it is not part of the
default package set in the group but only installed if you pick a
particular locale.

Rahul

[das]

On Fri, Apr 24, 2009 at 4:15 PM, Rahul Sundaram
<sundaram(a)fedoraproject.org&gt; wrote:

>  imsettings-xfce is a separate sub package. IIRC it is not part of
> the
>  default package set in the group but only installed if you pick a
>  particular locale.
>  
Now the whole thing gets clear. And it reminds me I had the same
problem with SCIM in XFCE in Fedora 8. Most probably I made a bug
report, and someone there helped me with the suggestion that I will
have to install that package. But all this time I thought that it was
a kind of a dependency problem.


-- 
দাশ das
http://ddts.randomink.org/

[das]

On Fri, Apr 24, 2009 at 4:15 PM, Rahul Sundaram
<sundaram(a)fedoraproject.org&gt; wrote:
>  imsettings-xfce is a separate sub package. 
Still a question remains. There must be some counterpart of this in
Gnome, like, say, imsettings-gnome. And if Gnome takes that by
default, why Xfce should not?

And the document written by Runa Bhattacharya mentions im-chooser,
which I did already run on Xfce, and it gave me no error message.

[I am sorry if I sound nagging, and particularly, when the problem is
already solved, but, actually I cannot understand the logic of the
full thing.]
-- 
দাশ das
http://ddts.randomink.org/

[Rahul Sundaram]

On 04/25/2009 08:01 AM, das wrote:
>  On Fri, Apr 24, 2009 at 4:15 PM, Rahul Sundaram
>  <sundaram(a)fedoraproject.org&gt; wrote:
> > imsettings-xfce is a separate sub package.
>  
>  Still a question remains. There must be some counterpart of this in
>  Gnome, like, say, imsettings-gnome. And if Gnome takes that by
>  default, why Xfce should not? 
imsettings-xfce is defined as conditional in the comps group which is
the file that is used in Fedora to determine which package belongs to
which group

http://cvs.fedoraproject.org/viewvc/comps/comps-f11.xml.in?view=markup

It is likely that imsettings (there is no specific subpackage for GNOME)
was a direct dependency for some package you cherry picked. You would
have to trace the exact steps to figure out which one.

Rahul

[das]

On Sat, Apr 25, 2009 at 10:06 AM, Rahul Sundaram
<sundaram(a)fedoraproject.org&gt; wrote:

>  It is likely that imsettings (there is no specific subpackage for GNOME)
>  was a direct dependency for some package you cherry picked. You would
>  have to trace the exact steps to figure out which one.
>  
Yesterday I installed F11 on a Lennovo laptop, with an F11 beta DVD.

After the installation was over (with software customization set
'later', no software or repositories added, everything default), I
made a reboot, and logged in, and it was a Gnome, obviously. And the
interesting point is, here iBus was working and I added a Bangla
Probhat keyboard in iBus and on a Gedit window I typed Bangla at ease.

Now I made 'yum -y update' and did a reboot, and still iBus Bangla
Probhat was working.

Now I installed the group XFCE and rebooted and logged in into Xfce,
and iBus did not work, the usual problem, as reported in the bug your
OP quoted.

Now I installed yumex and got into yumex. Searched for the string
'imsetting' and saw that a package named 'imsetting' was installed,
and as expected, another package named 'imsetting-xfce' was there but
it was not installed, as you predicted, which now I did and it worked.

So, there was a default 'imsetting' that was being used by Gnome. So,
it does not matter, if Gnome did not have its own imsetting package.
It was using the system-wide default. And not that any package
selected by mine did make it happen. It happened by default.

And Xfce, even when the system-wide 'imsetting' is installed and
working and the group 'XFCE' is called for install, is not installing
its own version of imsetting. A working system is rendered unworkable
(by 'work' in terms of iBus) by adding Xfce. Do you think it is an
expected behavior of 'groupinstall XFCE'?

What the whole OS is doing on its system default, is getting broken by
installing XFCE, a part added to the whole. Do you consider it as a
bug?

-- 
দাশ das
http://ddts.randomink.org/

[Rahul Sundaram]

On 04/28/2009 06:44 AM, das wrote:
>  On Sat, Apr 25, 2009 at 10:06 AM, Rahul Sundaram
>  <sundaram(a)fedoraproject.org&gt; wrote:
>  
> > It is likely that imsettings (there is no specific subpackage for GNOME)
> > was a direct dependency for some package you cherry picked. You would
> > have to trace the exact steps to figure out which one. 
CC'ing Kevin Fenzi, who is the Xfce maintainer in Fedora.



> >
>  
>  Yesterday I installed F11 on a Lennovo laptop, with an F11 beta DVD.
>  
>  After the installation was over (with software customization set
>  'later', no software or repositories added, everything default), I
>  made a reboot, and logged in, and it was a Gnome, obviously. And the
>  interesting point is, here iBus was working and I added a Bangla
>  Probhat keyboard in iBus and on a Gedit window I typed Bangla at ease.
>  
>  Now I made 'yum -y update' and did a reboot, and still iBus Bangla
>  Probhat was working.
>  
>  Now I installed the group XFCE and rebooted and logged in into Xfce,
>  and iBus did not work, the usual problem, as reported in the bug your
>  OP quoted.
>  
>  Now I installed yumex and got into yumex. Searched for the string
>  'imsetting' and saw that a package named 'imsetting' was installed,
>  and as expected, another package named 'imsetting-xfce' was there but
>  it was not installed, as you predicted, which now I did and it worked.
>  
>  So, there was a default 'imsetting' that was being used by Gnome. So,
>  it does not matter, if Gnome did not have its own imsetting package.
>  It was using the system-wide default. And not that any package
>  selected by mine did make it happen. It happened by default.
>  
>  And Xfce, even when the system-wide 'imsetting' is installed and
>  working and the group 'XFCE' is called for install, is not installing
>  its own version of imsetting. A working system is rendered unworkable
>  (by 'work' in terms of iBus) by adding Xfce. Do you think it is an
>  expected behavior of 'groupinstall XFCE'?
>  
>  What the whole OS is doing on its system default, is getting broken by
>  installing XFCE, a part added to the whole. Do you consider it as a
>  bug?
>