matplotlib

Playing with this a little bit more, times and pslatex seem to be the
only settings for font.latex.package  that make any difference.  I
still don't get the pretty san serif font I get on the screen, but at
least the legend boxes are right.  Does it make sense that the on
screen font is different?  I thought that was coming from dvipng and
would be generated by latex.  What is the on screen font and how do I
get it into my eps files?

Thanks,

Ryan

On 1/28/06, Ryan Krauss <ryanlists@...> wrote:
> I am having a problem with the fonts with the usetex option.  My plots
> look beautiful on the screen and the labels are in a san-serif font
> that I would guess is Helvetica.  My rc files has this setting in it:
> font.latex.package  : type1cm
>
> But when I save these plots and include them in a LaTeX file (or look
> at them with a posscript viewer), the font seems to have switched to
> times and the legends don't fit in the legend boxes any more.
>
> What am I doing wrong?
>
> Ryan
>

On Saturday 28 January 2006 20:15, Ryan Krauss wrote:
> Playing with this a little bit more, times and pslatex seem to be the
> only settings for font.latex.package  that make any difference.  I
> still don't get the pretty san serif font I get on the screen, but at
> least the legend boxes are right.  Does it make sense that the on
> screen font is different?  I thought that was coming from dvipng and
> would be generated by latex.  What is the on screen font and how do I
> get it into my eps files?

Shot in the dark: Try clearing you tex.cache.

If you set pslatex, the adobe postscript fonts will be used instead of the 
computer modern fonts. So if you do {\sffamily Print this in sans-serif} with 
pslatex, you get helvetica fonts. You can do the same with computer modern.

Times is a subset of pslatex, the computer modern fonts end up being used for 
math.

clearing the tex.cache doesn't seem to make a difference.  times is
still the only package thae doesn't overflow the legend box and the on
screen is always san serif and the eps is always serif.

On 1/28/06, Darren Dale <dd55@...> wrote:
> On Saturday 28 January 2006 20:15, Ryan Krauss wrote:
> > Playing with this a little bit more, times and pslatex seem to be the
> > only settings for font.latex.package  that make any difference.  I
> > still don't get the pretty san serif font I get on the screen, but at
> > least the legend boxes are right.  Does it make sense that the on
> > screen font is different?  I thought that was coming from dvipng and
> > would be generated by latex.  What is the on screen font and how do I
> > get it into my eps files?
>
> Shot in the dark: Try clearing you tex.cache.
>
> If you set pslatex, the adobe postscript fonts will be used instead of th=
e
> computer modern fonts. So if you do {\sffamily Print this in sans-serif} =
with
> pslatex, you get helvetica fonts. You can do the same with computer moder=
n.
>
> Times is a subset of pslatex, the computer modern fonts end up being used=
 for
> math.
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi=
les
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D230486&dat=
=3D121642
> _______________________________________________
> Matplotlib-users mailing list
> Matplotlib-users@...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

On Saturday 28 January 2006 10:04 pm, Ryan Krauss wrote:
> clearing the tex.cache doesn't seem to make a difference.  times is
> still the only package thae doesn't overflow the legend box and the on
> screen is always san serif and the eps is always serif.

I think this is now fixed in cvs.

I don't know what I am doing wrong, but I just checked out everything
from cvs and when I go into the directory and do a sudo python
setup.py install and then import matplotlib, it says my version is
0.86.2 and I still have the same problems as before.  It seems like
cvs versions always had a cvs at the end of them before.


On 1/28/06, Darren Dale <dd55@...> wrote:
> On Saturday 28 January 2006 10:04 pm, Ryan Krauss wrote:
> > clearing the tex.cache doesn't seem to make a difference.  times is
> > still the only package thae doesn't overflow the legend box and the on
> > screen is always san serif and the eps is always serif.
>
> I think this is now fixed in cvs.
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi=
les
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D230486&dat=
=3D121642
> _______________________________________________
> Matplotlib-users mailing list
> Matplotlib-users@...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

Darren Dale wrote:
> On Saturday 28 January 2006 10:04 pm, Ryan Krauss wrote:
>> clearing the tex.cache doesn't seem to make a difference.  times is
>> still the only package thae doesn't overflow the legend box and the on
>> screen is always san serif and the eps is always serif.
> 
> I think this is now fixed in cvs.

