El dg 28 de 03 de 2010 a les 22:19 +0000, en/na Rainer Oliveira va
escriure:
> I don't know if this is related, but I'm running Lucid (as of march
> 28th) and ubiquity is still showing the slideshow in pt_PT instead of
> pt_BR (as I selected from the beginning).
>
> But the interesting thing is that even if I install the language pack (pt_BR) after the instalation, Firefox and computer-janitor continues to be in pt_PT (and not in pt_BR).
> I also remembered running Kubuntu Lucid some days ago and some programs were also in pt_PT.
>
> Could it be a more complex problem?
>
> Thanks.
>
Rainer,
Thanks for your comment. I've got a few questions for you:
* Did you have to manually install the pt_BR language pack after
the installation?
* If so, how did you do it?
* After the installation on the system you're experiencing the
problem, what's the output of the 'locale' command on the
terminal? (in case you are not used to work with the terminal,
you might find this useful: https://help.ubuntu.com/community/UsingTheTerminal)
This will help in determining whether we need to open a separate bug for
your problem.
El dg 28 de 03 de 2010 a les 22:19 +0000, en/na Rainer Oliveira va
escriure:
> I don't know if this is related, but I'm running Lucid (as of march
> 28th) and ubiquity is still showing the slideshow in pt_PT instead of
> pt_BR (as I selected from the beginning).
>
> But the interesting thing is that even if I install the language pack (pt_BR) after the instalation, Firefox and computer-janitor continues to be in pt_PT (and not in pt_BR).
> I also remembered running Kubuntu Lucid some days ago and some programs were also in pt_PT.
>
> Could it be a more complex problem?
>
> Thanks.
>
Rainer,
Thanks for your comment. I've got a few questions for you:
* Did you have to manually install the pt_BR language pack after /help.ubuntu. com/community/ UsingTheTermina l)
the installation?
* If so, how did you do it?
* After the installation on the system you're experiencing the
problem, what's the output of the 'locale' command on the
terminal? (in case you are not used to work with the terminal,
you might find this useful:
https:/
This will help in determining whether we need to open a separate bug for
your problem.