Summary: | Translation/localization packages and new category for them | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alexander Dubov <oakad> |
Component: | New packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED WONTFIX | ||
Severity: | enhancement | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Alexander Dubov
2005-12-18 06:43:54 UTC
Like creating about a zillion of ebuilds for each available i18n-compliant ebuild and LINGUA? Sorry, that's what LINGUAS variable is for, there's really no need to clutter portage tree with tons of such duplicate ebuilds for each language. I'm constantly working with multi-language installations (> 4 languages). The problem is that some i18n ebuilds take longer to rebuild than application itself. Then, if you consider the fact that not all application require translation and that some translations for kde-i18n are already more than 30MB in size it is not too far fetched to create separate ebuilds for such translations. Additionally, not all applications require translations and not every application is translated to every language. Now, my desire is to have a setup which would allow me to move toward complete translation of my working environment. This means at least two things: ability to update translation for some language without affecting others and ability to query current status of translations to a given language. To my opinion current arrangement interferes quite strongly with this goal. |