Ps2pdf paper size pdf

Report forwarded to debian-bugs-dist lists. Message 5 received at submit bugs. Information forwarded to debian-bugs-dist lists. Message 10 received at bugs. Message 15 received at bugs. Bug marked as not found in version 8. Message 24 received at done bugs. The xcfcmyk device creates output files with spot colors placed in separate alpha channels.

The XCF file format does not currently directly support spot colors. Overprinting with spot colors is not allowed if the tint transform function is being used to convert spot colors. Thus if spot colors are used with overprinting, then the appearance of the result can differ between output devices.

If the test succeeds, Ghostscript tries to open the file using the name given. Otherwise it tries directories in this order:. By default, Ghostscript no longer searches the current directory first but provides -P switch for a degree of backward compatibility. Note that Ghostscript does not use this file searching algorithm for the run or file operators: for these operators, it simply opens the file with the name given.

To run a file using the searching algorithm, use runlibfile instead of run. Adobe specifies that resources are installed in a single directory. Ghostscript instead maintains a list of resource directories, and uses an extended method for finding resource files.

The search for a resource file depends on whether the value of the system parameter GenericResourceDir specifies an absolute path. The user may set it as explained in Resource-related parameters. The first path with Resource in it is used, including any prefix up to the path separator character following the string Resource. If the value of the system parameter GenericResourceDir is an absolute path the default , Ghostscript assumes a single resource directory. It concatenates :. If the value of the system parameter GenericResourceDir is not an absolute path, Ghostscript assumes multiple resource directories.

In this case it concatenates :. Due to possible variety of the part 1, the first successful combination is used. For example, if the value of the system parameter GenericResourceDir is the string.. So in this example, if the user on a Windows platform specifies the command line option -I.

The string.. In the case of multiple resource directories, the default ResourceFileName procedure retrieves either a path to the first avaliable resource, or if the resource is not available it returns a path starting with GenericResourceDir. Consequently Postscript installers of Postscript resources will overwrite an existing resource or add a new one to the first resource directory.

To look up fonts, after exhausting the search method described in the next section , it concatenates together. Ghostscript has a slightly different way to find the file containing a font with a given name. See the documentation of fonts for details. Then, when Ghostscript needs to find a font that isn't already loaded into memory, it goes through a series of steps. CID fonts e. Chinese, Japanese and Korean are found using a different method. SGI in place of Fontmap or Fontmap. It says: "15 files, 15 scanned, 0 new fonts".

We think this problem has been fixed in Ghostscript version 6. See Fontmap. Sol instead. Also, on Solaris 2. The fonts Sun distributes on Solaris 2. These paths may not be exactly right for your installation; if the indicated directory doesn't contain files whose names are familiar font names like Courier and Helvetica, you may wish to ask your system administrator where to find these fonts.

Adobe Acrobat comes with a set of fourteen Type 1 fonts, on Unix typically in a directory called There is no particular reason to use these instead of the corresponding fonts in the Ghostscript distribution which are of just as good quality , except to save about a megabyte of disk space, but the installation documentation explains how to do it on Unix.

CID fonts are PostScript resources containing a large number of glyphs e. Please refer to the PostScript Language Reference, third edition, for details. CID font resources are a different kind of PostScript resource from fonts. In particular, they cannot be used as regular fonts. CID font resources must first be combined with a CMap resource, which defines specific codes for glyphs, before it can be used as a font. This allows the reuse of a collection of glyphs with different encodings. Another method is possible using the composefont operator.

They are not found using Font lookup on the search path or font path. In general, it is highly recommended that CIDFonts used in the creation of PDF jobs should be embedded or available to Ghostscript as CIDFont resources, this ensures that the character set, and typeface style are as intended by the author. In cases where the original CIDFont is not available, the next best option is to provide Ghostscript with a mapping to a suitable alternative CIDFont - see below for details on how this is achieved.

As shipped, this uses the DroidSansFallback. This font contains a large number of glyphs covering several languages, but it is not comprehensive. There is, therefore, a chance that glyphs may be wrong, or missing in the output when this fallback is used. As with any font containing large numbers of glyphs, DroidSansFallback.

The build system will cope with the file being removed, and the initialization code will avoid adding the internal fall back mapping if the file is missing. If DroidSansFallback. As the name suggests, this will result in all the glyphs from a missing CIDFont being replaced with a simple bullet point. This type of generic fall back CIDFont substitution can be very useful for viewing and proofing jobs, but may not be appropriate for a "production" workflow, where it is expected that only the original font should be used.