I made similar observations here. With matplotlib from cvs, an empty tex-cache,
without own matplotlibrc and setting
rcParams['text.usetex'] = True
I get sans-serif fonts on screen (I guess it is the WXAgg backend) and serif
fonts in the eps output and the legend box is mostly too small.

Regards, Christian

On Saturday 28 January 2006 11:56 pm, Ryan Krauss wrote:
> I don't know what I am doing wrong, but I just checked out everything
> from cvs and when I go into the directory and do a sudo python
> setup.py install and then import matplotlib, it says my version is
> 0.86.2 and I still have the same problems as before.  It seems like
> cvs versions always had a cvs at the end of them before.

My version also says 0.86.2. Maybe the problem is that non-developer checkout 
is lagging. Try checking out again, your backend_ps is the only file that 
required changing. If it still does not reflect the changes, just inserted 
the following lines into the RendererPS.draw_tex method at line 641:

        if rcParams['text.tex.engine'] == 'latex':
            fontcmd = {'sans-serif' : r'{\sffamily %s}',
                   'monospace'  : r'{\ttfamily %s}'}.get(
                    rcParams['font.family'], r'{\rmfamily %s}')
            s = fontcmd % s

These commands produced the attached eps file (fontfamily is sans-serif in 
matplotlibrc):

In [1]: plot([2,3,4,5])
Out[1]: [<matplotlib.lines.Line2D instance at 0xb5ba71cc>]

In [2]: plot([1,2,3,4])
Out[2]: [<matplotlib.lines.Line2D instance at 0xb5bb5b0c>]

In [3]: legend(('IIIIIIIIIIIIII','IIIIIIIIIIIIII'), 2) # Those are capital i's
Out[3]: <matplotlib.legend.Legend instance at 0xb5bb982c>

In [4]: savefig('sans-serif.eps')

That seems to have done it.  And CVS is caught up for non-developers.=20
Thanks for all your hard work Darren.  I can now have my choice of
serif or san-serif fonts and the eps files match the screen.  You can
still have problems if you change your rc file without clearing you
tex.cache.  I don't know if a note about that in the rc file would cut
down on problems or not.

Thanks again,

Ryan

On 1/29/06, Darren Dale <dd55@...> wrote:
> On Saturday 28 January 2006 11:56 pm, Ryan Krauss wrote:
> > I don't know what I am doing wrong, but I just checked out everything
> > from cvs and when I go into the directory and do a sudo python
> > setup.py install and then import matplotlib, it says my version is
> > 0.86.2 and I still have the same problems as before.  It seems like
> > cvs versions always had a cvs at the end of them before.
>
> My version also says 0.86.2. Maybe the problem is that non-developer chec=
kout
> is lagging. Try checking out again, your backend_ps is the only file that
> required changing. If it still does not reflect the changes, just inserte=
d
> the following lines into the RendererPS.draw_tex method at line 641:
>
>         if rcParams['text.tex.engine'] =3D=3D 'latex':
>             fontcmd =3D {'sans-serif' : r'{\sffamily %s}',
>                    'monospace'  : r'{\ttfamily %s}'}.get(
>                     rcParams['font.family'], r'{\rmfamily %s}')
>             s =3D fontcmd % s
>
> These commands produced the attached eps file (fontfamily is sans-serif i=
n
> matplotlibrc):
>
> In [1]: plot([2,3,4,5])
> Out[1]: [<matplotlib.lines.Line2D instance at 0xb5ba71cc>]
>
> In [2]: plot([1,2,3,4])
> Out[2]: [<matplotlib.lines.Line2D instance at 0xb5bb5b0c>]
>
> In [3]: legend(('IIIIIIIIIIIIII','IIIIIIIIIIIIII'), 2) # Those are capita=
l i's
> Out[3]: <matplotlib.legend.Legend instance at 0xb5bb982c>
>
> In [4]: savefig('sans-serif.eps')
>
>
>
>
>

I know Fernando had posted questions about changing the font package
and John said something about adding the font family to the cache
somehow.  I was talking specifically of having problems when switching
from serif to sans-serif and needing to clear the cache when you do.

