Name: print/cups/filter/foomatic-db-engine Summary: Foomatic Database Engine Publisher: solaris Version: 4.0.14.20240820 Build Release: 11.4 Branch: 11.4.81.0.0.193.0 Packaging Date: Fri Mar 21 23:02:41 2025 Size: 1.02 MB Compressed Size: 328.23 kB FMRI: pkg://solaris/print/cups/filter/foomatic-db-engine@4.0.14.20240820,11.4-11.4.81.0.0.193.0:20250321T230241Z License: ## Files: COPYING GNU GENERAL PUBLIC LICENSE Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc. 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your programs, too. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things. To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it. For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software. Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations. Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you". Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does. 1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program. You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee. 2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions: a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change. b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License. c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.) These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program. In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License. 3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following: a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.) The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable. If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code. 4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance. 5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it. 6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License. 7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program. If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances. It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice. This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License. 8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License. 9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation. 10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. END OF TERMS AND CONDITIONS How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. Copyright (C) This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA Also add information on how to contact you by electronic and paper mail. If the program is interactive, make it output a short notice like this when it starts in an interactive mode: Gnomovision version 69, Copyright (C) year name of author Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details. The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than `show w' and `show c'; they could even be mouse-clicks or menu items--whatever suits your program. You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample; alter the names: Yoyodyne, Inc., hereby disclaims all copyright interest in the program `Gnomovision' (which makes passes at compilers) written by James Hacker. , 1 April 1989 Ty Coon, President of Vice This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Library General Public License instead of this License. ## Files: README Foomatic 4.0.13 =============== foomatic-db-engine ------------------ Foomatic's database engine generates PPD files from the data in Foomatic's XML database. It also contains scripts to directly generate print queues and handle jobs. Till Kamppeter Lars Uebernickel http://www.openprinting.org/ This README contains mainly info for developers. See the file USAGE if you want to know how to use Foomatic. Copying ------- This package and also the other Foomatic packages needed to run this are under the GPL. See http://www.gnu.org/. Bugs ---- If you spot a data error or any other bug, please report it on the OpenPrinting bug tracking system: http://bugs.linux-foundation.org/ Choose "OpenPrinting" as the product and "foomatic-db-engine" as the component. Intro ----- This is the stable version of Foomatic. This version is also the base of our database web interface on http://www.openprinting.org/ New features for Foomatic 4.0.x ------------------------------- Added in 4.0.0: - Support for the PDF-based printing workflow. foomatic-rip now understands both PostScript and PDF as input. PPDs are generated with two "*cupsFilter" lines now, so that CUPS knows that also PDF can get fed in. By the cost factors PDF is made the preferred input format. - foomatic-rip is rewritten in C, so that libraries can be used without needing Perl bindings. - Support for CUPS custom options. If a printer/driver combo has numerical, string, or password options, appropriate keywords are added to the PPD so that these options are also recognized as CUPS custom options (see http://www.cups.org/documentation.php/doc-1.4/spec-ppd.html for the CUPS PPD extension for custom options). - PJL/JCL options in PPD files are now generated in the standard way as defined by the PPD specs. Foomatic keywords are only used if really necessary. - Generated PPDs have now an additional "*cupsFilter:" line to tell CUPS that foomatic-rip understands PDF input (output of the "pdftopdf" CUPS filter). - Driver XML files can now have a new "" tag in the "" section, to supply a different command line prototype for PDF input. If left out, the same command line prototype is used for both PDF and PostScript input. - Margins in generated PPDs now default to safer values and not to zero if no margins are specified in the XML files. - CUPS page accounting can be suppressed on a per-driver basis now, via the tag "" and the PPD keyword "*FoomaticRIPNoPageAccounting: True". - Added new "foomatic-ppd-to-xml" utility to generate Foomatic XML files corresponding to a given PPD file. - Printer/driver relations now can be defined by the "" section in the driver XML file or by the "" section in the printer XML file. Before, only the former was possible. - Added find_printer() method, to search for printers in the database. This method is especially used by the web query API for automatic driver/PPD downloads from the OpenPrinting web site. It can also be used in a local installation with the new "foomatic-searchprinter" utility. - Added support for more detailed driver information, like license, whether it is free, whether it comes from the printer's manufacturer, support contacts, short description, by-task ratings. This gives more information to decide on downloading and installing a driver for both driver auto download and browsing the OpenPrinting web site. The information can also be used by printer setup tools using a locally installed Foomatic database. The information is available in the driver XML files (there one enters it), the PPD files, and also in the device ID strings, defined in the PPDs (so that the information goes into the output of "lpinfo -l -m" of CUPS). New features for Foomatic 3.0.x ------------------------------- Added after 3.0.2: - Support for on-the-fly PPD generation by CUPS 1.2. Now all Foomatic PPDs appear in the model lists of the CUPS web interface without needing to pre-compile the PPDs. The PPDs get actually generated if one selects them for the new print queue to be set up. Added in 3.0.2: - Some fixes to make foomatic-rip more robust against weird input via the command line or environment variables are done. This solves the problem of an attacker being able to run arbitrary commands as "lp" (or however the spooler's special user is named) on the print server (Security Advisory CAN-2004-0801). - Workaround for PostScript generation bug in all OpenOffice.org 1.1.x versions. - Let the PPD generator use the manufacturer as defined in the Foomatic database and not the one from the IEEE-1284 auto-detection ID string for the "*Manufacturer: ..." tag of the PPD files, as in the IDs the manufacturer names often do not comply with the Adobe specs (as "Hewlett-Packard", "HP" has to be used). Added in 3.0.1: - CUPS raster drivers can now be used with any spooler. This makes a lot of newer commercial or manufacturer-supplied printer drivers available for non-CUPS environments. To use a CUPS raster driver with a spooler other than CUPS, you need to install Ghostscript (preferrably ESP Ghostscript) with CUPS raster support, the appropriate CUPS raster driver. You do not need to install the complete CUPS package, the CUPS libraries are enough (libcups and libcupsimage, usually in the "libcups" package of your distribution) and to compile CUPS raster drivers you need also the header files of the CUPS library (libcups-devel, cupsys-dev, or similar package of your distro). Then you can set up a print queue with the PPD file of the CUPS driver the same way as if you had a native PostScript printer. - If a printer/driver combo has Foomatic-defined JCL options and the driver already generates a JCL header, the JCL options are merged into the header produced by the driver. - Workaround for newly introduced PostScript generation bug of OpenOffice.org 1.1.0 (OOo puts settings for whole document into "%%PageSetup" section of first page). - Added "use strict;" to the most important Perl scripts, clean-up of the scripts (Thanks to Patrick Powell from LPRng) - Improved LPRng support (Thanks to Patrick Powell from LPRng) - Printer listing options and auto-selection of recommended driver for the PPD generator foomatic-ppdfile (Thanks to Patrick Powell from LPRng). - Support for string options and additional operation modes for foomatic-addpjloptions (Thanks to Patrick Powell from LPRng). - Additional checks in the configure scripts (Thanks to Patrick Powell from LPRng). - Composite options can be nested now (normal and forced composite options can be mixed). - Several modifications to make the PPD files compatible with the PostScript drivers for Windows: 100 instead of 999 choices for the "Copies" options, no "," and "+" in the "*NickName" and "*ShortNickName" entries, optional cutting of the long names of the options and choices (translation strings in the PPDs) to 39 characters for compatibility with the Microsoft PostScript driver and the original PostScript driver for Windows of CUPS. All this is not required by the Adobe specification for PPD files. - Compatibility fixes for IRIX and the *BSD operating systems. - Script to update the "gutenprint" driver entry in the database using the src/foomatic/foomatic-printermap file of the source tarball of Gutenprint 5.0.x. - perltoxml() Perl function in DB.pm to generate XML database entries from PPD files (thanks to Tim Waugh from Red Hat). - Let foomatic-ppdfile (which can be also called under the name "foomatic-datafile", for compatibility with frontends) accept and ignore the "-t" option for backwards compatibility. Now the KDE Printing Manager works correctly again. - Fixed PPD file generation so that the files pass the "cupstestppd" of CUPS 1.1.20. Added in 3.0.0: - For all supported spoolers (CUPS, LPRng, LPD, GNUlpr, PPR, PDQ, CPS, no spooler) the same PostScript-to-printer's-native-language filter (RIP, Raster Image Processor), foomatic-rip is used. foomatic-rip detects automatically from which spooler it is called. - foomatic-rip gets the info about the printer's capabilities and the driver options and default settings always from PPD files, independent which spooler is used. It is possible to use Foomatic-generated PPD files (usually for non-PostScript printers) or manufacturer- supplied PPD files of PostScript printers. So o PPD files of PostScript printers can be used with every spooler, not only with CUPS and PPR and on all spoolers all options will be available. So PostScript printers work always "Perfectly". o With the PPD file one has one configuration file for every place where information about the printer and its options is needed: The print queue itself, PPD-aware applications (as Star Office, OpenOffice.org, GIMP, ...), and clients (Windows, Mac, Unix with arbitrary spooler). The PPD format is a standard format used by every modern operating system. - PPD building and PostScript processing is done according to the Adobe specifications DSC (Document Structuring Conventions) and PPD (PostScript Printer Description) as published on http://partners.adobe.com/public/developer/ps/index_specs.html - foomatic-rip inserts all default settings from the PPD file (so you can edit the "*Default..." lines in the PPD files to set the defaults), reads option settings from the user's command line, and from the PostScript data stream. Settings in the PostScript data stream have the highest priority to assure that what one sets in an application is used. Depending on the option type the settings are applied to the renderer's (usually Ghostscript's) command line, to the JCL header, or stuffed in at the right place of the PostScript data stream. - Support for option settings only acting on a certain page selection (example: First page on letterhead paper from tray 1, rest on plain paper from tray 2). Settings must be put into the "%%BeginPageSetup"/ "%%EndPageSetup" sections (or at least right after the "%%Page:" comments) of the appropriate pages in the PostScript input file. They can also be specified on the command line by specifying a page range before the option name (ex: "lpr -o 1,5-8:ColorMode=CMYK file.ps"). If necessary, the renderer (usually Ghostscript) is stopped and restarted in the middle of the job, when certain pages need a different command line for the renderer. The bug of Star Office/OpenOffice.org inserting the "%%BeginSetup...%%EndSetup" section after the first "%%Page:" comment is taken care of. - foomatic-rip does neither use temporary files on the disk, nor does it need to load huge documents completely into memory. All is done in data streams where not more data than necessary is buffered. To make this possible foomatic-rip forks into up to six sub-processes. - The installation is very easy, one needs only foomatic-rip (absolutely monolithic, no Perl modules needed), a PPD file, and optionally foomatic-gswrapper. No different files for different spoolers. - Custom page size support with all spoolers when the PPD file has Adobe-compliant definitions for usage of custom page sizes. - The spooler-less printing mode of foomatic-rip can be used for testing and debugging PPD files in arbitrary directories, one simply specifies them with the new "--ppd" option. - With PDQ one can print arbitrary file types now, and even set up raw printers. The PDQ driver files are generated by foomatic-rip, so the user does not need to download more files than with other spoolers. - Under PPR 1.50 and newer foomatic-rip runs as a PPR RIP, under older versions, as before, as a PPR interface. - foomatic-configure sets up printer queues based on Foomatic database entries, arbitrary third-party PPDs (as shipped with PostScript printers), or raw queues. - foomatic-configure is much faster when copying or modifying print queues now, as it does not rebuild the PPD from the Foomatic database all the time (as long as one does not force a rebuild with "-f"). - foomatic-addpjloptions works also in regular installations now, not only in "inplace" installations. - foomatic-compiledb generates only PPD and XML files now. - foomatic-datafile is renamed to foomatic-ppdfile, a compatibility link named foomatic-datafile is set. foomatic-ppdfile generates only PPDs, the options "-t" and "-f" are ignored. - foomatic-configure, foomatic-printjob, and all the other scripts have the same command lines as in Foomatic 2.0. Exceptions: In foomatic-configure "--oldppd" was dropped, "--ppd" (for setting up a queue with a third-party PPD file) added, and the meaning of "-f" (force rebuild of PPD) changed. - Option groups: Options can be put into groups and subgroups in the PPD files, so that GUIs can present them in a structured way (in tabs or in a tree structure). It is nearly completely functional, the only thing missing is translation support ("long names" for the groups, as "Adjustments and Corrections" for "Adjustment", or translations to other languages). Now the PPD generator makes trivial translations ("ThisIsAGroup" -> "This Is A Group") automatically. - Composite options: This is a new option type to make it easier for users to choose the best settings for a certain printing task, especially if the driver has very many options. The idea is to have an enumerated choice option which does not directly modify something in the driver's command line but sets several of the other options. We will have a "Printout Mode" option for all printers with the following choices: Draft Normal High Quality Very High Quality Photo For an Epson Stylus Color 680 with Gutenprint it sets the options resolution, dithering, and image type as follows: Choice Resolution Dither ImageType ------------------------------------------------------------------ Draft 180x180 dpi Very Fast LineArt Normal 360x360 dpi Adaptive Hybrid Photographs High Quality 720x720 dpi Adaptive Hybrid Photographs Very High Qual. 1440x720 dpi Adaptive Hybrid Photographs Photo 2880x720 dpi Even Tone Photographs The mentioned settings set all the color mode to "Color", there are also choices with a ".Gray" modifier (ex: "Normal.Gray" which set the color mode to "Grayscale", but the other mentioned options as the standard variants ("Normal"). The member options of the composite option all get one choice called "FromPrintoutMode"/"Controlled by 'Printout Mode'" added, which gets their default setting. If this choice is selected, the option is set by the composite option according to the table. If the user wants to modify one of the individual member options, he simply chooses a value other than "FromPrintoutMode" for this particular option. In addition the member options will be put into a group (named "Printout Mode"). and the composite option goes into the same group as "PageSize", "InputSlot", ... So the user sees the composite option on the "Front page" of the GUI and can quickly set up print jobs without getting confused. The user with more special demands goes to the tab with the member options and makes detailed choices. - Forced composite options: These are special composite options where the user cannot set the individual member options, but only the composite option (the user is forced to use the composite option). This allows options acting at two or more places, for example a "PageSize" option for a driver which is a filter translating Ghostscript bitmap output to the printer's language. One lets one member option be an option inserting PostScript code for the page size into the PostScript input data stream for Ghostscript, and another member option insert the correct bitmap size into the filter's command line. The user sees only the composite option and sets the paper size with it as usual. - String and password options: These options allow the user to supply nearly arbitrary strings (a length limit and restrictions be a list of allowed characters or a Perl regular expression can be set) to the printer driver, for example names of color calibration files, fax numbers, passwords for confidential jobs, ... Frequently needed strings can be added as enumerated choices, so a frontend can show the option as a combo-box. The enumerated choices are also used for frontends which only support options as defined by the PPD spec. - New handling of numerical options in the PPD files: "*Default