dvipng manpage

There is now a dvipng man page.
/JÅ

--

-- 
There are two kinds of people:
  1.) Those who have sent email to the wrong address
  2.) Those who will send email to the wrong address.

-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click

Re: dvipng manpage

Jan-Åke Larsson <jalar <at> mai.liu.se> writes:

> There is now a dvipng man page.

Good idea.  I still have some things to do with regard to
preview-latex 0.7.9, but should be able to in the next few days.

--

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click

PDFTeX support...

Ok, I checked in pretty complete PDFTeX support.  If you have
customized preview-required-option-list, you need to recustomize (one
needs the tightpdf option instead of dvips).  And you need to have
LaTeX-command-style choose pdflatex.  And you need to customize
preview-LaTeX-command-replacements to nil.

It works dandy except for one minor problem: previews are white (once
this works, they will be black on white instead of taking colors from
the screen, but one thing after the other).  And they are a bit small,
too.

When creating pdf files manually with tightpdf option, the PDF file
looks fine.  It is just the daemon operation of GhostScript in PDF
mode that somehow manages to white out the previews completely.

I have no clue what may be happening.  Maybe it is just my version of
GhostScript that is affected.  Maybe not.

It is a bit sad to release this in this state.

--

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

Ok, PDFLaTeX support now works as well...

But the stuff is still much too small and I have no clue who is at
fault here.  Nevertheless, stuff works right now, including the
correct colors mostly (actually, I get colors that are off and
stippled) and things.  The tightpdf option of preview.sty has been
removed again: I just use the tightpage option always, also on dvi.
This has the added advantage that I can set the PageSize to 1ptx1pt,
speeding up redundant calls of setpagedevice (I actually check for
this setting and skip initialization completely as long as the page
size is set to that).

Jan-Åke: preview.sty is now always called with the "tightpage" option:
If I see this correctly, dvipng will just accept those specs.

I don't see any option to specify the transparent color to dvipng
(meaning the color in which transparent pixels will get rendered to an
RGB image instead of RGBA).  Is there something like that?  At the
moment, this is just identical to the background color.  Which does
nothing when using Emacs.

I adapted the scale to dvipng's new conventions.  I also removed
everything that would stop PDFLaTeX from producing PDF.  Setting
preview-image-type to dvipng will use dvipng when DVI gets produced,
GhostScript on the PDF when PDF was produced.

This is the first time I checked out dvipng 1.0.  Sweet rendering
speed once the fonts are generated!

I guess we are quite close to release time.  I am tempted to leave PDF
state as it is right now and hope for a volunteer among our users to

PDF fixed...

Actually, if I want GhostScript to have a certain resolution, it
helps if I tell it so.  Doh.  I am an idiot.

PDF works now just as nice as DVI.  I still use pdf2dsc for a task
that could be perfectly well done without it, but I think that the
performance impact is not devastating.  One would have to separate
PostScript/PDF handling more thoroughly than what is the case right
now in order to get that right.

So I think we should be ready for release now.  I guess I'll be able
to call this 0.8 after all.

--

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

preview-latex 0.8 has been released.

It was a real bear getting the spec file to run (as can be witnessed
by the hundreds of checkins I needed).

I changed the package names to have the old names for redhat releases
(nobody else places "redhat" in RedHat RPMs, and besides, having a
".redhat" Source RPM file that is perfectly suitable for SuSE would be
an oxymoron) and "suse" for SuSE releases (mixed case extensions are
too hard to type).

Sorry for taking that liberty.  Getting all the paths right was
really darn hard.

Let's see when the bug reports start pouring in.

Oh, the release notes:

Release notes for version 0.8 of the preview-latex package:

preview-latex dresses up your LaTeX source by pasting judiciously
selected chunks (such as single formulas) chopped from unwieldy
preview pages right over their source in the Emacs/XEmacs buffer.  You
get to have your eye candy and edit it, too.

The employed style file `preview.sty' is independently useful for
extraction of selected text elements as images.  It now fully supports
pdftex including the `tightpage' option.

The package is released under the GNU Public License (GPL).  At the
current point of time, at least GNU Emacs-21.1 under the X window

rel-0-8; generating preamble fails

Remember to cover the basics.  Including a minimal LaTeX example
file exhibiting the problem might help.

Dumping a preview format fails:
Running `Preview-LaTeX' on `neutronbook' with ``\1latex -ini "&\1latex" prv_neutronbook.ini  "\nonstopmode\PassOptionsToPackage{active,tightpage,auctex}{preview}\AtBeginDocument{\ifx\ifPreview\undefined\RequirePackage[displaymath,floats,graphics,textmath,sections,footnotes]{preview}\fi}\input{neutronbook.tex}"''
/bin/sh: line 1: 1latex: command not found

Preview-LaTeX exited abnormally with code 127 at Mon Apr 12 12:28:13

Emacs  : XEmacs 21.4 (patch 9) "Informed Management" [Lucid] (i686-pc-linux) of Sat Oct 19 2002 on bjoern
Package: rel-0-8

current state:
==============

