No edit summary |
(added some info) |
||
| Line 1: | Line 1: | ||
I would like to propose naming guidelines for adding language translation packages for any package. I see few packages are not following package naming of using language code only. | == Proposal == | ||
I would like to propose naming guidelines for adding language translation packages for any package. I see few packages are not following package naming of using language code only. The reason behind proposing this guidelines is to have some uniqueness in translated language package naming. Other one is for package yum-langpacks which is going to use these package names to determine which languages are available in the current repository. The yum-langpacks langavailable command reads ending -<langcode> in rpm name and uses that as that language support is available. So if some packages virtually provides <pkgname>-<langcode> that language will not be considered in langavailable command. | |||
Package maintainers can virtually provide package names as <pkgname>-<fulllanguagename> but real package name should be <pkgname>-<langcode> | |||
The current inconsistencies I found are for packages | The current inconsistencies I found are for packages | ||
| Line 14: | Line 17: | ||
When adding language translations, package name should end with that language code for that language. | When adding language translations, package name should end with that language code for that language. | ||
These language codes must be valid and used from /usr/share/xml/iso-codes/iso_639_3.xml or from /usr/share/i18n/locales. | These language codes must be valid and used from /usr/share/xml/iso-codes/iso_639_3.xml or from /usr/share/i18n/locales. | ||
The real package name should be <pkgname>-<langcode> | The real package name should be <pkgname>-<langcode> | ||
</pre> | </pre> | ||
Revision as of 09:22, 24 September 2013
Proposal
I would like to propose naming guidelines for adding language translation packages for any package. I see few packages are not following package naming of using language code only. The reason behind proposing this guidelines is to have some uniqueness in translated language package naming. Other one is for package yum-langpacks which is going to use these package names to determine which languages are available in the current repository. The yum-langpacks langavailable command reads ending -<langcode> in rpm name and uses that as that language support is available. So if some packages virtually provides <pkgname>-<langcode> that language will not be considered in langavailable command.
Package maintainers can virtually provide package names as <pkgname>-<fulllanguagename> but real package name should be <pkgname>-<langcode>
The current inconsistencies I found are for packages
kde-l10n-* uses language names and in some subpackages language aliases like British, Brazil, Farsi, LowSaxon which are not real language names. tesseract-langpack-* uses some own defined 3 letter language codes. I reported bug to rename them but virtual provides added by its maintainer. childsplay-alphabet_sounds_* this uses language code correctly but it should end with -<langcode> and not with _<langcode>
So the proposal is
When adding language translations, package name should end with that language code for that language. These language codes must be valid and used from /usr/share/xml/iso-codes/iso_639_3.xml or from /usr/share/i18n/locales. The real package name should be <pkgname>-<langcode>