#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: cups 1.4b2\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2009-01-10 21:21-0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Translate Toolkit 1.2.1\n"

#: ./spec-postscript.html:1
msgid "Generating PostScript for CUPS"
msgstr ""

#: ./spec-postscript.html:2
msgid "Programming, PostScript, Document Structuring Conventions"
msgstr ""

#: ./spec-postscript.html:3
msgid "Introduction"
msgstr ""

#: ./spec-postscript.html:4
msgid ""
"This document describes how to generate PostScript output for CUPS and is "
"largely based on the <a "
"href=\"http://partners.adobe.com/public/developer/en/ps/5001.DSC_Spec.pdf\"> "
"Adobe TechNote #5001: PostScript Language Document Structuring Conventions "
"Specification Version 3.0</a>. While CUPS can generally print any PostScript "
"file, following the rules in the Adobe TechNote and this document will "
"ensure that your PostScript output will work reliably."
msgstr ""

#: ./spec-postscript.html:5
msgid "Anatomy of a PostScript File"
msgstr ""

#: ./spec-postscript.html:6
msgid ""
"PostScript files are ASCII text files starting with a header line (<tt>%!PS-"
"Adobe-3.0</tt>) followed by a combination of comment lines starting with the "
"percent sign (<tt>%</tt>) and PostScript code lines. The lines themselves "
"should not exceed 255 characters to conform to the DSC. The following short "
"PostScript file produces a box with a smiley face in it:"
msgstr ""

#: ./spec-postscript.html:7
msgctxt "./spec-postscript.html:7"
msgid "Sample PostScript File Output"
msgstr ""

#: ./spec-postscript.html:8
msgid "Figure 1: <a name=\"FIGURE_1\">Sample PostScript File Output</a>"
msgstr ""

#: ./spec-postscript.html:9
msgctxt "./spec-postscript.html:9"
msgid "Sample PostScript File Output"
msgstr ""

#: ./spec-postscript.html:10
msgid "Embedding Printer Options"
msgstr ""

#: ./spec-postscript.html:11
msgid ""
"There are two main strategies for embedding printer options in PostScript "
"files. The first is to list CUPS options using the "
"<code>%cupsJobTicket</code> comment:"
msgstr ""

#: ./spec-postscript.html:12
msgid ""
"CUPS options apply to the entire job. To apply options to individual pages, "
"use the <code>%%IncludeFeature</code> comment instead:"
msgstr ""

#: ./spec-postscript.html:13
msgid "Embedding Fonts and Text"
msgstr ""

#: ./spec-postscript.html:14
msgid ""
"Always embed the fonts used by your print job, and for best performance "
"embed the fonts and character encodings in the setup section of the "
"PostScript file. Type 1 and Type 3 fonts are supported by all PostScript "
"printers, while Type 42 (TrueType) and CID fonts are supported by most level "
"2 and all level 3 PostScript printers. Binary font files should always be "
"converted to the corresponding ASCII (hex) encoding to avoid problems when "
"printing over interfaces that do not support binary PostScript."
msgstr ""

#: ./spec-postscript.html:15
msgid "Embedding Images"
msgstr ""

#: ./spec-postscript.html:16
msgid ""
"The <code>image</code> operator should be used to embed images in PostScript "
"files. Always use ASCII hex or Base-85 encoding for the image data to avoid "
"problems when printing over interfaces that do not support binary "
"PostScript. In most cases, the Base-85 encoding and compression filters can "
"be used to embed images with very little, if any, increase in data size."
msgstr ""