Hello all,
I'm using ps.map and I notice that accent are not well supported in 3 cases :
- map scale units, for example "kilomètre" is displayed "kilomÄ"tre". I dont'see how to solve that
- for a selecting field in vector map, like [where myfield = "classé"] (does not work) while [where myfield = "classe"] (works if I change my "é" with "e" in the attribute data). I can solve that by adding an other field in my table without accent.
- labels : labels created with v.label seems to cannot support accent. Is there any way to solve this ?
my ps.map file are encoded in ISO-8859-1 and other text works well with accent. I saw that an environment variable exist : GRASS_DB_ENCODING but I don't know how to see it and if I change if it would damage my data table ...
Is anybody can advice me ?
I'm using Grass 7.4.1 on debian9
Thank you for your help,
Frank
On Tue, 30 Oct 2018, Frank David wrote:
- map scale units, for example "kilomètre" is displayed "kilomÄ"tre". I
dont'see how to solve that
- for a selecting field in vector map, like [where myfield = "classé"]
(does not work) while [where myfield = "classe"] (works if I change my "é"
with "e" in the attribute data). I can solve that by adding an other field
in my table without accent.
- labels : labels created with v.label seems to cannot support accent. Is
there any way to solve this ?
It would be beneficial to all of us who use ps.map, especially via
g.gui.psmap for ititial layout, if there were configuration options
available. In addition to language support being able to change the default
page size from A4 would be helpful.
Rich
On Tue, 30 Oct 2018, Frank David wrote:
I think some point are missing or lack of documentation. I think about
[read] command, display layer order, language support, unit of position in
the page (inch/cm), etc. Some improvement would be great, like line
thickness from column for example, accent support from v.label (??)...
Frank,
Yes, there is room for improvement in both ps.map and g.gui.psmap. Perhaps
Martin Landa has another undergrad student in need of a degree project. 
g.gui.psmap is great, but difficult to use because it does not support complex document.
So far my use of g.gui.psmap has been fairly simple and I like that I can
place objects more easily than by changing coordinates in the .psmap file
and recompiling.
Both ps.map and g.gui.psmap are very useful and for many purposes
(including mine) are more practical than using a different application such
as qgis.
Regards,
Rich
Le 30/10/2018 à 15:38, Rich Shepard a écrit :
On Tue, 30 Oct 2018, Frank David wrote:
I think some point are missing or lack of documentation. I think about
[read] command, display layer order, language support, unit of position in
the page (inch/cm), etc. Some improvement would be great, like line
thickness from column for example, accent support from v.label (??)...
Frank,
Yes, there is room for improvement in both ps.map and g.gui.psmap. Perhaps
Martin Landa has another undergrad student in need of a degree project.
g.gui.psmap is great, but difficult to use because it does not support complex document.
So far my use of g.gui.psmap has been fairly simple and I like that I can
place objects more easily than by changing coordinates in the .psmap file
and recompiling.
Both ps.map and g.gui.psmap are very useful and for many purposes
(including mine) are more practical than using a different application such
as qgis.
I agree, especially when numerous maps needed ! But some malfunctions prevent us from using this marvellous tool ! I hope it will be improved soon.
cheers,
Frank
Regards,
Rich
_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user
Hello Veronica,
Thanks for your reply. I have seen that note, but it's about the psmap file encoding standard. What is correct for me (ISO-8859-1), and [comments] text with accent are well displaying. My problem comes from data coming from database thru v.label or units as kilometer which comes from grass translation. please see attached screen-shot.
V.label display well accent in the grass display. but psmap do not display the same. The only way i see is to remove accent...
Cheers,
Frank
Le 30/10/2018 à 12:03, Veronica Andreo a écrit :
Hi Frank,
There's a note on that in the last paragraph under Notes section in the manual page [1]
Vero
[1] https://grass.osgeo.org/grass74/manuals/ps.map.html
El mar., 30 oct. 2018 7:33, Frank David <frank.david@geophom.fr <mailto:frank.david@geophom.fr>> escribió:
Hello all,
I'm using ps.map and I notice that accent are not well supported in 3
cases :
- map scale units, for example "kilomètre" is displayed
"kilomÄ"tre". I
dont'see how to solve that
- for a selecting field in vector map, like [where myfield =
"classé"]
(does not work) while [where myfield = "classe"] (works if I
change my
"é" with "e" in the attribute data). I can solve that by adding an
other
field in my table without accent.
- labels : labels created with v.label seems to cannot support
accent.
Is there any way to solve this ?
my ps.map file are encoded in ISO-8859-1 and other text works well
with
accent. I saw that an environment variable exist :
GRASS_DB_ENCODING but
I don't know how to see it and if I change if it would damage my data
table ...
Is anybody can advice me ?
I'm using Grass 7.4.1 on debian9
Thank you for your help,
Frank
_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org <mailto:grass-user@lists.osgeo.org>
https://lists.osgeo.org/mailman/listinfo/grass-user
(attachments)
CompressedFiles (1).zip (132 KB)