The file forms a table of records, each of which should use one of three formats, explained below. Note that the default Ghostscript build includes such configuration and resource files in a rom file system built into the executable. So, to ensure your changes have an effect, you should do one of the following: rebuild the executable; use the "-I" command line option to add the directory containing your modified file to Ghostscript's search path; or, finally, build Ghostscript to use disk based resources.

Please pay attention that both them must be designed for same character collection. The trailing semicolon and the space before it are both required.

If the array consists of 2 elements, the first element is a string, which specifies Ordering ; the second element is a number, which specifies Supplement. If the array consists of 3 elements, the first element is a string, which specifies Registry ; the second element is a string, which specifies Ordering ; the third element is a number, which specifies Supplement. The TrueType font must contain enough characters to cover an Adobe character collection, which is specified in Ordering and used in documents.

The script can also be run separately e. Note that the font file path uses Postscript syntax. Because of this, backslashes in the paths must be represented as a double backslash.

This can complicate substitutions for fonts with non-Roman names. This cannot be used directly in a cidfmap file because the xx notation in names is a PDF-only encoding. Instead, try something like:. This lets you specify a name using any sequence of bytes through the encodings available for Postscript strings. There is no reliable way to generate a character ordering for truetype fonts. The 7. This is replaced in the 8.

As a workaround the PDF interpreter applies an additional substitution method when a requested CID font resource is not embedded and it is not available. The latter may look some confusing for a font name, but we keep it for compatibility with older Ghostscript versions, which do so due to a historical reason. If the CID font file is not embedded, the Adobe-Identity record depends on the document and a correct record isn't possible when a document refers to multiple Far East languages.

In the latter case add individual records for specific CID font names used in the document. Ghostscript can make use of Truetype fonts with a Unicode character set. To do so, you should generate a NOTE: non-standard! The resulting output will be compliant with the spec unlike the input. Ghostscript currently doesn't do a very good job of deleting temporary files if it exits because of an error; you may have to delete them manually from time to time.

The original PostScript language specification, while not stating a specific word sise, defines 'typical' limits which make it clear that it was intended to run as a bit environment.

Ghostscript was originally coded that way, and the heritage remains within the code base. This is the only real purpose in adding support for large integers, however since that time, we have made some efforts to allow for the use of bit words; in particular the use of integers, but also lifting the 64K limit on strings and arrays, among other areas. Even when the build supports bit words, you should be aware that there are areas of Ghostscript which do not support bit values.

Sometimes these are dependent on the build and other times they are inherent in the architecture of Ghostscript the graphics library does not support bit co-ordinates in device space for example, and most likely never will.

Note that the extended support for bit word size can be disabled by executing 'true. The Ghostscript distribution includes some Unix shell scripts to use with Ghostscript in different environments. These are all user-contributed code, so if you have questions, please contact the user identified in the file, not Artifex Software.

For instance,. If the "directory" name ends with a closing square bracket " ] ", it is taken to refer to a real directory, for instance. To preserve the case of switches, quote them like this:. If you are using on an X Windows display, you can set it up with the node name and network transport, for instance. When passing options to ghostcript through a batch file wrapper such as ps2pdf. For example:.

There is also an older version for MS Windows called just gswin32 that provides its own window for the interactive postscript prompt. For printer devices, the default output is the default printer.

This can be modified as follows. Invoking Ghostscript from the command prompt in Windows is supported by the Windows executable described above. In addition to the device parameters recognized by all devices , Ghostscript's X driver provides parameters to adjust its performance.

Users will rarely need to modify these. Note that these are parameters to be set with the -d switch in the command line e. Xdefaults file. Because of bugs in the SCO Unix kernel, Ghostscript will not work if you select direct screen output and also allow it to write messages on the console.

If you are using direct screen output, redirect Ghostscript's terminal output to a file. Because Ghostscript must initialize the PostScript environment before executing the commands specified by this option it should be specified after other setup options.

Specifically this option 'bind's all operations and sets the systemdict to readonly. Note that by "library files" here we mean all the files identified using the search rule under " How Ghostscript finds files " above: Ghostscript's own initialization files, fonts, and files named on the command line. This means that -p can do the job of both -d and -s.

Broadly, only use -p if you cannot set what you want using -s or -d. Also, internally, after setting an parameter with -p we perform an initgraphics operation. This is required to allow changes in parameters such as HWResolution to take effect. This means that attempting to use -p other than at the start of a page is liable to give unexpected results. However, device parameters set this way PageSize , Margins , etc. As noted above, -d and -s define initial values for PostScript names.

