Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 560116 - Gentoo ebuilds should have internal unified approach to i10n
Summary: Gentoo ebuilds should have internal unified approach to i10n
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: Normal enhancement (vote)
Assignee: Gentoo's Team for Core System packages
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-10 12:35 UTC by Arsen Shnurkov
Modified: 2015-09-26 07:34 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Arsen Shnurkov 2015-09-10 12:35:56 UTC
There is no guide on how to author documentation for new national-language programs.

Each ebuild does it in it's own way:
france, japan, debian:
https://github.com/gentoo/gentoo/blob/56bd759df1d0c750a065b8c845e93d5dfa6b549d/sys-process/fcron/fcron-3.1.2-r2.ebuild#L168-L174

https://github.com/gentoo/gentoo/blob/56bd759df1d0c750a065b8c845e93d5dfa6b549d/dev-util/debhelper/debhelper-9.20150628.ebuild#L55-L69

I propose to implement a new helper class man-i18n.eclass and add all that cycles there. But the most important piece - is the documentation for authors of new programs, how they should name their man files in their native languages.

Reproducible: Always
Comment 1 Zac Medico gentoo-dev 2015-09-10 16:30:31 UTC
You could post your proposal on the gentoo-dev mailing list. That's where we discuss new eclasses.
Comment 2 Zac Medico gentoo-dev 2015-09-10 16:33:10 UTC
Assigning to base-system, since they would be the likely maintainers of your proposed eclass.
Comment 3 Markos Chandras (RETIRED) gentoo-dev 2015-09-10 20:40:01 UTC
Ben already maintains the l10n eclass so he may be interested in this one as well.
Comment 4 SpanKY gentoo-dev 2015-09-11 05:24:18 UTC
you mean i10n (localization), not i18n (internationalization).  we have a unified format already for users (you set LINGUAS), but leave it up to developers to manage IUSE however they want in their ebuild.

wrt man category naming, there's already a standard, and that is beyond Gentoo.  in that regard, both ebuilds you highlight are doing the same thing.

so what exactly is it you expect man-i10n.eclass (not man-i18n) to do ?