[GRASS-dev] Re: [bug #5195] (grass) ps.map sets encoding to
hamish_nospam at yahoo.com
Tue Oct 10 22:09:27 EDT 2006
> Ok, so the only thing to do seems to be a note in the man page.
> Does the attached patch look alright ?
RCS file: /grassrepository/grass6/ps/ps.map/description.html,v
retrieving revision 1.45
diff -u -r1.45 description.html
--- ps/ps.map/description.html 19 Jul 2006 10:08:31 -0000 1.45
+++ ps/ps.map/description.html 10 Oct 2006 13:31:33 -0000
@@ -20,7 +20,9 @@
This program has two distinct modes of operation. The command-line
mode requires the user to prepare a file of mapping instructions prior
to running <EM>ps.map</EM> that describes the various spatial and textual
-information to be printed.
+information to be printed. For users wanting to use special characters (such as accented characters) it is important to not that ps.map uses ISO-Latin1 encoding. This means that your instructions file will have to be encoded in this encoding. If you normally work in a different encoding environment (such as UTF-8), you have to transform your file to the ISO-latin1 encoding, for example by using <EM>iconv</EM>:
+<EM>iconv -f UTF-8 -t ISO_8859-1 utf_file > iso_file</EM>
The interactive mode (i.e., no command-line arguments) will prompt the
user for items to be mapped and does not require the user
It reads well. A few suggestions:
- this probably belongs in the NOTES section, not the DESCRIPTION
section of the help page.
- typo: "it is important to not that" s/not/note/
- please break lines before the 80th column
- "code" examples should be html-ized as follows:
(also in the above you forgot <BR> or <P> to separate the line)
iconv -f UTF-8 -t ISO_8859-1 utf_file.txt > iso_file.txt
More information about the grass-dev