Some of these names are parameters that control the interpreter or the graphics engine. Otherwise, images are rendered using the nearest neighbour scaling Bresenham's line algorithm through the image, plotting the closest texture coord at each pixel. When downscaling this results in some source pixels not appearing at all in the destination.

When upscaling, each source pixels will cover at least one destination pixel. This allows for a performance vs. Every source pixel will contribute partially to the destination pixels. Computationally, image interpolation is much more demanding than without interpolation lots of floating point muliplies and adds for every output pixel vs simple integer additions, subtractions, and shifts. In all but special cases image interpolation uses a Mitchell filter function to scale the contributions for each output pixel.

When upscaling, every output pixel ends up being the weighted sum of 16 input pixels, When downscaling more source pixels will contribute to the interpolated pixels. Every source pixel has some effect on the output pixels. Note that because of the way antialiasing blends the edges of shapes into the background when they are drawn some files that rely on joining separate filled polygons together to cover an area may not render as expected with GraphicsAlphaBits at 2 or 4.

Further note; because this feature relies upon rendering the input it is incompatible, and will generate an error on attempted use, with any of the vector output devices. PCL andPostScript cannot be handled in ths way, and so all the pages must be interpreted.

Pages are scaled to fit the requested number horizontally and vertically, maintaining the aspect ratio. If the scaling selected for fitting the nested pages leaves space horizontally on the master page, the blank area will be added to the left and right of the entire row of nested pages.

If the fit results in vertical space, the blank area will be added above and below all of the rows. If there are any nested pages on the master page, the partially filled master page will be output.

Printer devices typically reallocate their memory whenever the transparency use of a page changes from one page having transparency, to the next page not having transparency, or vice versa.

This would cause problems with Nup, possibly leading to lost or corrupt pages in the output. To avoid this, the Nup device changes the parameters of the page to always set the PageUsesTransparency flag.

While this should be entirely transparent for the user and not cause extra transparency blending operations during the standard rendering processes for most devices, it may cause devices to use the clist rather than PageMode. Useful only for compatibility with Adobe printers for loading some obsolete fonts. This may be useful in environments without a file system. This may be useful for debugging. This may be needed if the platform fonts look undesirably different from the scalable fonts.

This may be needed to ensure consistent rendering on the platforms with different fonts, for instance, during regression testing.

Specifies alternate name or names for the Fontmap file. Note that the names are separated by " : " on Unix systems, by " ; " on MS Windows systems, and by " , " on VMS systems, just as for search paths. Also, in this case, the font returned by findfont is the actual font named fontname , not a copy of the font with its FontName changed to the requested one.

The font specified fontname will be embedded instead, limiting all future users of the document to the same approximate rendering. The value is platform dependent. It must end with a directory separator. Adobe specifies GenericResourceDir to be an absolute path to a single resource directory. Ghostscript instead maintains multiple resource directories and uses an extended method for finding resources, which is explained in "Finding PostScript Level 2 resources".

Due to the extended search method, Ghostscript uses GenericResourceDir only as a default directory for resources being not installed. Therefore GenericResourceDir may be considered as a place where new resources to be installed. The default implementation of the function ResourceFileName uses GenericResourceDir when 1 it is an absolute path, or 2 the resource file is absent.

The extended search method does not call ResourceFileName. Active Oldest Votes. Improve this answer. Raman Raman What was the error message? Does your input postscript contain a bounding box? You appear to have downvoted but you don't provide a lot of information.

No error shown but the resulting PDF does not preserve the page size. As you say, maybe that option reads the bounding box, but this question is about the page size, which is stored in the DocumentMedia header, see my answer below. I updated my answer to reflect its limitations. An A4 page has a dimension of xpt PostScript points. Ghostscript internally by default computes with a resolution of pixels per inch when it comes to PDF output.

Hence for your case in question 8. Kurt Pfeifle Kurt Pfeifle Now I corrected the question. Re: ps2pdf page size problem Post by kyp4 » Sun Mar 07, pm Thanks a lot for the suggestions guys. I didn't know prosper was deprecated or never would have even messed with it.

I am using powerdot now and it's working great. It uses a standard letter size so the problem was avoided altogether. It did produce a PDF with the wrong orientation was portrait when it should have been landscape but a simple rotation in evince solved that problem.