Dear John,
From: John Hunter [mailto:jdhunter@…4…]
I don't think you need both. I think you could just do
rcParams['font.latex.filename'] = 'mypresentation.llfc'
rcParams['font.latex.filename'] = None
Good idea... nice and clean...
> The "low level font command" input file has the
> following included:I think it would be much easier for us to deal with this
if you submit it as a proper patch against CVS and upload
it to the sf site.
I'm not following... This "low level font command" input file is user
specific...
> ... def get_tex_command(self, tex, fname): fh =
> file(fname, 'w') if rcParams['text.tex.engine'] ==
> 'latex': print >>fh, r"""\documentclass{article}
> \usepackage{%s} \setlength{\paperwidth}{72in}
> \setlength{\paperheight}{72in} \pagestyle{empty}
> \begin{document}""" % (rcParams['font.latex.package'])
> if rcParams['font.latex.inputfile']: inputfile =
> rcParams['font.latex.inputfile.filename'] if
> os.path.exists(inputfile): print >>fh, r"\input{%s}" %
> inputfile print >>fh, r"""%s \end{document}""" % texI worry that this is starting to get hairy -- perhaps we
should look into separating the latex from the code more cleanly.
I think the problem here has to do with Windows line breaks on non
Windows computers...
Was the attached file just as "hairy"...?
I think it would be much easier for us to deal with this
if you submit it as a proper patch against CVS and upload
it to the sf site. Could I trouble you to do that?
Yes, but first I would like to add a some python code to allow for a
"LaTeX preamble" input file for stuff like:
\DeclareMathAlphabet\mathscr{T1}{futs}{m}{it}
For custom mathscript or for custom macro definitions used within mpl
text..
User would also be able to load additional packages, like:
\usepackage[afrikaans,english]{babel} % Or other languages
\usepackage[iso,english]{isodate} % For ISO style date format in
conjunction with the babel package
\usepackage{numprint} % For 123 456,789 number format
instead of 123,456.789
There would then be two optional LaTeX input files:
- a "LaTeX preamble" input file and/or
- a "low level font command" input file
(it would be difficult to combine them into one...)
Selectable with:
rcParams[latex.preamble.filename'] = 'MySimmulation.prbl
rcParams[latex.lowlevelfontcommand.filename] = 'MyPresentation.llfc'
Any suggestions for better rcParams names... (and extension... or is it
necessary, it could actually be anything... but a standard would be...
"nice")
Finally, with:
\usepackage{helvet}
in the "LaTeX preamble" input file,
rcParams['font.latex.package'] would become unnecessary... but IMHO
should be retained...
Kind regards,
Peter-Jan Randewijk
Senior Lektor - Drywingselektronika & Elektriese Aandrywing
-oOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOo-
Departement E&E. Ingenieurswese
Universiteit Stellenbosch
Privaatsak X1
Matieland, 7603
Suid-Afrika
Tel: +27 (0) 21 808 4457 (w)
Faks: +27 (0) 21 808 3951 (w)
Tel: +27 (0) 21 883 8592 (h)
Sel: +27 (0) 83 556 5809 (h)
-oOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOo-
···
-----Original Message-----