Firstly because the description of the page won't be the same, if your workflow relies upon for example finding rectangles in the description then it might not work after it has been processed by a high level device, as the rectangles may all have turned into lengthy path descriptions. In addition, any part of the original input which does not actually make marks on the page such as hyperlinks, bookmarks, comments etc will normally not be present in the output, even if the output is the same format.
In general the PDF interpreter and the PDF output device pdfwrite try to preserve the non-marking information from the input, but some kinds of content are not carried across, in particular comments are not preserved.
Instead, a new PDF file is being created, which should look the same as the original, but the actual insides of the PDF file are not the same as the original.
This may not be a problem, but if it's important to keep the original contents, then you need to use a different tool we'd suggest MuPDF, also available from Artifex. Of course, if the intention is to produce a modified PDF file for example, reducing the resolution of images, or changing the colour space , then clearly you cannot keep the original contents unchanged, and pdfwrite performs these tasks well. Text output The txtwrite device will output the text contained in the original document as Unicode.
The XML output is the same format as the MuPDF output, but no additional processing is performed on the content, so no block detection. Note the algorithm used is not the same as the MuPDF code, and so the results will not be identical. Rotated text is placed into textboxes. Heuristics are used to group glyphs into words, lines and paragraphs; for some types of formatting, these heuristics may not be able to recover all of the original document structure.
There are a number of caveats as mentioned in the overview above. In addition to the general comments there are some additional points that bear mentioning;. The pdfwrite device makes no attempt to handle this, and the resulting PDF file will not match the original input. The only way to deal with these types of file is to render the whole page to a bitmap and then 'wrap' the bitmap as a PDF file.
Currently we do not do this either, but it is possible that a future enhancement may do so. If the input contains PDF-compatible transparency, but the ps2write device is selected, or the pdfwrite device is selected, but has been told to limit the PDF feature set to a version less than 1.
In this case the entire page is rendered to a bitmap and that bitmap is 'wrapped up' in appropriate PDF or PostScript content. The output should be visually the same as the input, but since it has been rendered it will not scale up or down well, unlike the original, vector, content of the input.
The options in the command line may include any switches that may be used with the language interpreter appropriate for the input see here for a complete list. In addition the following options are common to all the pdfwrite family of devices, and should work when specified on the command line with any of the language interpreters.
By setting this flag, forms will be unrolled and stored in the output each time they are used, which avoids the problems. Note that the output file will of course be larger this way. Setting this switch will prevent these devices from emitting any fonts, all text will be stored as vectors or bitmaps in the case of bitmapped fonts in the page content stream. Note that this will produce larger output which will process more slowly, render differently and particularly at lower resolution produce less consistent text rendering.
Use with caution. The default value is true ; the false setting is intended only for debugging as it will result in larger output. The PostScript setdistillerparams and currentdistillerparams operators are also recognized when the input is PostScript, and provide an equivalent way to set these parameters from within a PostScript input file.
Although the name implies that these parameters are for controlling PDF output, in fact the whole family of devices use these same parameters to control the conversion into PostScript and EPS as well. The pdfwrite family of devices recognize all of the Acrobat Distiller 5 parameters defined in the DistillerParameters version 5 document available from the Adobe web site.
UseFlateCompression is treated as always on, but the switch CompressPages can be set to false to turn off page level stream compression.
Now that the patent has expired, we could change this should it become worthwhile. Note; if a non-integer downsample factor is used the code will clamp to the nearest integer if the difference is less than 0.
PDF 2. The new Ghostscript-specific value Gray converts all colors to DeviceGray. With the introduction of new color conversion code in version 9. NeverEmbed should always specify the original CID font name. To specify these, you must use PostScript, either by including it in the PostScript source or by passing the -c command-line parameter to ghostscript as described in Limitations below.
For example, including the PostScript string in your file in. This prevents the multiplication of JPEG artefacts caused by lossy compression. In addition this parameter will be ignored if the pdfwrite device needs to modify the source data. This can happen if the image is being downsampled, changing colour space or having transfer functions applied. Color Conversion and Management As of the 9. This considerably improves the color handling in both pdfwrite and ps2write, particularly in the areas of Separation and DeviceN color spaces, and Indexed color spaces with images.
The colour management code has no effect at all unless either ColorConversionStrategy or ConvertCMYKImagesToRGB is set, or content has to be rendered to an image this is rare and usually required only when converting a PDF file with transparency to a version Options based on object type image, text, linework are not used, all objects are converted using the same scheme. All other color spaces are converted appropriately.
Separation and DeviceN spaces will be preserved if possible ps2write cannot preserve DeviceN or Lab and if the alternate space is not appropriate a new alternate space will be created. By default Ghostscript determines viewing page orientation based on the dominant text orientation on the page. Sometimes, when the page has text in several orientations or has no text at all, wrong orientation can be selected.
Acrobat Distiller parameter AutoRotatePages controls the automatic orientation selection algorithm. On Ghostscript, besides input stream, Distiller parameters can be given as command line arguments. Valid values are: 0 portrait , 3 landscape , 2 upside down , and 1 seascape.
See Limitations below. Ghostscript passes the orientation values from DSC comments to the pdfwrite driver, and these are compared with the auto-rotate heuristic. If they are different then the DSC value will be used preferentially. The precise value for each control is listed in the table above. Many of the controls used for distiller parameters can be used on the command line with the -d or -s switches, and these will work correctly with PCL or PXL input.
When the input is PostScript or PDF we can use the -c and -f switches to send PostScript through the interpreter to control these parameters, but clearly this is not possible when the interpreter does not understand PostScript. In addition some features are controlled using the PostScript pdfmark operator and again that clearly is not possible unless we are using a PostScript interpreter to read the input.
However it is important to realise that these are not processed by a full PostScript interpreter, and there are syntactic rules which must be followed carefully when using these parameters. This is done for the pdfmark case only by defining a special non-standard pdfmark name PUTFILE , this simply takes the preceding string, and uses it as a fully qualified path to a file.
Any further pdfmark operations can then use the named object holding the file to access it. The easiest way to use these parameters is to create a 'settings' file, put all the commands in it, and then put it on the command line immediately before the real input file. For example:. The line breaks between "" below should be replaced with space characters, the double quote charcters " are required. Annotation types listed in this array will be preserved, whilst those not listed will be drawn according to the setting os ShowAnnots and ShowAnnotTypes.
By using the controls PreserveAnnots, PreserveAnnotTypes, ShowAnnots and ShowAnnotTypes it is possible to select by annotation type whether annotations are preserved as annotations, drawn into the page, or simply dropped.
The following options are useful for creating PDF 1. Some old viewers, such as Ghostscript 3. Setting this option to false, one can get more compatibility, but the mask interpolation is lost. Default value is false. If the clipping path exceeds the specified size, the masked image and the clipping path is decomposed into smaller images. The value of the option counts straight path segments curved segments are not used for representing a mask.
View code. OfficeToPDF - what does it do? There are some technical requirements that must be met before you can use it:. Supported File Types The following file types can be converted: Word. Instructions In order to use the tool, download the officetopdf. Microsoft Windows [Version 6.
All rights reserved. Feb 26, Packages 0 No packages published. You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Ask a Question. Please Sign up or sign in to vote. See more: C. Thanx IN Advance. Posted 6-Mar pm andy -RKO. Add a Solution. Sergey Alexandrovich Kryukov 8-Mar pm. Is it programming question or not? If not, this is off-topic. If programming, you should specify your platform, preferred language and other detail.
Net Language.. Accept Solution Reject Solution. Posted 8-Mar pm Aniket Yadav. Add your solution here. OK Paste as.
0コメント