Archive:L10N/Access
From FedoraProject
It has been requested that this page be deleted.
Deprecated content, also duplicated
Deprecated content, also duplicated
The Fedora Localization Project - Repository access for translations
- All translatable modules related to Fedora are listed on: http://translate.fedoraproject.org/module/.
- Modules hosted outside
cvs.fedoraproject.orgrequire special treatment for sending translations. Either you'd need an account on the system, open a bug report for the maintainer to commit your translation, or use a special system to submit the translation.
The following is a rough list of the repos that are related to translations. To see which is used for each module, please refer to: http://translate.fedoraproject.org/module/. Ideally, these all should be accessible by fedora translators through Transifex soon.
cvs.fedoraproject.org |
This is the main CVS server for Fedora. The accounts are handled by the Fedora Account System; translators are considered all the members of the cvsl10n group. Instructions for joining the Fedora Localization Project can be found on the page L10N/Join . The following three repositories exist in it:
|
/cvs/docs/ -- Translators have access to the /po/* subdirectories. To translate Documentation, checkout the appropriate module from the docs repository. For more information, refer to DocsProject/Translation .
| |
/cvs/l10n -- Translators have access to the whole repo.
| |
/cvs/pkgs -- Translators have access to the /po/* subdirectories.
| |
svn.fedorahosted.org |
To submit files, use Transifex . |
hg.fedorahosted.org |
To submit files, use Transifex . |
git.fedorahosted.org |
To submit files, use Transifex . |
http://linux.duke.edu/yum/git |
No direct access for Fedora translators. To submit PO files, open a bug report at bugzilla.redhat.com.
|
- Project maintainers who would like to receive translations for their project should provide translators with access on their Version Control System (CVS, SVN, etc).
- To add a new language, either a Makefile should be edited and the language code should be appended in the appropriate line, or a file called LINGUAS should exist inside the
po/directory, which lists the published languages of the module. - CVS automations usually take place, so that translators can checkout a module containing just the po subdirs instead of the whole source code.
