You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
(12) |
Sep
(12) |
Oct
(56) |
Nov
(65) |
Dec
(37) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(59) |
Feb
(78) |
Mar
(153) |
Apr
(205) |
May
(184) |
Jun
(123) |
Jul
(171) |
Aug
(156) |
Sep
(190) |
Oct
(120) |
Nov
(154) |
Dec
(223) |
| 2005 |
Jan
(184) |
Feb
(267) |
Mar
(214) |
Apr
(286) |
May
(320) |
Jun
(299) |
Jul
(348) |
Aug
(283) |
Sep
(355) |
Oct
(293) |
Nov
(232) |
Dec
(203) |
| 2006 |
Jan
(352) |
Feb
(358) |
Mar
(403) |
Apr
(313) |
May
(165) |
Jun
(281) |
Jul
(316) |
Aug
(228) |
Sep
(279) |
Oct
(243) |
Nov
(315) |
Dec
(345) |
| 2007 |
Jan
(260) |
Feb
(323) |
Mar
(340) |
Apr
(319) |
May
(290) |
Jun
(296) |
Jul
(221) |
Aug
(292) |
Sep
(242) |
Oct
(248) |
Nov
(242) |
Dec
(332) |
| 2008 |
Jan
(312) |
Feb
(359) |
Mar
(454) |
Apr
(287) |
May
(340) |
Jun
(450) |
Jul
(403) |
Aug
(324) |
Sep
(349) |
Oct
(385) |
Nov
(363) |
Dec
(437) |
| 2009 |
Jan
(500) |
Feb
(301) |
Mar
(409) |
Apr
(486) |
May
(545) |
Jun
(391) |
Jul
(518) |
Aug
(497) |
Sep
(492) |
Oct
(429) |
Nov
(357) |
Dec
(310) |
| 2010 |
Jan
(371) |
Feb
(657) |
Mar
(519) |
Apr
(432) |
May
(312) |
Jun
(416) |
Jul
(477) |
Aug
(386) |
Sep
(419) |
Oct
(435) |
Nov
(320) |
Dec
(202) |
| 2011 |
Jan
(321) |
Feb
(413) |
Mar
(299) |
Apr
(215) |
May
(284) |
Jun
(203) |
Jul
(207) |
Aug
(314) |
Sep
(321) |
Oct
(259) |
Nov
(347) |
Dec
(209) |
| 2012 |
Jan
(322) |
Feb
(414) |
Mar
(377) |
Apr
(179) |
May
(173) |
Jun
(234) |
Jul
(295) |
Aug
(239) |
Sep
(276) |
Oct
(355) |
Nov
(144) |
Dec
(108) |
| 2013 |
Jan
(170) |
Feb
(89) |
Mar
(204) |
Apr
(133) |
May
(142) |
Jun
(89) |
Jul
(160) |
Aug
(180) |
Sep
(69) |
Oct
(136) |
Nov
(83) |
Dec
(32) |
| 2014 |
Jan
(71) |
Feb
(90) |
Mar
(161) |
Apr
(117) |
May
(78) |
Jun
(94) |
Jul
(60) |
Aug
(83) |
Sep
(102) |
Oct
(132) |
Nov
(154) |
Dec
(96) |
| 2015 |
Jan
(45) |
Feb
(138) |
Mar
(176) |
Apr
(132) |
May
(119) |
Jun
(124) |
Jul
(77) |
Aug
(31) |
Sep
(34) |
Oct
(22) |
Nov
(23) |
Dec
(9) |
| 2016 |
Jan
(26) |
Feb
(17) |
Mar
(10) |
Apr
(8) |
May
(4) |
Jun
(8) |
Jul
(6) |
Aug
(5) |
Sep
(9) |
Oct
(4) |
Nov
|
Dec
|
| 2017 |
Jan
(5) |
Feb
(7) |
Mar
(1) |
Apr
(5) |
May
|
Jun
(3) |
Jul
(6) |
Aug
(1) |
Sep
|
Oct
(2) |
Nov
(1) |
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2025 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
1
(2) |
2
(8) |
3
(8) |
4
(3) |
5
(15) |
6
(11) |
7
(4) |
|
8
|
9
(3) |
10
(21) |
11
(5) |
12
(7) |
13
(10) |
14
(12) |
|
15
(3) |
16
(4) |
17
(16) |
18
(20) |
19
(11) |
20
(9) |
21
(1) |
|
22
|
23
(15) |
24
(11) |
25
(1) |
26
(9) |
27
(5) |
28
|
|
29
(1) |
30
|
31
(6) |
|
|
|
|
|
From: John H. <jd...@gm...> - 2007-07-10 23:46:12
|
On 7/10/07, Devin Halperin <dh...@ya...> wrote:
> I'm trying to figure out why this command is taking on average over 14
> seconds to render a drawing of a fairly simple plot. If anyone has ideas,
> I'd really appreciate some help.
> fig = figure(figsize=(12.5,3.75), dpi=80,facecolor = 'y', edgecolor='b')
///snip
> canvas = FigureCanvasAgg(fig)
You can't do this. You are combining pylab figure management (eg
figure) with explicit use of FigureCanvasAgg. Who the hell knows what
will happen.
If you want to use pylab, just create the figure as above and you can
access the cancas directly w/ fig.canvas and set your backend to Agg,
eg with
import matplotlib
matplotlib.use('Agg')
before importing pylab.
If you don't want to use pylab, follow the approach of
http://matplotlib.sf.net/examples/agg_oo.py
Note there we use matplotlib.figure.Figure to create the figure, not
pylab.figure.
This is probably your problem. If I were to guess, you are getting
caught up somewhere in some GUI nastiness inadvertently by using
pylab.figure and this is causing the slowdown.
JDH
|
|
From: Peter I. H. <pe...@gm...> - 2007-07-10 23:22:10
|
On 7/11/07, Eric Firing <ef...@ha...> wrote:
> Peter I. Hansen wrote:
> > Hello
> >
> > I have gridded data of the shape:
> >
> > x_1 y_1 z_1
> > x_1 y_2 z_2
> > . . .
> > x_1 y_N z_N
> >
> > x_2 y_1 z_(N+1)
> > x_2 y_2 z_(N+2)
> > . . .
> > x_2 y_N z_(2N)
> >
> > x_M y_1 z_(MN)
> > x_M y_2 z_(MN)
> > . . .
> > x_M y_N z_(MN)
> >
> > I've tried to follow the contour_demo script by making
>
>
> You don't need to make your own X, Y, so delete the following 3 lines.
> >
> > x = arange(M numbers)
> > y = arange(N numbers)
> > X,Y = meshgrid(x,y)
> >
> > M = load('zdata.dat')
>
> Now you have X, Y, and Z, each as a column in your file, so you need to
> split them apart and reshape them. Let's assume M, N are the number of
> X and Y values in your grid; to avoid name confusion, change the load to
>
> XYZ = load('zdata.dat')
>
> X = XYZ[:,0]
> X.shape = (M,N)
> Y = XYZ[:,1]
> Y.shape = (M,N)
> Z = XYZ[:,2]
> Z.shape = (M,N)
>
> CS = contour(X.transpose(), Y.transpose(), Z.transpose())
>
> The reason for all the transposing is that pcolor and contour display
> images with column number increasing with X, and row number increasing
> with Y. Since you have M X-values and N Y-values, everything has to end
> up N by M, not the reverse.
Perfect. That was just what i needed to know. Thanks!
|
|
From: Eric F. <ef...@ha...> - 2007-07-10 23:01:21
|
Peter I. Hansen wrote:
> Hello
>
> I have gridded data of the shape:
>
> x_1 y_1 z_1
> x_1 y_2 z_2
> . . .
> x_1 y_N z_N
>
> x_2 y_1 z_(N+1)
> x_2 y_2 z_(N+2)
> . . .
> x_2 y_N z_(2N)
>
> x_M y_1 z_(MN)
> x_M y_2 z_(MN)
> . . .
> x_M y_N z_(MN)
>
> I've tried to follow the contour_demo script by making
You don't need to make your own X, Y, so delete the following 3 lines.
>
> x = arange(M numbers)
> y = arange(N numbers)
> X,Y = meshgrid(x,y)
>
> M = load('zdata.dat')
Now you have X, Y, and Z, each as a column in your file, so you need to
split them apart and reshape them. Let's assume M, N are the number of
X and Y values in your grid; to avoid name confusion, change the load to
XYZ = load('zdata.dat')
X = XYZ[:,0]
X.shape = (M,N)
Y = XYZ[:,1]
Y.shape = (M,N)
Z = XYZ[:,2]
Z.shape = (M,N)
CS = contour(X.transpose(), Y.transpose(), Z.transpose())
The reason for all the transposing is that pcolor and contour display
images with column number increasing with X, and row number increasing
with Y. Since you have M X-values and N Y-values, everything has to end
up N by M, not the reverse.
Eric
>
> Z = reshape(M, (M,N))
>
> figure()
> CS = contour(X,Y,Z)
>
> But I get errors that x and y are not 1D or 2D... Can someone help me
> to do this right?
> thanks, Peter
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
|
|
From: Devin H. <dh...@ya...> - 2007-07-10 21:16:37
|
I'm trying to figure out why this command is taking on average over 14 seconds to render a drawing of a fairly simple plot. If anyone has ideas, I'd really appreciate some help.
fig = figure(figsize=(12.5,3.75), dpi=80,facecolor = 'y', edgecolor='b')
start_date = "20050710"
start_date += "T000000"
my_dates = list(rrule(DAILY, dtstart=parse(start_date), until=datetime.today()))
formatted_dates = [date2num(parse(start_date))]
for date in my_dates :
formatted_dates.append(date2num(date))
formatted_dates.append(date2num(datetime.today()))
y_ticks = []
for x in xrange(0,11):
my_string = str(x*10)+' Percent'
y_ticks.append(my_string)
yticks(arange(0.0, 1.1, .1), y_ticks)
y_data = rand(len(formatted_dates))
ax = fig.add_subplot(111)
ax.plot_date(formatted_dates, y_data, '-')
labels = ax.get_xticklabels()
setp(labels, rotation=20, fontsize=8)
ax.autoscale_view()
#xlabel('')
#ylabel('')
title('Could put start date and end date here')
grid(True)
canvas = FigureCanvasAgg(fig)
# 90% Run-time
############################################
############################################
canvas.draw()
############################################
############################################
imageSize = canvas.get_width_height()
imageRgb = canvas.tostring_rgb()
pilImage = Image.fromstring("RGB", imageSize, imageRgb)
pilImage.show()
---------------------------------
Ready for the edge of your seat? Check out tonight's top picks on Yahoo! TV. |
|
From: Peter I. H. <pe...@gm...> - 2007-07-10 21:02:29
|
Hello
I have gridded data of the shape:
x_1 y_1 z_1
x_1 y_2 z_2
. . .
x_1 y_N z_N
x_2 y_1 z_(N+1)
x_2 y_2 z_(N+2)
. . .
x_2 y_N z_(2N)
x_M y_1 z_(MN)
x_M y_2 z_(MN)
. . .
x_M y_N z_(MN)
I've tried to follow the contour_demo script by making
x = arange(M numbers)
y = arange(N numbers)
X,Y = meshgrid(x,y)
M = load('zdata.dat')
Z = reshape(M, (M,N))
figure()
CS = contour(X,Y,Z)
But I get errors that x and y are not 1D or 2D... Can someone help me
to do this right?
thanks, Peter
|
|
From: Edin S. <edi...@gm...> - 2007-07-10 20:48:33
|
On 7/10/07, John Hunter <jd...@gm...> wrote: > Hey Edin, if you get a minute, could you contribute a patch against > the faq in htdocs/faq.html.template explaining how to install the > bakoma fonts for svg viewers? Is this sufficiently difficult that it > merits a FAQ? It sure is easy to forget :) Attached is the patch to the FAQ. I don't have the htdocs dir checked out. John, can you apply the patch? Any comments? Best, Edin |
|
From: Edin S. <edi...@gm...> - 2007-07-10 19:53:21
|
On 7/10/07, Kaushik Ghose <kg...@um...> wrote: > Hi Edin, > Good point. I tried just now on Firefox and got the same error. > For an image of what I mean see this > http://python-pieces.blogspot.com/2007/07/latex-and-svg-export.html > > > I'm attaching the svg output here in case someone wants to try it out: (...) This should be fixed in SVN (r3346 or r3353) --- Norbert Nemec recently fixed the mathtext support in the SVG backend. Best, Edin |
|
From: John H. <jd...@gm...> - 2007-07-10 19:35:42
|
On 7/10/07, Eric Firing <ef...@ha...> wrote: > My argument for fraction of font size is that this is the norm for > setting text; in a word processor, or in LaTeX (preferred, of course), Well, if that's how latex does it, that's how we should do it too.... Thanks for the offer to add this -- shouldn't be too hard. I don't mind also having an rc parameter for this, but probably a text property will suffice. JDH |
|
From: Eric F. <ef...@ha...> - 2007-07-10 19:24:20
|
John Hunter wrote: > On 7/10/07, Eric Firing <ef...@ha...> wrote: >> John Hunter wrote: > >> It looks to me like it is all in the text._get_layout() method, where a >> 2-pixel pad is specified in one place, and an additional 3-pixel pad in >> another; both seem to be used for vertical spacing, so it is 5 pixels. >> >> Certainly for line spacing, and probably in other places related to text >> positioning, I would think pads usually should be in fractions of the >> font size, not fixed numbers of pixels. Comments? > > My first thought is that it should be in points, but I'm open to > arguments that it should be a fraction of font size. It should > definitely not be in pixels -- wonder what fool wrote that :-) > > JDH John, My argument for fraction of font size is that this is the norm for setting text; in a word processor, or in LaTeX (preferred, of course), when you increase the font size, the physical spacing between lines (and between characters) increases proportionally. Shouldn't it work the same way in a plot? Eric |
|
From: John H. <jd...@gm...> - 2007-07-10 19:09:09
|
On 7/10/07, Eric Firing <ef...@ha...> wrote: > John Hunter wrote: > It looks to me like it is all in the text._get_layout() method, where a > 2-pixel pad is specified in one place, and an additional 3-pixel pad in > another; both seem to be used for vertical spacing, so it is 5 pixels. > > Certainly for line spacing, and probably in other places related to text > positioning, I would think pads usually should be in fractions of the > font size, not fixed numbers of pixels. Comments? My first thought is that it should be in points, but I'm open to arguments that it should be a fraction of font size. It should definitely not be in pixels -- wonder what fool wrote that :-) JDH |
|
From: Eric F. <ef...@ha...> - 2007-07-10 18:31:30
|
John Hunter wrote: > On 7/10/07, Jianfu Pan <Jia...@gs...> wrote: >> Hi, >> >> I use Text() call of Figure() object for writing text. Because my text is >> long, I use line breaker (\n) to write multiple lines with a single >> call. This works fine except the line spacing is really tight and I wish I >> could set a bigger line spacing. Does anyone know if this is >> possible? Thanks for your time. > > Currently not, the pad between the newline is hard coded, but we could > expose it as a parameter w/o too much work. It looks to me like it is all in the text._get_layout() method, where a 2-pixel pad is specified in one place, and an additional 3-pixel pad in another; both seem to be used for vertical spacing, so it is 5 pixels. Certainly for line spacing, and probably in other places related to text positioning, I would think pads usually should be in fractions of the font size, not fixed numbers of pixels. Comments? Unless someone else would like to do it, I can take care of this at least as far as putting an rcParam entry for inter-line spacing as a fraction of font height, and a corresponding kwarg in Text and TextWithDash. Eric |
|
From: James B. <bo...@ll...> - 2007-07-10 18:03:51
|
As a coincidence, just today I was trying to figure out how to increase the spacing between the lines in the title of my plot. I too, would like some means to control this. --Jim On Jul 10, 2007, at 10:48 AM, Jianfu Pan wrote: > John, > > Thanks for your prompt response. I think the option can be > useful. In my > case, the gap between the lines are really tight with "_" in the > first line > right on the top of characters in the second line. > > Regards, > Jianfu > > At 12:31 PM 7/10/2007, John Hunter wrote: >> On 7/10/07, Jianfu Pan <Jia...@gs...> wrote: >>> Hi, >>> >>> I use Text() call of Figure() object for writing text. Because >>> my text is >>> long, I use line breaker (\n) to write multiple lines with a single >>> call. This works fine except the line spacing is really tight >>> and I wish I >>> could set a bigger line spacing. Does anyone know if this is >>> possible? Thanks for your time. >> >> Currently not, the pad between the newline is hard coded, but we >> could >> expose it as a parameter w/o too much work. >> >> JDH >> >> --------------------------------------------------------------------- >> ---- >> This SF.net email is sponsored by DB2 Express >> Download DB2 Express C - the FREE version of DB2 express and take >> control of your XML. No limits. Just data. Click to get it now. >> http://sourceforge.net/powerbar/db2/ >> _______________________________________________ >> Matplotlib-users mailing list >> Mat...@li... >> https://lists.sourceforge.net/lists/listinfo/matplotlib-users > > > ---------------------------------------------------------------------- > --- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Matplotlib-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users |
|
From: Jianfu P. <Jia...@gs...> - 2007-07-10 17:48:42
|
John, Thanks for your prompt response. I think the option can be useful. In my case, the gap between the lines are really tight with "_" in the first line right on the top of characters in the second line. Regards, Jianfu At 12:31 PM 7/10/2007, John Hunter wrote: >On 7/10/07, Jianfu Pan <Jia...@gs...> wrote: > > Hi, > > > > I use Text() call of Figure() object for writing text. Because my text is > > long, I use line breaker (\n) to write multiple lines with a single > > call. This works fine except the line spacing is really tight and I wish I > > could set a bigger line spacing. Does anyone know if this is > > possible? Thanks for your time. > >Currently not, the pad between the newline is hard coded, but we could >expose it as a parameter w/o too much work. > >JDH > >------------------------------------------------------------------------- >This SF.net email is sponsored by DB2 Express >Download DB2 Express C - the FREE version of DB2 express and take >control of your XML. No limits. Just data. Click to get it now. >http://sourceforge.net/powerbar/db2/ >_______________________________________________ >Matplotlib-users mailing list >Mat...@li... >https://lists.sourceforge.net/lists/listinfo/matplotlib-users |
|
From: Kaushik G. <kg...@um...> - 2007-07-10 17:34:36
|
Hi Edin, > Hmm. I'm not sure whether this is a problem with matplotlib or > inkscape. I had some weird problems with inkscape on Ubuntu Feisty > recently, like: when I open the file from Nautilus (right click->open > with Inkscape) it is completely turned around; when I open Inkscape > (blank file), and open the file from within inkscape everything is > displayed correctly. > > Have you opened the file in other viewers? > Good point. I tried just now on Firefox and got the same error. For an image of what I mean see this http://python-pieces.blogspot.com/2007/07/latex-and-svg-export.html I'm attaching the svg output here in case someone wants to try it out: <?xml version="1.0" standalone="no"?> <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd"> <!-- Created with matplotlib (http://matplotlib.sourceforge.net/) --> <svg width="586" height="442" viewBox="0 0 586 442" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" version="1.1" id="svg1"> <g id="figure1"> <polygon style="fill: #ffffff; stroke: #ffffff; stroke-width: 1.000000; stroke-linejoin: miter; stroke-linecap: square; opacity: 1.000000" points = "0.000000,442.800000 0.000000,0.000000 586.800000,0.000000 586.800000,442.800000"/> <g id="axes1"> <g id="mathtext1"> <text style="font-size: 12.000000; font-family: cmr10; fill: #000000;" x="88.182031" y="358.020000" >1</text> <text style="font-size: 12.000000; font-family: cmr10; fill: #000000;" x="78.859766" y="358.020000" >=</text> <text style="font-size: 12.000000; font-family: cmmi10; fill: #000000;" x="71.658594" y="358.020000" >n</text> <text style="font-size: 8.400000; font-family: cmmi10; fill: #000000;" x="127.162500" y="370.020000" >i</text> <text style="font-size: 12.000000; font-family: cmmi10; fill: #000000;" x="139.373148" y="373.020000" >±</text> <text style="font-size: 12.000000; font-family: cmr10; fill: #000000;" x="130.050882" y="373.020000" >+</text> <text style="font-size: 12.000000; font-family: cmmi10; fill: #000000;" x="122.115625" y="373.020000" >q</text> <text style="font-size: 12.000000; font-family: cmsy10; fill: #000000;" x="116.115625" y="373.020000" >¤</text> <text style="font-size: 8.400000; font-family: cmr10; fill: #000000;" x="111.920313" y="379.020000" >5</text> <text style="font-size: 12.000000; font-family: cmr10; fill: #000000;" x="105.998438" y="373.020000" >9</text> <text style="font-size: 12.000000; font-family: cmr10; fill: #000000;" x="99.998438" y="373.020000" >9</text> <text style="font-size: 12.000000; font-family: cmr10; fill: #000000;" x="90.676172" y="373.020000" >=</text> <text style="font-size: 12.000000; font-family: cmr10; fill: #000000;" x="85.935938" y="388.020000" >0</text> <text style="font-size: 12.000000; font-family: cmr10; fill: #000000;" x="79.935938" y="388.020000" >0</text> <text style="font-size: 12.000000; font-family: cmr10; fill: #000000;" x="73.935938" y="388.020000" >1</text> <text style="font-size: 12.000000; font-family: cmex10; fill: #000000;" x="73.350000" y="386.020000" >X</text> </g> </g> </g> </svg> |
|
From: John H. <jd...@gm...> - 2007-07-10 17:32:02
|
On 7/10/07, Jianfu Pan <Jia...@gs...> wrote: > Hi, > > I use Text() call of Figure() object for writing text. Because my text is > long, I use line breaker (\n) to write multiple lines with a single > call. This works fine except the line spacing is really tight and I wish I > could set a bigger line spacing. Does anyone know if this is > possible? Thanks for your time. Currently not, the pad between the newline is hard coded, but we could expose it as a parameter w/o too much work. JDH |
|
From: Edin S. <edi...@gm...> - 2007-07-10 17:13:52
|
On 7/10/07, Kaushik Ghose <kg...@um...> wrote:
> Thanks Edin! Yes, that worked!
You're welcome!
> There is still an issue with sub/super
> scripts though. They are inverted i.e. superscripts become subscripts.
> I'm attaching an example, created using
>
> m.text(0 ,0 ,'$\sum_{n=1}^{100} = 99^5 * q_i +
> \delta$');m.axis('off');m.savefig('eraseme.svg')
Hmm. I'm not sure whether this is a problem with matplotlib or
inkscape. I had some weird problems with inkscape on Ubuntu Feisty
recently, like: when I open the file from Nautilus (right click->open
with Inkscape) it is completely turned around; when I open Inkscape
(blank file), and open the file from within inkscape everything is
displayed correctly.
Have you opened the file in other viewers?
Is anyone else having the same problem?
Cheers,
Edin
|
|
From: Jianfu P. <Jia...@gs...> - 2007-07-10 17:12:56
|
Hi, I use Text() call of Figure() object for writing text. Because my text is long, I use line breaker (\n) to write multiple lines with a single call. This works fine except the line spacing is really tight and I wish I could set a bigger line spacing. Does anyone know if this is possible? Thanks for your time. Jianfu |
|
From: Giorgio F. G. <gi...@gi...> - 2007-07-10 15:35:44
|
Well I did fix it myself in the meanwhile. I must say I don't like working with the CVS because I am planning to release the application I am writing and I need to guarantee a minimal version of the packages that the end user should eventually install without caring too much about the CVS. Thank you anyway. Giorgio On 7/7/07, Jouni K. Sepp=E4nen <jk...@ik...> wrote: > > Another bug, though, comes with backend_pdf.py > > The function embedPDF in the class PdfFile has a call to > > encodings.cp1252.decoding_map[charcode] > > I believe this was fixed by Michael Droettboom in svn revision 3450. > You can apply the patch to your copy if you don't want to use > in-development versions: > > > > -- > Jouni K. Sepp=E4nen > http://www.iki.fi/jks > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Matplotlib-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users > > > |
|
From: John H. <jd...@gm...> - 2007-07-10 13:28:46
|
On 7/10/07, Kaushik Ghose <kg...@um...> wrote: > > > > I looked into this. You just have to install (copy) the BaKoMa fonts > > (TrueType version of the Computer Modern fonts) into your system's > > font dir, so the svg viewer can see them. These fonts are located in > > the "matplotlib/mpl-data/fonts/ttf" dir (the cm*.ttf files). > > > > > Thanks Edin! Yes, that worked! There is still an issue with sub/super > scripts though. They are inverted i.e. superscripts become subscripts. > I'm attaching an example, created using Hey Edin, if you get a minute, could you contribute a patch against the faq in htdocs/faq.html.template explaining how to install the bakoma fonts for svg viewers? Is this sufficiently difficult that it merits a FAQ? JDH |
|
From: Kaushik G. <kg...@um...> - 2007-07-10 13:08:34
|
>
> I looked into this. You just have to install (copy) the BaKoMa fonts
> (TrueType version of the Computer Modern fonts) into your system's
> font dir, so the svg viewer can see them. These fonts are located in
> the "matplotlib/mpl-data/fonts/ttf" dir (the cm*.ttf files).
>
Thanks Edin! Yes, that worked! There is still an issue with sub/super
scripts though. They are inverted i.e. superscripts become subscripts.
I'm attaching an example, created using
m.text(0 ,0 ,'$\sum_{n=1}^{100} = 99^5 * q_i +
\delta$');m.axis('off');m.savefig('eraseme.svg')
thanks!
-Kaushik
|
|
From: Edin S. <edi...@gm...> - 2007-07-10 08:21:18
|
On 7/7/07, Edin Salkovic <edi...@gm...> wrote: > On 7/6/07, Kaushik Ghose <kg...@um...> wrote: > > Hi Edin, (...) > > Actually the original string renders as desired. Its the svg save that > > causes the problem. > > > > I gather this is due to incomplete implementation of svg export. > > > > thanks! > > -Kaushik > > Sorry, I see the problem now. Unfortunately I wont have the resources > to investigate into this this weekend. It's past midnight here, and > tomorrow early I have to travel. > > Best, > Edin > I looked into this. You just have to install (copy) the BaKoMa fonts (TrueType version of the Computer Modern fonts) into your system's font dir, so the svg viewer can see them. These fonts are located in the "matplotlib/mpl-data/fonts/ttf" dir (the cm*.ttf files). HTH, Edin |