[mapserver-users] Mapserver docs and i18n

[Jeff McKenna]

Hello Thomas,

Thank you for your contributions!

Before moving forward, I would like to hear more about the problems you
are having with restructured text files.  Now that we have moved to
Github I am noticing more contributions from users directly through
those rst/text files and their Github clones (wow excellent!).

Also, this is the first I have heard of problems with translated files
(a system has been in place for language support for several years now;
you can see all of the different translations in the source directory -
German, Spanish, French, Italian, and recently Chinese
https://github.com/mapserver/docs/tree/master).

So yes, I agree, before making any changes, let's have a high-level
public discussion about what is good currently, what is a
challenge/problematic, and how we can keep contributors happy in all
languages.  (a wise man once told me 'if it ain't broke don't fix it',
so it's good to discuss things before making changes)

Thanks for this discussion! :)

-jeff


-- 
Jeff McKenna
MapServer Consulting and Training Services
http://www.gatewaygeomatics.com/






On 12-07-03 11:58 AM, Thomas Gratier wrote:
> Hello list,
> 
> I've been working since some weeks on making i18n available in Mapserver
> docs. I've done some translation in the past of french part and I was
> fed up with maintaining rst files languages to languages and not simple
> shorts strings. For the french part, I've already backported all to i18n
> system.
> I've already submit a pull request (e.g
> https://github.com/mapserver/docs/pull/7) on Github but a community
> feedback is welcome because this request can change the way we do
> translations on the project.
> For already existing translation, things can stay as they 're depending
> on every langage community.
> You can read more about the process
> https://github.com/ThomasG77/docs/wiki/How_to-i18n
> All inputs are welcome against like for
> 
> Regards
> 
> ThomasG77
>