From Fedora Project Wiki
No edit summary
Line 8: Line 8:
* Email: [mailto:petersen@redhat.com petersen@redhat.com]
* Email: [mailto:petersen@redhat.com petersen@redhat.com]


== Stato attuale ==
== Stato corrente ==
* Rilascio: [[Releases/13|  Fedora 13]]
* Rilascio: [[Releases/13|  Fedora 13]]
* Per informazioni aggiornate sullo stato del progetto consultare la [[Features/YumLangpackPlugin#Current_status | pagina originale]] di questo documento.
* Per informazioni aggiornate sullo stato del progetto consultare la [[Features/YumLangpackPlugin#Current_status | pagina originale]] di questo documento.
Line 18: Line 18:


This feature will also allow firefox and thunderbird to earn langpacks as they deserve.
This feature will also allow firefox and thunderbird to earn langpacks as they deserve.
Here is an outline of the design and current assumptions:
# add langpack-support-<lang> metapackage for each language, which users can install if they want langpack support for the language
# the langpack metapackages will all require yum-plugin-langpacks
# langpack-support-<lang> metapackages will be added to the comps lang support groups
# when user activates yum (eg through PackageKit) the plugin will check if langpacks are needed or available for the packages involved in the transaction
# maybe keep conditional lang entries for now in F12 and drop them later in F13 say
Optional/longer term ideas (likely deferred for later).
# allow for whitelisting/blacklisting of specific langpacks
# setting for which langs appear by default in gdm lang top menu ([https://bugzilla.redhat.com/show_bug.cgi?id=505484 rfe bug])
# recommendation for Packaging Guideline for standard naming of langpacks (eg <basename>-langpack-<lang>)
# (longterm) extend to handling gettext translation .mo files
=== anaconda ===
Anaconda will need to require yum-plugin-langpacks and enable it by default (as outlined in the above mail).
Additionally the plugin must be able to take into account new langpack-support metapackages being added in an rpm transaction when determining langpacks (not just currently installed langpack-support metapackages).
=== gdm ===
Explain https://bugzilla.redhat.com/show_bug.cgi?id=505484 here.
=== pungi ===
For pungi, since all the langpack-support metapackages will be listed in comps if it also requires and enables yum-plugin-langpacks it should be able to pull in the corresponding langpacks needed to compose Fedora trees, etc.
=== livecd-tools ===
livecd-tools probably also needs to require yum-plugin-langpacks and enable it.  Currently the official Live Spins don't actually include any @lang-support groups. Localized spins should list any required langpack-support-<lang> meta package or @<lang>-support group anyway in their kickstart file.
=== comps ===
Once the feature is available in Rawhide all the metapackages will be added to the respective language support groups in comps.
=== yum ===
Rather than making changes to each of the tools using Yum (as outlined above) it might be easier just to enable the langpack plugin in yum by default to avoid having to change Yum code in multiple places?


== Vantaggi per Fedora ==
== Vantaggi per Fedora ==

Revision as of 19:33, 3 February 2010

Plugin Yum Langpack

Sommario

Un plugin di yum per installare automaticamente, se disponibili, i pacchetti tradotti nella propria lingua in fase di installazione dei pacchetti base.

Progettista

Stato corrente

Descrizione dettagliata

Currently when users install packages with langpacks they have to install the langpacks themselves by hand (if they even know about them).

Last year in a related thread on fedora-devel-list Bill Nottingham posted an initial proof of concept of this plugin. This feature will polish that further and make it ready for general use. (See also this rfe bug.)

This feature will also allow firefox and thunderbird to earn langpacks as they deserve.

Vantaggi per Fedora

Gli utenti, volendo, potranno installare i pacchetti, tradotti nella loro lingua.

Altre informazioni

Per:

  • Obbiettivi
  • Test Plan
  • Esperienza Utente
  • Dipendenze
  • Progetto corrente
  • Documentazione
  • Note di rilascio
  • Commenti e Discussioni

consultare la pagina originale di questo documento.