[paludis-dev] [Paludis] #122: Native Language Support

Paludis trac at pioto.org
Sat Sep 3 19:24:13 UTC 2011


#122: Native Language Support
-----------------------------+---------------------
    Reporter:  ciaranm       |      Owner:  ciaranm
        Type:  enhancement   |     Status:  closed
    Priority:  ProjectIdeas  |  Milestone:
   Component:  core/paludis  |    Version:
  Resolution:  wontfix       |   Keywords:
  Blocked By:                |   Blocking:
Distribution:  Gentoo        |
-----------------------------+---------------------
Changes (by ciaranm):

 * status:  new => closed
 * distribution:   => Gentoo
 * resolution:   => wontfix


Old description:

> Paludis should include native language support. Adding this consists of:
>
>  * Converting the code over to use some kind of internationalisation
> framework. This will probably be gettext.
>  * Ensuring that the code (particularly the ebuild bash code) doesn't
> rely upon quirks that are only true for POSIX locales. Currently there
> are a few places where we do things like 'tr a-z ...'. These will need
> identifying and fixing.
>  * Providing at least one complete translation.
>  * Unit tests.
>
> This is not as simple as it might appear. Gettext more or less assumes
> that people are using printf-style format strings. We don't. We use C++
> standard library streams instead, because we like the type safety. Any
> proposed solution must not involve giving up type safety.
>
> Ideally, a solution that doesn't result in the package breaking if
> gettext breaks should be used. Because Paludis is often used as a key
> system component, we try to avoid hard linking to additional libraries.
> The current selinux handling can be seen as an example of how to do this.
>
> Interested parties are invited to discuss this with us on IRC.

New description:

 Paludis should include native language support. Adding this consists of:

  * Converting the code over to use some kind of internationalisation
 framework. This will probably be gettext.
  * Ensuring that the code (particularly the ebuild bash code) doesn't rely
 upon quirks that are only true for POSIX locales. Currently there are a
 few places where we do things like 'tr a-z ...'. These will need
 identifying and fixing.
  * Providing at least one complete translation.
  * Unit tests.

 This is not as simple as it might appear. Gettext more or less assumes
 that people are using printf-style format strings. We don't. We use C++
 standard library streams instead, because we like the type safety. Any
 proposed solution must not involve giving up type safety.

 Ideally, a solution that doesn't result in the package breaking if gettext
 breaks should be used. Because Paludis is often used as a key system
 component, we try to avoid hard linking to additional libraries. The
 current selinux handling can be seen as an example of how to do this.

 Interested parties are invited to discuss this with us on IRC.

--

Comment:

 I've come to the conclusion that NLS is Satan's work.

-- 
Ticket URL: <http://trac.pioto.org/paludis/ticket/122#comment:2>
Paludis <http://paludis.pioto.org/>
Paludis, the Other Package Mangler


More information about the paludis-dev mailing list