Opened 8 years ago

Last modified 5 years ago

#3090 new defect

d.font does not change default font in monitors

Reported by: veroandreo Owned by: grass-dev@…
Priority: normal Milestone: 7.8.3
Component: Display Version: unspecified
Keywords: d.font Cc:
CPU: x86-64 Platform: Linux

Description

d.font -l and d.fontlist give 439 possibilities for fonts. However,

d.font font="whatever_font_from_the_439_items_list" 

does not change font setting in monitors, nor raise any error/warning. The only error appears when trying to set, for example, font=romanp which is indeed listed as option in d.font manual page (https://grass.osgeo.org/grass73/manuals/d.font.html).

Whatever font I choose, monitors keep using default roman, which IMHO looks awful and makes that the output of d.text or d.vect.thematic, for example, look terrible, too.

The only way I found to effectively change font for d.mon was with: 

export GRASS_FONT="sans"

I use fedora 23, grass trunk r68780.

Change History (13)

comment:1 by annakrat, 8 years ago

d.font calls D_font but that affects only the font in that process.

in reply to:  1 comment:2 by veroandreo, 8 years ago

Replying to annakrat:

d.font calls D_font but that affects only the font in that process.

If by process you mean a particular monitor, that's the case I'm reporting. Here, what I do:

d.mon wx0
d.font font="sans"
d.text "Hello GRASS GIS"

No sans font, but the default roman. However, please try saving the wx0 monitor with "Save Display to file", something strange happens... The "Hello GRASS" part disappears and only "GIS" word remain and with a different font.

comment:3 by neteler, 8 years ago

Probably caused by reason which leads to #3137

comment:4 by neteler, 8 years ago

Milestone: 7.2.07.2.1

Ticket retargeted after milestone closed

comment:5 by martinl, 8 years ago

Milestone: 7.2.17.2.2

comment:6 by neteler, 7 years ago

Milestone: 7.2.27.2.3

Ticket retargeted after milestone closed

comment:7 by martinl, 7 years ago

Milestone: 7.2.3

Ticket retargeted after milestone closed

comment:8 by martinl, 7 years ago

Milestone: 7.2.4

comment:9 by veroandreo, 6 years ago

Milestone: 7.2.47.8.0

I still get the same behavior in freshly compiled trunk

comment:10 by neteler, 5 years ago

Milestone: 7.8.07.8.1

Ticket retargeted after milestone closed

comment:11 by neteler, 5 years ago

Milestone: 7.8.17.8.2

Ticket retargeted after milestone closed

comment:12 by neteler, 5 years ago

Milestone: 7.8.2

Ticket retargeted after milestone closed

comment:13 by neteler, 5 years ago

Milestone: 7.8.3
Note: See TracTickets for help on using tickets.