You are not logged in.

#1 2020-12-01 19:29:34

alicavus
Member
Registered: 2020-12-01
Posts: 2

package localization in PKGBUILD (i18n and l10n)

Hi!

I am thinking over localization of package related information like description, opt/make dependencies etc. in PKGBUILD files.

When user run

pacman -Qi packagename

package related information is not translated (pacman itself is).

Maybe in future will be possible to translate pkgdesc optdeps fields...

Offline

#2 2020-12-02 14:03:14

mpan
Member
Registered: 2012-08-01
Posts: 641
Website

Re: package localization in PKGBUILD (i18n and l10n)

PKGBUILD is just a bash script, so one may customize content based on the current locale.

What you are asking for is having a multilanguage version of .PKGINFO entries. While adding support for that in libalpm might be easy, one faces the common obstacle: who will maintain the translation?


Sometimes I seem a bit harsh — don’t get offended too easily! PGP: 7C848198AE93D3BB

Offline

#3 2020-12-03 12:11:00

alicavus
Member
Registered: 2020-12-01
Posts: 2

Re: package localization in PKGBUILD (i18n and l10n)

Translation works are done by translators, like in every FLOSS project. Who will maintain - the translation team I guess.

Offline

#4 2020-12-03 18:24:52

mpan
Member
Registered: 2012-08-01
Posts: 641
Website

Re: package localization in PKGBUILD (i18n and l10n)

The question was not about what title will those persons bear. I was asking who would that be. People do not appear out of thin air.

Last edited by mpan (2020-12-03 18:25:06)


Sometimes I seem a bit harsh — don’t get offended too easily! PGP: 7C848198AE93D3BB

Offline

#5 2020-12-04 05:36:48

eschwartz
Trusted User/Bug Wrangler
Registered: 2014-08-08
Posts: 3,936

Re: package localization in PKGBUILD (i18n and l10n)

alicavus wrote:

Hi!

I am thinking over localization of package related information like description, opt/make dependencies etc. in PKGBUILD files.

Opt dependencies include English descriptions. Make dependencies don't.

Only the description field and the optdepends text after ":" are relevant to the discussion.

And we're most likely not adding a feature that isn't useful, so unless someone comes up with a proposal to crowdsource descriptions which aren't known ahead of time and cannot be added after the fact...
(Note that gettext catalogs can be shipped separately from the application they translate.)


Managing AUR repos The Right Way -- aurpublish (now a standalone tool)

Offline

Board footer

Powered by FluxBB