[GRASS-dev] Collecting ideas for training manual for GRASS GIS

[Blumentrath, Stefan]

>From my experience the need for internationalization varies very much and depends on a lot of things (one of them is culture and exposure to foreign esp. English language).
Here in Norway, I guess no one would really miss a translation to Norwegian, as e.g. kids-TV, movies in the Cinema, and so on are not dubbed (like in e.g. the Netherlands). Actually, we even turn the GUI to English to have it aligned with manuals.

However, in other countries things can be quite different...

Personally, I would not spend an effort on translation into many languages but maybe (max) a few central ones, meaning: Spanish, and maybe Portuguese and / or French (no ideas about the importance of Asian or Arabic languages or Russian)...

Anyway, better to have one good annual in English than having lots of halfway translations.

Finally, terms in spatial analysis are often not too straight forward to translate and sometimes end up in funny translations...

Cheers
Stefan


-----Original Message-----
From: grass-dev-bounces at lists.osgeo.org [mailto:grass-dev-bounces at lists.osgeo.org] On Behalf Of Luca Delucchi
Sent: 18. september 2015 06:27
To: Vaclav Petras <wenzeslaus at gmail.com>
Cc: Moritz Lennert <moritz.lennert at ulb.ac.be>; GRASS-dev <grass-dev at lists.osgeo.org>
Subject: Re: [GRASS-dev] Collecting ideas for training manual for GRASS GIS

On 18 September 2015 at 04:45, Vaclav Petras <wenzeslaus at gmail.com> wrote:
> (Was: Re: [GRASS-dev] FOSS4G 2016 code sprint)
>
> Hi Moritz and Luca,
>

Hi Vaclav,

>>
>> We could also start a discussion about the software to use and create 
>> a repository and try to start to centralize the material already 
>> existing
>
> from technical point of view, we are now using HTML pages (which can 
> be tutorials as well, not only manual pages), wiki and then all other things.
> If we want to allow for an internationalization, that's yet another 
> question.
>

internationalization is the main topic, I think, we should provide it or not?
for some reason yes, newbie some times would like to have material in their native language, for some other reason is really difficult to maintain it updated because people start to work on it and after disappear.

Use some simple tool as Transfixer [0] maybe could be useful

> For the sources I'm involved in, you can have a look at:
>
> http://geospatial.ncsu.edu/osgeorel/courses.html
>
> in particular:
>
> http://courses.ncsu.edu/gis582/common/grass/
> http://ncsu-osgeorel.github.io/erosion-modeling-tutorial/grassgis.html
> http://ncsu-osgeorel.github.io/grass-temporal-workshop/
> http://ncsu-osgeorel.github.io/uav-lidar-analytics-course/assignments/
> lidar.html 
> http://ncsu-osgeorel.github.io/uav-lidar-analytics-course/assignments/
> water_flow.html http://ncsu-osgeorel.github.io/grass-intro-workshop/
> http://www4.ncsu.edu/~akratoc/GRASS_intro/
>

this is really cool material I have some question:
- could be this documentation moved in some official GRASS page (maintaining of course ncsu affiliation)
- do you have any idea how simple could be translate it?

> Ideally, the things should be in the OSGeo Educational Content 
> Inventory and we should be adding the stable or valuable things there 
> as we are collecting them.
>
> http://www.osgeo.org/educational_content?filter1=grass
>
> Vaclav

[0] https://www.transifex.com/

--
ciao
Luca

http://gis.cri.fmach.it/delucchi/
www.lucadelu.org
_______________________________________________
grass-dev mailing list
grass-dev at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev