matplotlib-users Mailing List for matplotlib

John Hunter wrote:

> Awesome - impressive work for an afternoon.  Thanks for pointing me to
> that dvi specification reference.  I was trying to discern the format
> from TeX: The Program, which despite its literate style, was less
> accessible than the reference you pointed to.  It is painful, though,
> as you say, no matter how you slice it.
> 
> Funny that I missed tftopl in my hunt for a parser, which was sitting
> right on my system the whole time.

I know how you feel. *Believe* me. In any case, please use tftopl. I'm 
pretty sure there's a bug in how tfm.py reads the fixed-point values, 
but I'm giving up in favor of tftopl.

> In order to use this information in mathtext, we have reconstruct the
> mapping from TeX symbol name to font and character number for each of
> the tex symbols we use (cmr10, cmi10, cmex10 and cmsy10) .  Currently
> mathtext hardcodes the mapping from tex name to bakoma
> fontname/number.
> 
> A better approach would be to use either the mathml or unicode number
> as the internal code for each symbol, and then provide mappings from
> these to the tfm fontname/charnum and to the corresponding tex symbol
> names - my guess is that this has already been done and we just have
> to dig it up.

Does http://www.dessci.com/fr/support/tech/encodings/font_enc.stm help?

> Then we could use any of the fonts (Wolfram, Design Science, Symbol,
> AMS, Bakoma) at http://www.mozilla.org/projects/mathml/fonts/encoding
> for matplotlib mathtext, since the mapping from mathml/unicode to
> fontname/charnum already exists on pages like
> http://www.mozilla.org/projects/mathml/fonts/encoding/cmr.html, and is
> easily parsed (I already did this when I was working on PS mathtext
> with type1 fonts before Paul had the bright idea of just embedding the
> truetype fonts in the ps document and reusing what we already had.
> 
> In summary, it would be nice to be able to readily go from tex name
> <-> mathml/unicode name <-> fontname/charnum in a variety of files,
> including at a minimum the bakoma ttf and the corresponding tfm files.
> Got some images to process today <wink>
> 
> Does this sound like the right approach to you?

More or less. Converting from TeX encodings (which are arcane) to modern 
standards as soon as possible is almost certainly the best approach.

-- 
Robert Kern
rk...@uc...

"In the fields of hell where the grass grows high
  Are the graves of dreams allowed to die."
   -- Richard Harter

>>>>> "Carl" == Carl Dr Kleffner <cmk...@gm...> writes:

    Carl> Any thoughts to use Richard Kinchs Universal Modern fonts as
    Carl> well as the bellek fonts on his site (www.truetex.com)
    Carl> instead of the bakoma fonts? It seems that um and bellek are
    Carl> free to use and redistributable. This is not the case for
    Carl> bakoma in commercial use.  The quality of the fonts are
    Carl> excellent. Umlauts and more special signs are included
    Carl> compared to bakoma. The charnums are different however and
    Carl> not included on mozillas encoding page.

I would be very happy to support these fonts, especially if someone
(you, perhaps) provided the dictionary mapping tex symbol names to
name/charnum, as in the latex_to_bakoma dictionary in
matplotlib._mathtext_data.  The rest is easy, and I could provide an
rc param allowing you to select which fonts to include.  

We ought to expose the glyph names through FT_Get_Glyph_Name in the
ft2font module to facilitate this kind of thing....  I notice that,
for example, blex.ttf uses names like

    ceilingleftbigg ceilingrightbigg braceleftbigg bracerightbigg
    angbracketleftbigg angbracketrightbigg slashbigg backslashbigg
    parenleftBigg

which would make it fairly easy to do the mapping.

Since the bakoma fonts are the only things in the matplotlib distro
restricted for free, noncommercial use, this would be a nice addition.
If we later decide to go with a mathml/unicode representation
internally, it would be trivial to automatically convert the existing
dictionaries in _mathtext_data.

JDH

> Then we could use any of the fonts (Wolfram, Design Science, Symbol,
> AMS, Bakoma) at http://www.mozilla.org/projects/mathml/fonts/encoding
> for matplotlib mathtext, since the mapping from mathml/unicode to
> fontname/charnum already exists on pages like
> http://www.mozilla.org/projects/mathml/fonts/encoding/cmr.html, and is
> easily parsed (I already did this when I was working on PS mathtext
> with type1 fonts before Paul had the bright idea of just embedding the
> truetype fonts in the ps document and reusing what we already had.
> 

Any thoughts to use Richard Kinchs Universal Modern fonts as well
as the bellek fonts on his site (www.truetex.com) instead of 
the bakoma fonts? It seems that um and bellek are free to use and 
redistributable. This is not the case for bakoma in commercial use.
The quality of the fonts are excellent. Umlauts and more special 
signs are included compared to bakoma. The charnums are different 
however and not included on mozillas encoding page.

Regards

Carl-M Kleffner


> In summary, it would be nice to be able to readily go from tex name
> <-> mathml/unicode name <-> fontname/charnum in a variety of files,
> including at a minimum the bakoma ttf and the corresponding tfm files.
> Got some images to process today <wink>
> 
> Does this sound like the right approach to you?
> 
> JDH
> 
>

-- 
NEU +++ DSL Komplett von GMX +++ http://www.gmx.net/de/go/dsl
GMX DSL-Netzanschluss + Tarif zum supergünstigen Komplett-Preis!

>>>>> "Robert" == Robert Kern <rk...@uc...> writes:


    John> Another idea I had while reading Knuth's "TeX: The Program"
    John> is to use the layout information in the TFM font metric
    John> files.  Apparently math fonts have additional layout
    John> information in them, like where to place superscripts.  I've
    John> looked at several tfm parsing implementations, and

    Robert> I wish you luck!

Who needs luck when we've got people like you around! :-)

    Robert> Taking this as a challenge (and having little to do while
    Robert> waiting for images to process), I wrote a TFM parser that
    Robert> handles the extra parameters for math symbols. This
    Robert> format[1] is excruciatingly painful.

    Robert> http://starship.python.net/crew/kernr/tfm.py

    Robert> And then I realized that the output of tftopl(1) is
    Robert> incredibly easy to parse and contains the same
    Robert> information. <sigh>

    Robert> Either way, you now have the information you need for some
    Robert> fonts, at least.

Awesome - impressive work for an afternoon.  Thanks for pointing me to
that dvi specification reference.  I was trying to discern the format
from TeX: The Program, which despite its literate style, was less
accessible than the reference you pointed to.  It is painful, though,
as you say, no matter how you slice it.

Funny that I missed tftopl in my hunt for a parser, which was sitting
right on my system the whole time.

In order to use this information in mathtext, we have reconstruct the
mapping from TeX symbol name to font and character number for each of
the tex symbols we use (cmr10, cmi10, cmex10 and cmsy10) .  Currently
mathtext hardcodes the mapping from tex name to bakoma
fontname/number.

A better approach would be to use either the mathml or unicode number
as the internal code for each symbol, and then provide mappings from
these to the tfm fontname/charnum and to the corresponding tex symbol
names - my guess is that this has already been done and we just have
to dig it up.

Then we could use any of the fonts (Wolfram, Design Science, Symbol,
AMS, Bakoma) at http://www.mozilla.org/projects/mathml/fonts/encoding
for matplotlib mathtext, since the mapping from mathml/unicode to
fontname/charnum already exists on pages like
http://www.mozilla.org/projects/mathml/fonts/encoding/cmr.html, and is
easily parsed (I already did this when I was working on PS mathtext
with type1 fonts before Paul had the bright idea of just embedding the
truetype fonts in the ps document and reusing what we already had.

In summary, it would be nice to be able to readily go from tex name
<-> mathml/unicode name <-> fontname/charnum in a variety of files,
including at a minimum the bakoma ttf and the corresponding tfm files.
Got some images to process today <wink>

Does this sound like the right approach to you?

JDH

John Hunter wrote:

> Another idea I had while reading Knuth's "TeX: The Program" is to use
> the layout information in the TFM font metric files.  Apparently math
> fonts have additional layout information in them, like where to place
> superscripts.  I've looked at several tfm parsing implementations, and
> haven't found one yet that actually extracts this information; most
> extract the standard font information but not the special math
> information.  But if we could access this info, we could include the
> tfm files for common raster sizes and use the layout info crafted by
> the master himself.

Taking this as a challenge (and having little to do while waiting for 
images to process), I wrote a TFM parser that handles the extra 
parameters for math symbols. This format[1] is excruciatingly painful.

http://starship.python.net/crew/kernr/tfm.py

And then I realized that the output of tftopl(1) is incredibly easy to 
parse and contains the same information. <sigh>

Either way, you now have the information you need for some fonts, at least.

[1] 
http://www.ctan.org/tex-archive/dviware/driv-standard/level-0/dvistd0.pdf

-- 
Robert Kern
rk...@uc...

"In the fields of hell where the grass grows high
  Are the graves of dreams allowed to die."
   -- Richard Harter

After this fix to pycxx, I was able to create
matplotlib fine (with pygtk 2.4 patch). Thanks for a
quick response.

--- John Hunter <jdh...@ac...> wrote:

> >>>>> "Samir" == Samir Patel <mep...@ya...>
> writes:
> 
>     Samir> I am getting following error while
> compiling later version
>     Samir> of matplotlib with gcc 3.4.2: Any clue?
> 
> This is a pycxx bug that is fixed in pycxx and
> matplotlib cvs.  See
>
http://sourceforge.net/mailarchive/message.php?msg_id=9683332
> for the
> solution -- replace map(s) with map(m) on the
> offending line 2271 in
> CXX/Objects.hxx.
> 
> Hope this helps,
> JDH
> 



		
__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail 

>>>>> "Samir" == Samir Patel <mep...@ya...> writes:

    Samir> I am getting following error while compiling later version
    Samir> of matplotlib with gcc 3.4.2: Any clue?

This is a pycxx bug that is fixed in pycxx and matplotlib cvs.  See
http://sourceforge.net/mailarchive/message.php?msg_id=9683332 for the
solution -- replace map(s) with map(m) on the offending line 2271 in
CXX/Objects.hxx.

Hope this helps,
JDH

> Date: Mon, 25 Oct 2004 20:40:02 -0400
> From: Gary <pa...@in...>
> To: Chris Barker <Chr...@no...>
> CC:  mat...@li...
> Subject: Re: [Matplotlib-users] TeX in xlabel ?
>
> Chris Barker wrote:
>
> > Gary wrote:
> >
> >> AFAICT,  It is not possible to mix text and TeX symbols in a string
> >> and have it come out right.  For example, in
> >>
> >> xlabel(r'$\rm{Normalized Temperature} (kT/\epsilon)$'
> >> The text  comes out in TeX math mode ... not so pretty.  Please tell
> >> me what I've overlooked.
> >
> >
> > well, I'm not sure how this is supported in matplotlib, but in
> > LaTex,you would do:
> >
> > Normalized Temperature $(kT/\epsilon)$
> >
> > or:
> >
> > $\text{Normalized Temperature} (kT/\epsilon)$
> >
> > the "$" means put it in math mode, if you don't want "Normalized
> > Temperature" in math mode, don't put it inside the $$. The second puts
> > it all in math mode, but the text{} means set this in text mode.
> >
> > -Chris
> >
> Matplotlib doesn't support \text, and it requires that the first and
> last characters of a TeX string be $.  I guess it only processes
> mathmode.    Well, it can't do *everything*.  It would be nice to figure
> out a workaround...

Gary's example
     xlabel(r'$\rm{Normalized Temperature} (kT/\epsilon)$'
USED to work, in earlier versions of Matplotlib. It no longer does. I have
posted a similar issue a little while ago:
     http://sourceforge.net/mailarchive/message.php?msg_id=9681306
Unfortunately, I haven't really had the time to dig into the code to see what
has changed, but when I do, I'll let you know what I find. The solution
     xlabel(r'$\rm{Normalized \ Temperature} (kT/\epsilon)$'
somehow isn't entirely satisfactory.

As far as I can see, \rm{} in Matplotlib should act just the way \mbox{} does in
LaTeX, when you are already in math mode. And certainly, in LaTeX,
$$
xy = 0 \mbox{ but however } x \neq y
$$
produces the expected output in the expected fonts and with the expected
spacing.

Dominique