Output from running `gs -h':
AFPL Ghostscript 7.00 (2001-04-08)
Copyright (C) 2001 artofcode LLC, Benicia, CA.  All rights reserved.
Usage: gs [switches] [file1.ps file2.ps ...]
Most frequently used switches: (you can use # in place of =)
 -dNOPAUSE           no pause after page   | -q       `quiet', fewer messages
 -g<width>x<height>  page size in pixels   | -r<res>  pixels/inch resolution
 -sDEVICE=<devname>  select device         | -dBATCH  exit after last file
 -sOutputFile=<file> select output file: - for stdout, |command for pipe,
                                         embed %d or %ld for page #
Input formats: PostScript PostScriptLevel1 PostScriptLevel2 PDF
Available devices:
   x11 bbox x11alpha x11cmyk x11gray2 x11gray4 x11mono bmpmono bmpgray
   bmpsep1 bmpsep8 bmp16 bmp256 bmp16m bmp32b deskjet djet500 laserjet

rel-0-8; menu in xemacs does not work right

Remember to cover the basics.  Including a minimal LaTeX example
file exhibiting the problem might help.

Menu entries from OPtions onward do not work any.
Mouse click results in:
      Wrong type argument: stringp, nil
followed by:
	 button1 not defined.

Emacs  : XEmacs 21.4 (patch 9) "Informed Management" [Lucid] (i686-pc-linux) of Sat Oct 19 2002 on bjoern
Package: rel-0-8

current state:
==============

Output from running `gs -h':
AFPL Ghostscript 7.00 (2001-04-08)
Copyright (C) 2001 artofcode LLC, Benicia, CA.  All rights reserved.
Usage: gs [switches] [file1.ps file2.ps ...]
Most frequently used switches: (you can use # in place of =)
 -dNOPAUSE           no pause after page   | -q       `quiet', fewer messages
 -g<width>x<height>  page size in pixels   | -r<res>  pixels/inch resolution
 -sDEVICE=<devname>  select device         | -dBATCH  exit after last file
 -sOutputFile=<file> select output file: - for stdout, |command for pipe,
                                         embed %d or %ld for page #
Input formats: PostScript PostScriptLevel1 PostScriptLevel2 PDF
Available devices:
   x11 bbox x11alpha x11cmyk x11gray2 x11gray4 x11mono bmpmono bmpgray
   bmpsep1 bmpsep8 bmp16 bmp256 bmp16m bmp32b deskjet djet500 laserjet

Re: preview-latex 0.8 has been released.

* David Kastrup (2004-04-12) writes:

> Release notes for version 0.8 of the preview-latex package:

Thank you for your effort and this new release!

> Release 0.8 supports for the first time conversion with PDFLaTeX
> (however, the foreground color of Emacs buffers appears always black
> here, differing reports and PDFLaTeX/GhostScript expertise welcome),
> and conversion with dvipng.

This is the first time I tried dvipng.  I compared it with the output
of normal PNG creation (via GhostScript/PostScript I suppose) and have
some remarks or questions respectively.  There are two screenshots
which should illustrate the remarks; [1] shows dvipng's output
(`preview-image-type' set to `dvipng') and [2] shows normal PNG output
(`preview-image-type' set to `png').

1) dvipng's rendering in [1] is a bit pale.  The output in [2] is
   darker and blends smoother with the rest of the buffer (although
   dvipng's anti-aliasing seems nicer).  Is there a way to tweak
   dvipng in order to get a similar result?

2) In some cases dvipng's output occupies more (vertical) space
   compared to the default rendering method.  In the screenshots
   compare the distance between the line with the vector ("die durch
   den Punkt (..) geht") and the following line.  In the screenshot
   with dvipng the distance is larger.  I noticed a similar effect
   with footnote markers.  The default rendering method doesn't
   introduce additional space between lines with markers while dvipng

Re: rel-0-8; generating preamble fails

"Björn Pedersen" <bjoern.pedersen <at> arcor.de> writes:

> Dumping a preview format fails:
> Running `Preview-LaTeX' on `neutronbook' with ``\1latex -ini "&\1latex" prv_neutronbook.ini  "\nonstopmode\PassOptionsToPackage{active,tightpage,auctex}{preview}\AtBeginDocument{\ifx\ifPreview\undefined\RequirePackage[displaymath,floats,graphics,textmath,sections,footnotes]{preview}\fi}\input{neutronbook.tex}"''
> /bin/sh: line 1: 1latex: command not found

>  preview-dump-replacements '(preview-LaTeX-command-replacements
> 			     ("\\`\\(pdf\\)?\\(e?\\)\\(la\\)?tex\\(\\( -\\([^ \"]\\|\"[^\"]*\"\\)*\\)*\\)\\(.*\\)\\'"
"\\1\\2\\3tex -ini \"&\\1\\2\\3tex\" " preview-format-name ".ini \\7")
> 			     )
>  preview-undump-replacements '(("\\`\\(pdf\\)?\\(e?\\)\\(la\\)?tex\\(\\( -\\([^
\"]\\|\"[^\"]*\"\\)*\\)*\\).*\\input{\\([^}]*\\)}.*\\'" "\\1\\2\\3tex\\4 \"&"
preview-format-name "\" \\7")

This would appear to be a bug in the XEmacs regexp routines (probably
also prevalent in older Emacsen).  Sigh.  I knew I forgot some tests.

Does the following patch help? (if you are using one of the
ready-packaged versions, you'll need to use
byte-compile-file RET
on the preview.el file after applying it, then restart XEmacs).

--

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum