File: gettext.info, Node: Interfacing with the Translators, Next: Version Control Issues, Prev: autoconf macros, Up: Maintainers 14.6 Interfacing with the Translators ===================================== You need to decide whether your package joins a translation project or whether you want to connect to translators in an ad-hoc way. In a translation project, teams of translators work on a number of packages. They work together by exchanging common practice, technical dictionaries, or advice. Common translation projects are: • The "Translation Project" (https://translationproject.org/). This translation project is a good place for GNU packages. • The GNOME translation project (https://wiki.gnome.org/TranslationProject). This is the natural place for GNOME packages. • The KDE localization project (https://l10n.kde.org/). This is the canonical place for KDE packages. Note: KDE packages don't store their localizations in a ‘po/’ directory. • There are also many translation projects that use the Weblate (https://weblate.org/) localization suite. Connecting to translators in an ad-hoc way may be useful in the beginning if your package has highly specialized terms and translator volunteers already waiting. In the long term, though, you will get more language coverage by joining a translation team. When and how are the files in the ‘po/’ directory created, is related to this choice. See section *note Translations under Version Control?:: for details.
