1:30 p.m.
Hi,
I have the yum-langpacks plugin installed and it works. :-)
My problem in a sense is that it is limited in scope. :-(
http://fedoraproject.org/wiki/Features/YumLangpackPlugin was the feature page
for when the feature was initially deployed. The purpose of this is post is to
raise awareness for this feature and continue to have it implemented to have a
better experience for our users (from where developers are a subset).
1) "This feature will also allow firefox and thunderbird to earn langpacks as
they deserve."
In F15 asking
yum list *langpack*
shows that only
koffice
libreoffice
tesseract
support langpacks and tesseract has three letters acronyms for languages:
tesseract-langpack-bul
tesseract-langpack-cat
tesseract-langpack-ces
tesseract-langpack-chi_sim
tesseract-langpack-chi_tra
tesseract-langpack-dan
tesseract-langpack-dan-frak
tesseract-langpack-deu
tesseract-langpack-deu-frak
tesseract-langpack-ell
...
Searching to virtual provides we get:
repoquery --whatprovides \*langpack\*
this adds
moodle-<lang>
to the bundle.
2) In the Optional/longer term ideas:
"3. recommendation for Packaging Guideline for standard naming of langpacks
(eg <basename>-langpack-<lang>)"
This seems an easy step, both to standardize the form of <lang> as well as to
suggest a virtual provides to packages that already provide this, I am
thinking in this case of packages like kde-i18n* or kde-i10n*.
What do others think?
Regards,
--
José Abílio
1:23 a.m.
José Matos wrote:
1) "This feature will also allow firefox and thunderbird to
earn
langpacks as they deserve."
Yes that was my hope but it needs acceptance from the fedora mozilla packagers...
Support and encouragement is welcome.
In F15 asking
yum list *langpack*
shows that only
koffice
libreoffice
tesseract
You're oversimplifying: the plugin does not search for "langpack". :)
eg kde-l10n is already supported since F13 I think.
This seems an easy step, both to standardize the form of <lang>
as
well as to
suggest a virtual provides to packages that already provide this, I am
thinking in this case of packages like kde-i18n* or kde-i10n*.
Yes I think meta Provides is probably the way to go.
Concrete suggestions and design improvements are welcome - particularly in bugzilla. :-)
I think Bill Nottingham also has some more ideas in this direction.
Jens
12:45 p.m.
On Thursday 02 June 2011 07:23:34 Jens Petersen wrote:
I am sorry not to have replied before but in the place (local network) where I
have been I had access to imap but not smtp (weird I know) and it is klunky to
answer using a webmail interface. :-(
José Matos wrote:
> 1) "This feature will also allow firefox and thunderbird to earn
> langpacks as they deserve."
Yes that was my hope but it needs acceptance from the fedora mozilla
packagers... Support and encouragement is welcome.
So should we send them chocolate? ;-)
This feature is really a blessing for users/administrator who need to setup
localized interfaces.
> In F15 asking
> yum list *langpack*
> shows that only
>
> koffice
> libreoffice
> tesseract
You're oversimplifying: the plugin does not search for "langpack". :)
eg kde-l10n is already supported since F13 I think.
My mistake, sorry, I was in hurry and I did not read the code. It is nice to
see it and other similar packages supported.
> This seems an easy step, both to standardize the form of
<lang> as
> well as to
> suggest a virtual provides to packages that already provide this, I am
> thinking in this case of packages like kde-i18n* or kde-i10n*.
Yes I think meta Provides is probably the way to go.
Concrete suggestions and design improvements are welcome - particularly in
bugzilla. :-) I think Bill Nottingham also has some more ideas in this
direction.
Yes, I saw Bill's answer. Thank you for driving this feature your work is
really apreciated. :-)
Jens
--
José Abílio
7:05 p.m.
José Matos wrote:
I am sorry not to have replied before but in the place (local
network)
where I have been I had access to imap but not smtp (weird I know) and it
is klunky to answer using a webmail interface. :-(
And NNTP(S)?
This list is gatewayed as gmane.linux.redhat.fedora.devel on news.gmane.org
(NNTP) and snews.gmane.org (NNTPS), you can use any Usenet News client (e.g.
KNode) to read and post to this list.
Kevin Kofler
(who is using KNode to post this message)
7:26 p.m.
about language packs
in fedora we do
yum -y groupinstall "development tools"
but in portuguese
yum -y groupinstall "ferramentas de desenvolvimento"
and in spanish is another thing
its possible to change yum to accept both english and
internacionalized language ?
-
------------
Itamar Reis Peixoto
msn, google talk: itamar(a)ispbrasil.com.br
+55 11 4063 5033 (FIXO SP)
+55 34 9158 9329 (TIM)
+55 34 8806 3989 (OI)
+55 34 3221 8599 (FIXO MG)
7:54 p.m.
Itamar Reis Peixoto wrote:
about language packs
in fedora we do
yum -y groupinstall "development tools"
but in portuguese
yum -y groupinstall "ferramentas de desenvolvimento"
and in spanish is another thing
its possible to change yum to accept both english and
internacionalized language ?
You can use the internal identifier (which is never translated), i.e.:
yum groupinstall development-tools
Kevin Kofler
8:06 p.m.
On Mon, Jun 13, 2011 at 9:54 PM, Kevin Kofler <kevin.kofler(a)chello.at> wrote:
Itamar Reis Peixoto wrote:
> about language packs
>
> in fedora we do
>
> yum -y groupinstall "development tools"
>
> but in portuguese
> yum -y groupinstall "ferramentas de desenvolvimento"
>
>
> and in spanish is another thing
>
> its possible to change yum to accept both english and
> internacionalized language ?
You can use the internal identifier (which is never translated), i.e.:
yum groupinstall development-tools
Kevin Kofler
where I can get a list of internal identifiers
--
------------
Itamar Reis Peixoto
msn, google talk: itamar(a)ispbrasil.com.br
+55 11 4063 5033 (FIXO SP)
+55 34 9158 9329 (TIM)
+55 34 8806 3989 (OI)
+55 34 3221 8599 (FIXO MG)
3:50 a.m.
> You can use the internal identifier (which is never
translated),
> yum groupinstall development-tools
In F15, "yum grouplist" lists the identifier after each translation.
For earlier releases I think you may have to lowercase the English
and replace space by a hyphen? In the worst case one can check comps...
Jens
12:19 p.m.
On Tue, Jun 14, 2011 at 8:14 AM, Thomas Moschny
<thomas.moschny(a)gmail.com> wrote:
2011/6/14 Itamar Reis Peixoto <itamar(a)ispbrasil.com.br>:
> where I can get a list of internal identifiers
"yum grouplist -v" shows them.
Thomas Moschny <thomas.moschny(a)gmail.com>
thank you, its very useful when you're talking to a spanish person,
because you can tell the english names.
-
------------
Itamar Reis Peixoto
msn, google talk: itamar(a)ispbrasil.com.br
+55 11 4063 5033 (FIXO SP)
+55 34 9158 9329 (TIM)
+55 34 8806 3989 (OI)
+55 34 3221 8599 (FIXO MG)
2:30 a.m.
On Tuesday 14 June 2011 01:05:57 Kevin Kofler wrote:
And NNTP(S)?
This list is gatewayed as gmane.linux.redhat.fedora.devel on
news.gmane.org (NNTP) and snews.gmane.org (NNTPS), you can use any Usenet
News client (e.g. KNode) to read and post to this list.
Kevin Kofler
(who is using KNode to post this message)
I tried knode years ago but the messages composing and reading part was too
old and baroque when compared with kmail.
Since the outage with this work setup would be less than one week I decided
that it was not worth any effort to take a temporary workaround, :-)
--
José Abílio
10:28 a.m.
José Matos (jamatos(a)fc.up.pt) said:
My problem in a sense is that it is limited in scope. :-(
http://fedoraproject.org/wiki/Features/YumLangpackPlugin was the feature page
for when the feature was initially deployed. The purpose of this is post is to
raise awareness for this feature and continue to have it implemented to have a
better experience for our users (from where developers are a subset).
1) "This feature will also allow firefox and thunderbird to earn langpacks as
they deserve."
It certainly allows for it - it requires that the packagers take advantage
of it. ISTR discussions in the past that the mechanics of creating the
langpacks in the spec file wasn't something they wanted to deal with at the
time. yum-langpacks can't help with that part.
2) In the Optional/longer term ideas:
"3. recommendation for Packaging Guideline for standard naming of langpacks
(eg <basename>-langpack-<lang>)"
This seems an easy step, both to standardize the form of <lang> as well as to
suggest a virtual provides to packages that already provide this, I am
thinking in this case of packages like kde-i18n* or kde-i10n*.
These virtual provides should be there for any langpack that exists. I
suppose I should write an official packaging guideline for this.
Bill
12:44 p.m.
On Thursday 02 June 2011 16:28:56 Bill Nottingham wrote:
> 1) "This feature will also allow firefox and thunderbird to
earn
> langpacks as they deserve."
It certainly allows for it - it requires that the packagers take advantage
of it. ISTR discussions in the past that the mechanics of creating the
langpacks in the spec file wasn't something they wanted to deal with at the
time. yum-langpacks can't help with that part.
That is fair, thanks for the note.
> 2) In the Optional/longer term ideas:
> "3. recommendation for Packaging Guideline for standard naming of
> langpacks (eg <basename>-langpack-<lang>)"
>
>
>
> This seems an easy step, both to standardize the form of <lang> as well
> as to suggest a virtual provides to packages that already provide this,
> I am thinking in this case of packages like kde-i18n* or kde-i10n*.
These virtual provides should be there for any langpack that exists. I
suppose I should write an official packaging guideline for this.
That would be great, I think that this is a case where we can see the work
that is intrinsic to the coordination effort of a linux distribution.
Thank you for your work on this feature.
Bill
--
José Abílio
4698
days inactive
4711
days old
12 comments
6 participants
participants (6)
-
Bill Nottingham -
itamar -
Jens-Ulrik Petersen -
José Abílio Matos -
Kevin Kofler -
Thomas Moschny