#846: manpages translations - where to put them?
--------------------------+-------------------------------------------------
Reporter: steko | Owner: grass-dev@lists.osgeo.org
Type: enhancement | Status: new
Priority: normal | Milestone: 6.5.0
Component: Docs | Version: 6.4.0 RCs
Keywords: translations | Platform: All
Cpu: All |
--------------------------+-------------------------------------------------
The GRASS Italian community (Marco Curreli being the leader by far) has
been translating since some years (even though at a low pace) some GRASS
commands manpages (the description.html part). We plan to translate them
all, perhaps doing a Translation Sprint when possible. I have collected
the existing translations at http://bitbucket.org/steko/grass-doc-it/ and
I also plan to retrieve the existing translations which were done in the
GFOSS.it wiki for GRASS GIS 6.0.2 and possibly update them.
The question is how to make these translations available to GRASS users?
On the grass-translations list, Markus Neteler and I agreed that the best
place would obviously be the GRASS source tree http://lists.osgeo.org/pipermail/grass-translations/2009-
December/000544.html as Markus said "''We need to modify the Makefile
system to recognize the translated pages and generate the page header in
the related locale.''"
I hope something can be done about this, it would make our work even more
motivated.
#846: manpages translations - where to put them?
--------------------------+-------------------------------------------------
Reporter: steko | Owner: grass-dev@lists.osgeo.org
Type: enhancement | Status: new
Priority: normal | Milestone: 6.5.0
Component: Docs | Version: 6.4.0 RCs
Resolution: | Keywords: translations
Platform: All | Cpu: All
--------------------------+-------------------------------------------------
Comment (by glynn):
Replying to [ticket:846 steko]:
> Markus said "''We need to modify the Makefile system to recognize the
translated pages and generate the page header in the related locale.''"
>
> I hope something can be done about this, it would make our work even
more motivated.
The main question is whether the build process should generate manual
pages for all supported languages, or just for a single language.
Obviously, the former is harder than the latter. In particular, supporting
multiple languages requires us to decide the target directory structure
and file names; for a single language, we can continue to use the existing
layout.
#846: manpages translations - where to put them?
--------------------------+-------------------------------------------------
Reporter: steko | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone: 6.5.0
Component: Docs | Version: 6.4.0 RCs
Keywords: translations | Platform: All
Cpu: All |
--------------------------+-------------------------------------------------
Comment(by neteler):
As a first approach I would suggest to stick with single language support
at compile time. Means to compile individually for each locale which will
be the common use case.