Minimum unique abbreviation of option is acceptable. You may use double hyphens instead of a single hyphen to denote options. You may use white space in place of the equals sign to separate an option name from its value.
This program is part of Netpbm.
pamtopng reads a Netpbm image as input and produces a PNG image as output.
Color component values in PNG files are either 8 or 16 bits wide, so where necessary pamtopng scales colors to have a maxval of 255 or 65535. In that case, it will add an sBIT chunk to indicated the original bit-depth.
pamtopng works only on images with maxval 1, 3, 15, 255, or 65535. You can use pamdepth to convert an image with some other maxval to one of these.
pamtopng produces a color PNG from a color PAM, even if the only colors in the image are shades of gray. To create a graycale PNG, from such an image (which might be slightly smaller), you can use other Netpbm programs to convert the input to grayscale.
Netpbm contains another program for generating PNG images: pnmtopng. pnmtopng is a much older program - it is in fact the first program in the world that could generate a PNG. pnmtopng is a complex, feature-laden program. It lets you control various arcane aspects of the conversion and create PNGs with various arcane features. It does various transformations on the image to create the greatest compression possible, to a degree that probably doesn't make any difference in the modern world.
The main advantage pamtopng has over pnmtopng is that the former can use the transparency channel of a PAM image to generate the transparency information in the PNG. In contrast, handling of the alpha channel is very cumbersome with pnmtopng.
One difference that does not exist, that some people might incorrectly infer from the names, is the possible input formats. Both programs can take PBM, PGM, PPM, and PAM input.
Because pnmtopng has been around virtually forever, programs and procedures that use it are more portable than those that use pamtopng. Its age and popularity also probably make it have fewer bugs.
pamtopng does not have any way to do what the following do in pnmtopng:
These are some of the other functions of pnmtopng that pamtopng lacks:
Features that exist in both programs are controlled by largely the same command syntax. But there are these differences:
In addition to the options common to all programs based on libnetpbm (most notably -quiet, see Common Options), pamtopng recognizes the following command line options:
Specify the color (color) as described for the argument of the pnm_parsecolor() library routine. E.g. red or rgb:ff/00/0d.
The chroma_list value is a blank-separated list of 8 floating point decimal numbers: the CIE-1931 X and Y chromaticities (in that order) of each of white, red, green, and blue, in that order.
This information goes into the PNG's cHRM chunk.
In a shell command, make sure you use quotation marks so that the blanks in chroma_list don't make the shell see multiple command arguments.
intent is one of:
The output contains a distinct tEXt chunk for each entry in the file.
Here is an example of a text string file:
Title PNG file
Author John Doe
Description how to include a text chunk
PNG file
"Creation Date" 2015-may-11
Software pamtopng
The file is divided into entries, each entry comprising consecutive lines of text. The first line of an entry starts in the first column (i.e. the first column is not white space) and every other line has white space in the first column. The first entry starts in the first line, so it is not valid for the first line of the file to have white space in its first column.
The first word in an entry is the key of the text string (e.g. "Title"). It begins in column one of the line and continues up to, but not including, the first delimiter character or the end of the line, whichever is first. You can enclose the key in double quotes in which case the key can consists of multiple words. The quotes are not part of the key. The text string per se begins after the key and any delimiter characters after it, plus the text in subsequent continuation lines.
There is no limit on the length of a file line or entry or key or text string. There is no limit on the number of entries.
For each record, you must specify the language and give the key both in English and in the text string language.
Example:
Language nl-NL Taal nl-NL
Title nl-NL Titel PNG file
Author nl-NL Auteur Pietje Puk
Description nl-NL Omschrijving Tekst in het Nederlands.
The language specification is based on the ISO 639-1 standard, see http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes for the valid codes. The format is either a two character "nl" or an extended code like "en-US".
When you specify this option, pamtopng must hold the entire image in memory at once, whereas without it, the program holds only one raster row at a time. If you don't have enough memory for that, you might suffer extreme slowdowns or failure - not just in the process running pamtopng, but potentially throughout the system that shares memory with it. pnmtopng does not have this limitation (it holds only one row at a time in memory even when generating an interlaced PNG).
This option was new in Netpbm 10.86 (March 2019).
For information on the PNG format, see http://www.w3.org/TR/PNG/, http://libpng.org/pub/png/, http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes and http://schaik.com/png/.
pamtopng was new in Netpbm 10.70 (June 2015).
Before pamtopng, the two ways to create PNG images with Netpbm were pnmtopng and pamrgbatopng. The history of the former is discussed above. The latter was added to Netpbm in 2005 as a cheap way to fill a significant need that pnmtopng did not: the ability to turn the alpha channel in a PAM image into the alpha channel in a PNG image.
Handling of the alpha channel with pnmtopng is very cumbersome (as was dealing with alpha channels in general before the introduction of the PAM format). pamrgbatopng could do what people wanted with the alpha channel, but nothing else. It was a very small program with literally no command line options.
The goal in those days was eventually to expand pnmtopng to do the PAM alpha channel thing, rename it to pamtopng, and retire pamrgbatopng. But pnmtopng is such a complex program, because of its dizzying array of features and its need for backward compatibility, that adding that one capability to it was a daunting task and for ten years nobody attempted it.
In 2015, one of the authors of the original pnmtopng (from before it was even part of Netpbm -- a program that shared essentially no lines of code with pnmtopng of 2015) decided to go in a different direction. While many features of pnmtopng were pretty important and easy to implement, many others were probably of no use in the modern world or at least not important enough to justify the complexity they lent to the code. (The features thought to be outdated were ones that were intended to make the PNG output slightly smaller - something considerably less important with the declining cost of computer resources).
And there was an opportunity to drop those features: We could use the new name "pamtopng" for a new program, keep the existing program under the name "pnmtopng", and avoid most backward compatibility trouble.
Therefore, Willem van Schaik wrote an intermediate level program that had all the most important features of pnmtopng, plus the alpha channel handling of pamrgbatopng, with nice, simple code. That was pamtopng.
Because pamrgbatopng had no options, pamtopng was backward compatible with it without even trying. Therefore, as soon as we added pamtopng to Netpbm, we removed pamrgbatopng and recommended that pamrgbatopng be installed as an alias for pamtopng.