[GRASS-user] Character encoding problem

[Miha Staut]

The same holds true for hardcopy output command ps.map as far as I know. Correct me if I am wrong. Miha



--- On Wed, 21/1/09, Jana Krajcovicova <jkrajc at gmail.com> wrote:

> From: Jana Krajcovicova <jkrajc at gmail.com>
> Subject: Re: [GRASS-user] Character encoding problem
> To: grass-user at lists.osgeo.org
> Date: Wednesday, 21 January, 2009, 11:15 AM
> CORRECTION:
> It is still desirable to change the character encoding
> directly in the .dbf
> file after import.
> Reason is that setting truetype and character encoding 
> using
> d.font.freetype only affects display commands, but reading
> database (e.g.,
> using db.select) is still scrambled.
> 
> Maybe there is an environmental variable in GRASS which can
> be used to
> change the default UTF8 encoding? But I would say that it
> is better to use
> OpenOffice to change .dbf file encoding in single cases.
> 
> Jana
> 
> On Wed, Jan 21, 2009 at 9:22 AM, Jana Krajcovicova
> <jkrajc at gmail.com> wrote:
> 
> >
> >
> >
> > That's correct Glynn, I've just tested that.
> The trick is as simple as to
> > use *Truetype* font and set charset to the encoding
> used in the input
> > vector map (Apparently, my GRASS was not built to use
> iconv() :-)
> >
> > Anyway, GRASS is so nice, thanks to all of you :-)
> >
> > Jana
> >
> >
> >
> >>
> >> I can't comment on GDAL/OGR issues, but the
> display library will
> >> accept data in any encoding recognised by iconv[1]
> when using FreeType
> >> fonts. You just need to specify the encoding via
> the charset= option.
> >>
> >> [1] Provided that GRASS was built to use iconv();
> this is
> >> autodetected. Otherwise, text is treated as
> ISO-8859-1.
> >>
> >> --
> >> Glynn Clements <glynn at gclements.plus.com>