Re: bug in terminals affected by 'set size'

[Petr M. <mi...@ph...>]

> I should also point out that the existing PostScript and eps output
> offers a possible easy fix to at least part of this dilemma if you
> are willing to use an editor.  The following line appears near the
> very top of the output file:
> /gnulinewidth 5.000 def
>
> If you are planning to scale up your plot by a factor of 2 and
> don't want the line widths to became twice as thick, you can replace
> that with
> /gnulinewidth 2.500 def

I've just noticed there is also /userlinewidth, but it does not change 
anything? Isn't this a bug?

Another strange thing: I've put two plots (two pages) into postscript file. 
There is
 	/gnulinewidth 5.000 def
in the header.

Now, I wanted to increase the linewidth 5 times on the 2nd page by this 
change:

grestore
end
showpage
%%Page: 2 2
gnudict begin
gsave
/gnulinewidth 25.000 def
50 50 translate
0.100 0.100 scale

However, it changed also the line width on the first page! Why?! ... or is 
it a bug in ghostscript? When it draws it 1st time, then it is ok, but when 
you go back from the 2nd to the 1st page (gv, gsview), the linewidth gets 
wrong. That's probably the value of the variable was overwritten in the 
dictionary?

Question: how to organize different linewidths on different pages, or rather 
in different subplots?

> We could, I think, do exactly the same with font sizes by introducing
> a global multiplier in the header
> /gnufontsize 1.000 def

This would be useful.

---
PM