Re: [Savannah-hackers] submission of dvipng: A DVI-to-PNG converter - savannah.nongnu.org

[Alaska Subedi]

Hi,

I'm evaluating the project you submitted for approval in Savannah.

address@hidden writes:
 > A package was submitted to savannah.nongnu.org
 > This mail was sent to address@hidden, address@hidden
 > 
 > 
 > Jan-Åke Larsson <address@hidden> described the package as follows:
 > License: gpl
 > Other License: 
 > Package: dvipng: A DVI-to-PNG converter
 > System name: dvipng
 > Type: non-GNU
 > 
 > Description:
 > NAME
 >      dvipng - A DVI-to-PNG translator
 > 
 > SYNOPSIS
 >      dvipng [options] filename
 > 
 >      dvipng [options] [filename] -
 > 
 > DESCRIPTION
 >      This program makes PNG graphics from DVI files as obtained
 >      from TeX and its relatives.  The benefits include
 > 
 >      o   Speed. It is a very fast bitmap-rendering code for DVI
 >          files. On a fairly low-end laptop, it takes less than a
 >          second to generate 150 one-formula images. This makes
 >          dvipng suitable for generating large amounts of images
 >          on-the-fly, as needed in preview-latex, WeBWorK and
 >          others.
 > 
 >      o   It does not read the postamble, so it can be started
 >          before TeX finishes. There is a --follow switch that
 >          makes dvipng wait at EOF for further output, unless it
 >          finds the POST marker that indicates the end of the DVI.
 > 
 >      o   Interactive query of options. dvipng can read options
 >          interactively through stdin, and all options are usable.
 >          It is even possible to change the input file through
 >          this interface.
 > 
 >      o   Supports PK, VF, PostScript Type1, and TrueType fonts,
 >          color specials and simple PostScript inclusion specials.
 > 
 >      o   and more...
 > 
 > 
 > Other Software Required:
 > libgd (libpng, libz)
 > libkpathsea (alternatively libkps)
 > 
 > Other Comments:
 > 


Please provide us with the URL to the source code. You could also send
me the source code via email (address@hidden).
 
We wish to review your source code, even if it is not functional, to
catch potential legal issues early.
 
For example, to release your program properly under the GPL you must
include a copyright notice and permission-to-copy statements at
the beginning of every file of source code.  This is explained in
http://www.gnu.org/licenses/gpl-howto.html.  Our review would help catch
potential omissions such as these.

Regards,

Alaska Subedi