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
Add support for internationalization (i18n) on Mapserver docs #7
Add support for internationalization (i18n) on Mapserver docs #7
Conversation
@jmckenna where you going to merge this request? -Steve |
Add support for internationalization (i18n) on Mapserver docs
@ThomasG77 can you test with master? (I don't yet understand all the changes you made) Also, can you update the "Documentation Guide" (there is a translations section): \en\development\documentation.txt |
this was with master (not the live branch-6-0) correct? (all dev work for docs happen in master) Please verify (otherwise, if it is live then we better make sure it works) |
@ThomasG77 we may have to undo these changes as they were made to the live site. @ThomasG77 can you submit these changes to Master so we can first test there on the server, before the changes are applied to the live site? |
as request by @jmckenna I have reverted this merge. @ThomasG77 can you submit this against master, and explain how the docs should be built with this new system (by just running "make" the docs in "fr" are all in english. I tried running "make init" only to have my whole repo completely messed up with bogus files) |
I will submit during this week on master branch. tbonfort, for an overview, you'll find below a fast how to before I update the rst documentation for translation and resubmit to master branch. Install recent sphinx 1.1.x and install gettext package
|
Hello,
I've added support for i18n for Mapserver docs
You will find a doc about my purpose to do this and an how to
https://github.com/ThomasG77/docs/wiki/How_to-i18n
As said in the the doc above
"As I don't want to reinvent the wheel, I've modified the Makefile/make.bat to deal with both "old" system and new one. So people happy with old system, keep it this way and other can migrate to i18n."
For the french case, there is no regression (I've already backported the existing doc and added new pages translation)
The workflow to make translation will maybe need to change because of this i18n support.
All the gettext generation is not really needed for end user, he only need to edit *.po files.
Input from friendly Qgis community can help maybe e.g http://translate.qgis.org/ and
https://github.com/qgis/QGIS-Documentation part "Translators edit workflow"
Any input is welcome. Hope you will accept my pull.
Regards
PS: I've forgotten to deleted the fr dir in the root directory: depend from your acceptance of my pull