On 1/29/06, Ryan Krauss <ryanlists@...> wrote:
> That seems to have done it.  And CVS is caught up for non-developers.
> Thanks for all your hard work Darren.  I can now have my choice of
> serif or san-serif fonts and the eps files match the screen.  You can
> still have problems if you change your rc file without clearing you
> tex.cache.  I don't know if a note about that in the rc file would cut
> down on problems or not.
>
> Thanks again,
>
> Ryan
>
> On 1/29/06, Darren Dale <dd55@...> wrote:
> > On Saturday 28 January 2006 11:56 pm, Ryan Krauss wrote:
> > > I don't know what I am doing wrong, but I just checked out everything
> > > from cvs and when I go into the directory and do a sudo python
> > > setup.py install and then import matplotlib, it says my version is
> > > 0.86.2 and I still have the same problems as before.  It seems like
> > > cvs versions always had a cvs at the end of them before.
> >
> > My version also says 0.86.2. Maybe the problem is that non-developer ch=
eckout
> > is lagging. Try checking out again, your backend_ps is the only file th=
at
> > required changing. If it still does not reflect the changes, just inser=
ted
> > the following lines into the RendererPS.draw_tex method at line 641:
> >
> >         if rcParams['text.tex.engine'] =3D=3D 'latex':
> >             fontcmd =3D {'sans-serif' : r'{\sffamily %s}',
> >                    'monospace'  : r'{\ttfamily %s}'}.get(
> >                     rcParams['font.family'], r'{\rmfamily %s}')
> >             s =3D fontcmd % s
> >
> > These commands produced the attached eps file (fontfamily is sans-serif=
 in
> > matplotlibrc):
> >
> > In [1]: plot([2,3,4,5])
> > Out[1]: [<matplotlib.lines.Line2D instance at 0xb5ba71cc>]
> >
> > In [2]: plot([1,2,3,4])
> > Out[2]: [<matplotlib.lines.Line2D instance at 0xb5bb5b0c>]
> >
> > In [3]: legend(('IIIIIIIIIIIIII','IIIIIIIIIIIIII'), 2) # Those are capi=
tal i's
> > Out[3]: <matplotlib.legend.Legend instance at 0xb5bb982c>
> >
> > In [4]: savefig('sans-serif.eps')
> >
> >
> >
> >
> >
>

>>>>> "Ryan" == Ryan Krauss <ryanlists@...> writes:

    Ryan> That seems to have done it.  And CVS is caught up for
    Ryan> non-developers.  Thanks for all your hard work Darren.  I
    Ryan> can now have my choice of serif or san-serif fonts and the
    Ryan> eps files match the screen.  You can still have problems if
    Ryan> you change your rc file without clearing you tex.cache.  I
    Ryan> don't know if a note about that in the rc file would cut
    Ryan> down on problems or not.

What are you changing that is causing the problem?  I have tried to
include the font family information in the cache string.  Please give
us an exact sequence of steps that is causing the problem, starting
with a clean CVS build an empty cache.

Thanks,
JDH

On Sunday 29 January 2006 11:53 am, you wrote:
> That seems to have done it.  And CVS is caught up for non-developers.
> Thanks for all your hard work Darren.  

My pleasure.

> I can now have my choice of 
> serif or san-serif fonts and the eps files match the screen.  You can
> still have problems if you change your rc file without clearing you
> tex.cache.  I don't know if a note about that in the rc file would cut
> down on problems or not.

Thanks for pointing this out. It is fixed in CVS, Line 79 in texmanager has 
been changed to read: 

            s+='latex font: %s %s'% (rcParams['font.latex.package'], 
                rcParams['font.family'])

So it should not be necessary to clear your tex.cache.

On Sunday 29 January 2006 11:57 am, you wrote:
> >>>>> "Ryan" == Ryan Krauss <ryanlists@...> writes:
>
>     Ryan> That seems to have done it.  And CVS is caught up for
>     Ryan> non-developers.  Thanks for all your hard work Darren.  I
>     Ryan> can now have my choice of serif or san-serif fonts and the
>     Ryan> eps files match the screen.  You can still have problems if
>     Ryan> you change your rc file without clearing you tex.cache.  I
>     Ryan> don't know if a note about that in the rc file would cut
>     Ryan> down on problems or not.
>
> What are you changing that is causing the problem?  I have tried to
> include the font family information in the cache string.  Please give
> us an exact sequence of steps that is causing the problem, starting
> with a clean CVS build an empty cache.

