[GRASS-dev] encoding of manual pages
Glynn Clements
glynn at gclements.plus.com
Sun Aug 27 08:07:17 EDT 2006
Jachym Cepicky wrote:
> manual pages displayed with g.manual do have wrong encoding, which does
> not need to fit system encoding settings.
>
> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
>
> people, who are using iso-8859-2 or utf-8 will get unsuable character
> encoding:
>
> http://les-ejk.cz/tmp/Obrazovka-2.png
> should be
> http://les-ejk.cz/tmp/Obrazovka-3.png
>
> because of the manual pages are generated while system compilation, I
> would suggest:
>
> - generate english version of manual pages by default
> or
> - the script for manpage generation should set propper header based
> on system encoding
>
> what do you thing?
Generate English manual pages. All of the description.html files are
in English; it's only the portions which are auto-generated via
--html-description which will be localised.
This should be sufficient:
diff -u -r1.9 include/Make/Html.make
--- include/Make/Html.make 2 Jul 2006 20:28:59 -0000 1.9
+++ include/Make/Html.make 27 Aug 2006 11:57:37 -0000
@@ -92,7 +92,7 @@
GISBASE=$(GISBASE) \
PATH=$(GISBASE)/bin:$$PATH \
$(LD_LIBRARY_PATH_VAR)="$(GISBASE)/lib:$($(LD_LIBRARY_PATH_VAR))" \
- $(1) --html-description | grep -v '</body>\|</html>' > $(PGM).tmp.html ; true
+ LC_ALL=C $(1) --html-description | grep -v '</body>\|</html>' > $(PGM).tmp.html ; true
# html rules for cmd commands
htmlcmd: htmlcmd1 htmlgen
Alternatively, the build process could just generate an error if any
of the locale variables (LC_ALL, LC_*, LANG) are set (to something
other than "C" or "POSIX"). This would also eliminate the issue of
people including localised error messages when they report compilation
problems.
--
Glynn Clements <glynn at gclements.plus.com>
More information about the grass-dev
mailing list