Earlier today I entered a ps.map bug in trac; I don't know how to find that
and add more information so I ask your indulgence for my proving that
additional information here.
Running ps.map on a *.psmap file produces a *.ps file with no errors.
However, displaying the file (which is correctly done) is accompanied by
these warnings, for which an example is shown:
$ gv white-sturgeon.ps
Warning: Missing charsets in String to FontSet conversion
Warning: Cannot convert string
"-efont-biwidth-medium-r-normal--16-*-*-*-*-*-iso10646-1,-gnu-unifont-medium-r-normal--16-*-*-*-*-*-iso10646-1,-adobe-helvetica-medium-r-normal--14-*-*-*-*-*-*-*,-jis-fixed-medium-r-*--16-*-*-*-*-*-jisx0208.1983-0,-*-*-medium-r-*--16-*-*-*-*-*-*-*,*"
to type FontSet
Warning: Missing charsets in String to FontSet conversion
Warning: Unable to load any usable fontset
Warning: Missing charsets in String to FontSet conversion
Warning: Unable to load any usable fontset
I've not seen these warnings when viewing other postscript files so I'm
assuming they're related to the font issues with vlegend that prevents the
postscript file from displaying.
Regards,
Rich
_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user
