[Dvipng] pict2e problems

[Tim Arnold]

Hi,
I really like dvipng, and rely on it heavily for producing and
publishing technical documentation. I recently came across a problem
with picture environments. I get the same results with dvipng 1.6 and
1.9. I'm using pdfeTeXk, Version 3.141592-1.30.4-2.2 on HPux10.

If I do not include pict2e.sty, I get warnings from LaTeX. If I do
include pict2e.sty, I get warnings from dvipng.
I've winnowed it down to the following:
\documentclass{article}
%\usepackage{pict2e}
% If pict2e is omitted:
% LaTeX Warning: \oval, \circle, or \line size unavailable
%
% If pict2e is included:
% dvipng warning: at (176,143)
% unimplemented \special{ps: save /setgray { pop } def}
%
\begin{document}
\setlength{\unitlength}{1px}

\begin{picture}(200,100)
\put(50,50){\oval(120,80)[t]}
\end{picture}

\end{document}

Any ideas on what I can do here?
thanks,
--Tim Arnold

[Jan-Åke Larsson]

Post by Tim Arnold
Hi,
I really like dvipng, and rely on it heavily for producing and
publishing technical documentation. I recently came across a problem
with picture environments. I get the same results with dvipng 1.6 and
1.9. I'm using pdfeTeXk, Version 3.141592-1.30.4-2.2 on HPux10.

It seems that pict2e uses raw PostScript specials for the pictures. The
CVS version of dvipng supports raw PostScript to some degree, and the
example you sent certainly works. So try the CVS version.

There remains to implement more of the raw PostScript special syntax ("a
tortourus history" to quote the dvips manual) and to do some testing.

Please report any problems you have, or indeed any success. I intend to
release this as version 1.10 in time.

/JÅ

[Jan-Åke Larsson]

Post by Jan-Åke Larsson
It seems that pict2e uses raw PostScript specials for the pictures. The
CVS version of dvipng supports raw PostScript to some degree, and the
example you sent certainly works. So try the CVS version.

Ah, forgot to say. I needed to exchange

\setlength{\unitlength}{1px}

for

\setlength{\unitlength}{1pt}

TeX doesn't know how large a pixel will be....
/JÅ

[Tim Arnold]

Post by Jan-Åke Larsson

Post by Tim Arnold
Hi,
I really like dvipng, and rely on it heavily for producing and
publishing technical documentation. I recently came across a problem
with picture environments. I get the same results with dvipng 1.6 and
1.9. I'm using pdfeTeXk, Version 3.141592-1.30.4-2.2 on HPux10.

It seems that pict2e uses raw PostScript specials for the pictures.
The CVS version of dvipng supports raw PostScript to some degree, and
the example you sent certainly works. So try the CVS version.
There remains to implement more of the raw PostScript special syntax
("a tortourus history" to quote the dvips manual) and to do some
testing.
Please report any problems you have, or indeed any success. I intend
to release this as version 1.10 in time.
/JÅ

Hi Jan,
Thanks for the quick reply! Now, with the cvs version of dvipng, the
problem does go away, but I have a new warning--does it look familiar
to you? (the resulting png seems ok).

This is dvipng 1.9 Copyright 2002-2006 Jan-Ake Larsson
dvipng warning: cannot find ps2pk.map, nor psfonts.map
kpathsea: Running mktexpk --mfmode cx --bdpi 300 --mag 1+100/300 --dpi
400 cmr10
mktexpk: /shadow/system/tex/texmf-var/fonts/pk/cx/public/cm/cmr10.400pk
already exists.

which is weird, since I get this response from the unix command line:
kpsewhich ps2pk.map
/shadow/system/tex/texmf-var/fonts/map/dvips/updmap/ps2pk.map

thanks for any insights on this, and thanks for your work on dvipng!
--Tim Arnold
SAS Institute, Inc.

[Jan-Åke Larsson]

Post by Tim Arnold
This is dvipng 1.9 Copyright 2002-2006 Jan-Ake Larsson
dvipng warning: cannot find ps2pk.map, nor psfonts.map
kpathsea: Running mktexpk --mfmode cx --bdpi 300 --mag 1+100/300 --dpi
400 cmr10
mktexpk: /shadow/system/tex/texmf-var/fonts/pk/cx/public/cm/cmr10.400pk
already exists.
kpsewhich ps2pk.map
/shadow/system/tex/texmf-var/fonts/map/dvips/updmap/ps2pk.map

--------------------------------------
2.4 Installation outside the texmf tree

In some cases, a dvipng binary installed outside the texmf tree will not
be able to find virtual fonts, or the PostScript font maps (normally
used by dvips). This may be because _only_ $SELFAUTOLOC, $SELFAUTODIR,
and $SELFAUTOPARENT are used in the texmf tree configuration file
`texmf.cnf'. If so, give the switch `--enable-selfauto-set' to
`./configure'. This will make dvipng adjust these three internally so
that kpathsea thinks that dvipng _is_ installed in the texmf tree.
---------------------------------------

If this doesn't help, ask again.
/JÅ