The cache string included the latex font package, but this is not necessarily 
enough. pslatex, for example, will load the adobe fonts, but the output still 
depends on whether font.family is set to serif (times) or sans-serif 
(helvetica). I just added the font.family info to the cache string, that 
seems to take care of it.

Darren

>>>>> "Darren" == Darren Dale <dd55@...> writes:

    Darren>             s+='latex font: %s %s'%
    Darren> (rcParams['font.latex.package'], rcParams['font.family'])

    Darren> So it should not be necessary to clear your tex.cache.

Oops, I also added the font.family to the Agg key

Checking in lib/matplotlib/backends/backend_agg.py;
/cvsroot/matplotlib/matplotlib/lib/matplotlib/backends/backend_agg.py,v
<--  backend_agg.py
new revision: 1.42; previous revision: 1.41


It would be useful to centralize the cache key generation, since it is
fragile to have texmanager and backend_agg doing this
independently....

JDH

Darren Dale wrote:

> The cache string included the latex font package, but this is not necessarily 
> enough. pslatex, for example, will load the adobe fonts, but the output still 
> depends on whether font.family is set to serif (times) or sans-serif 
> (helvetica). I just added the font.family info to the cache string, that 
> seems to take care of it.

If I can make a suggestion: in

http://new.scipy.org/Wiki/Cookbook/Matplotlib/UsingTex

it might be worth clarifying exactly how font.family interacts with the 
various latex package options.  I think in particular the combination of 
serif/sans vs. the font.latex.package choice (helvet/typec1m/...) is a little 
bit confusing.

Cheers,

f

On Sunday 29 January 2006 3:58 pm, you wrote:
> Darren Dale wrote:
> > The cache string included the latex font package, but this is not
> > necessarily enough. pslatex, for example, will load the adobe fonts, but
> > the output still depends on whether font.family is set to serif (times)
> > or sans-serif (helvetica). I just added the font.family info to the cache
> > string, that seems to take care of it.
>
> If I can make a suggestion: in
>
> http://new.scipy.org/Wiki/Cookbook/Matplotlib/UsingTex
>
> it might be worth clarifying exactly how font.family interacts with the
> various latex package options.  I think in particular the combination of
> serif/sans vs. the font.latex.package choice (helvet/typec1m/...) is a
> little bit confusing.

Earlier this morning I changed the wiki page to explain this detail. Is it 
still unclear?

Darren Dale wrote:

> Earlier this morning I changed the wiki page to explain this detail. Is it 
> still unclear?

mmh.  Perhaps a little summary table of the kind

font.family   ||  font.latex.package  || resulting font
-------------------------------------------------------
serif         ||  various options

serif

sans

sans

etc.


Might help the dense amongst us make sense of the various possible results 
without having to think, something at least I am not very good at.

Cheers,

f

I made some improvements to the usetex option over the last few days in order 
to make font selection fit seemlessly with the rest of Matplotlib. The usetex 
option will now respect the serif, sans-serif, monospace, and cursive rc 
settings. Usetex looks until it finds a latex-compatible font, or defaults to 
computer modern. Proper font support with plainTeX is more difficult, and 
everyone seems to use the latex backend anyway, so I am dropping support of 
the tex engine. With these changes, the font.latex.package and the 
text.tex.engine rc settings are no longer needed, and should be removed from 
ones personal matplotlibrc file.

Here are the currently supported latex fonts:

- serif: Times, Palatino, Bookman, New Century Schoolbook, Charter, Computer 
Modern Roman (Times and Palatino have their own math fonts, the others 
default to computer modern math fonts)

- sans-serif: Helvetica, Avant Garde, Computer Modern Sans Serif (I added 
Avant Garde to the matplotlibrc.template)

- monospace: Courier, Computer Modern Typewriter

- cursive: Zapf Chancery

The font.family setting is respected and should be used to switch from one 
family to another. Cursive fonts are supported with latex, but fantasy fonts 
are not (raises a warning and defaults to serif). If you use the usetex 
option, please kick the tires and let me know how it goes.

Darren