On 18/09/15 06:26, Luca Delucchi wrote:
On 18 September 2015 at 04:45, Vaclav Petras <[email protected]> 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.
I think we should really look at the QGIS example for inspiration. The
system works quite well, uses sphynx, and allows creation of HTML and
PDF [1].
We might even consider using (at least some chapters of) the QGIS
training manual and adapt it to GRASS...
internationalization is the main topic, I think, we should provide it or not?
I think that we should think the infrastructure in a way that makes it
easy to translate. It will then be up to the language communities to
organise translation if they want to. I think both the French and German
communities are quite active on that level, for example.
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.
We can then show a mixed version, with only the translated parts shown
in the desired language, the rest in English. This is how it works for
the QGIS manuals.
Use some simple tool as Transfixer [0] maybe could be useful
Yes, I think so. This makes translation really easy and allows anyone to
participate (e.g. easy organisation of translation sprints).
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.
+1 (but let's create it first ! ;-)
Moritz
[1]
https://github.com/qgis/QGIS-Documentation/tree/master/source/docs/training_manual
_______________________________________________
grass-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-dev
