Frameworks/Epics/KF5.0 Release Preparation/l10n

Preparation

Status	Task
DONE	Decide where to place Messages.sh (src by default?)
IN PROGRESS	Define the way to extract translations for Qt-based frameworks. Patches under review.
DONE	Investigate whether it is possible to have Qt-based frameworks automatically load their transitions
TO DO	Check the release scripts to ensure they include the .po or .ts files as well as the matching CMake code to build and install them.	<{{{3}}}>

For each framework the following needs to be done:

Make sure all strings that need to be translated are either wrapped by i18n*() or tr*() depending on the translation API of choice.

If there is no Messages.sh file in the repository, create a src/Messages.sh file. See http://techbase.kde.org/Development/Tutorials/Localization/i18n_Build_Systems#handling_i18n_in_KDE.27s_subversion_repository for details on how to create and test it.

If there are Messages.sh files, check they are still relevant.

Things to test:

Make sure the Messages.sh files extract all the files
Make sure the Messages.sh files create catalogs with correct names. Look out for catalogs with '4' suffix, or catalogs whose name would clash with an existing KDE4 library.

If using ki18n, make sure it follows http://api.kde.org/frameworks-api/frameworks5-apidocs/ki18n/html/prg_guide.html#link_lib . In short: Check all files with calls to i18n*() define TRANSLATION_DOMAIN before including KLocalizedString.

If using tr(), make sure the list of source files include ${ECM_TR_LOADER}.

Framework list:

Status	Task
TO DO	Add src/Messages.sh script	<{{{3}}}>
TO DO	Check TRANSLATION_DOMAIN is set	<{{{3}}}>
TO DO	Integrate translation compilation code	<{{{3}}}>

Framework list:

Status	Task
DONE	Add src/Messages.sh script
DONE	Check QObject::tr is correctly used
TO DO	kwidgetsaddons: Check data for KCharSelectData is marked as translatable. See FIXME in the code	<{{{3}}}>
TO DO	Integrate translation compilation code	<{{{3}}}>