-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
setup localization via Transifex #3
Comments
This is now setup (thanks @rduivenvoorde for debugging) at https://www.transifex.com/projects/p/MetaSearch. Notes:
Workflow:
|
done. Process:
This results in a fully translated package to work against, package and upload. @rduivenvoorde: the last outstanding item is docs/website. Is there another structure we should do to make things better? How does QGIS do it? As well, we need a way to provide language selection in the docs. |
As well, foreach language, perhaps we can add the following steps to
|
Hi Tom, with the QGIS sites we use sphinx-intl (https://pypi.python.org/pypi/sphinx-intl) we only keep resources(=images etc) separated per language, where 'en' is the base-one and other can be copied over it. Sources are only en, and translations are only available as po files in i18n/locale dir. Themes are also not localized (some right to left magic via separate css file). So in the build dir we first copy all english images (from resources/en so we have an english 'base'), and then we overwrite them with (optionally) available localized images (with exact the same name in resources/xx). see https://github.com/qgis/QGIS-Website/blob/master/Makefile#L87-L114 |
Done. Website updated with multilingual docs/setup. |
Applied to both plugin and docs.
The text was updated successfully, but these errors were encountered: