1 # Buildsheet autogenerated by ravenadm tool -- Do not edit.
3 NAMEBASE= xorg-xorgproto
8 SDESC[standard]= Combined X.Org X11 Protocol headers
9 HOMEPAGE= https://www.x.org/
13 SITES[main]= XORG/individual/proto
14 DISTFILE[1]= xorgproto-2018.4.tar.bz2:main
17 SPKGS[standard]= single
19 OPTIONS_AVAILABLE= none
20 OPTIONS_STANDARD= none
22 DISTNAME= xorgproto-2018.4
25 LICENSE_FILE= MIT:{{WRKDIR}}/LICENSE_MIT
28 FPC_EQUIVALENT= x11/xorgproto
31 CONFIGURE_ARGS= --datarootdir={{PREFIX}}/lib
33 CONFIGURE_ENV= MISC_MAN_SUFFIX=7
37 ${HEAD} -n 300 COPYING-* > ${WRKDIR}/LICENSE_MIT)
40 ${RM} -r ${STAGEDIR}${PREFIX}/lib/doc
42 [FILE:100:descriptions/desc.single]
43 This package combines the X protocol headers, which were formerly
44 scattered in individual packages.
48 fee885e0512899ea5280c593fdb2735beb1693ad170c22ebcc844470eec415a0 390293 xorg/xorgproto-2018.4.tar.bz2
51 [FILE:2663:manifests/plist.single]
57 include/GL/internal/glcore.h
92 include/X11/extensions/
251 share/man/man7/Xprint.7.gz
254 [FILE:16443:patches/patch-man_Xprint.man]
255 --- man/Xprint.man.orig 2018-07-24 10:46:56 UTC
258 +.\" -*- coding: us-ascii -*-
259 +.TH Xprint __miscmansuffix__ "8 October 2004"
261 +Xprint \- The "X print service" - a portable, network-transparent printing system based on the X11 protocol
263 +Xprint is a very flexible, extensible, scaleable, client/server
264 +print system based on ISO 10175 (and some other specs) and the X11
266 +Using Xprint an application can search, query and use devices like
267 +printers, FAX machines or create documents in formats like PDF.
268 +In particular, an application can seek a printer, query supported
269 +attributes (like paper size, trays, fonts etc.), configure the printer
270 +device to match it\(cqs needs and print on it like on any other X device
271 +reusing parts of the code which is used for the video card Xserver.
273 +The "X Print Service" technology allows X rendering to devices such as
274 +printers and fax. Most of the service is available in the X11
275 +technology stack as Xp, with the remainder in single toolkit stacks (e.g. DtPrint for CDE).
276 +Modifications have also been made to the LessTif/Motif/Qt technology
277 +stacks to support Xprint.
279 +The Xp portion consists of:
282 +Xp Extension for the X-Server (included in the X-Server Xprt)
285 +Xp Extension API for the client side (libXp/libXprintUtils)
288 +PCL ddx driver that converts core X to native PCL
291 +PDF ddx driver that converts core X to native PDF
294 +PostScript ddx driver that converts core X to native PostScript
297 +Raster ddx driver that generates xwd rasters which can be converted to PCL, PDF or PostScript rasters
300 +From an X clients perspective, it can attach to one of two nearly
301 +identical X-Servers, a "Video" X-Server, and a "Print" X-Server
302 +which has the additional Xp capability but otherwise looks and
304 +.SH "HOW THE X PRINT SERVICE WORKS"
305 +The X Print Service expands on the traditional X-Server and Xlib world
309 +Most obvious is the use of "print ddx drivers" instead of
310 +"video ddx drivers". While a video ddx driver modifies pixels
311 +in a video frame buffer, a print ddx driver generates "page
312 +description language (PDL)" output (such as PCL, PDF or PostScript)
313 +or sends the print rendering instructions to a platform-specific
314 +print API (like Win32/GDI).
316 +Once a print ddx driver generates PDL output, it can be sent to
317 +a spooler such as \fBlp\fR(1)
318 +or retrieved by the client (to implement functionality like "print-to-file").
320 +Though not currently done, a single X-Server can support both
321 +print and video ddx drivers.
324 +Since printers support "paged" output, unlike video, a portion
325 +of the Xp Extension supports APIs to delineate printed output.
326 +For example, XpStartPage and XpEndPage tell the X-Server where
327 +a physical page starts and ends in an otherwise continuous
328 +stream of X rendering primitives. Likewise, XpStartJob and
329 +XpEndJob determine when a collection of pages starts and ends.
330 +XpEndJob typically causes the generated PDL to be submitted to
331 +a spooler, such as \fBlp\fR(1).
334 +Since printers have extensive capabilities, another portion of
335 +the Xp Extension supports APIs to manipulate "print contexts".
337 +Once a printer is selected using the Xp Extension API, a print
338 +context to represent it can be created. A print context
339 +embodies the printer selected - it contains the printer's
340 +default capabilities, selectable range of capabilities,
341 +printer state, and generated output. Some "attributes" within
342 +the print context can be modified by the user, and the
343 +X-Server and print ddx driver will react accordingly. For
344 +example, the attribute "content-orientation" can be set to
345 +"landscape" or "portrait" (if the printer supports these
346 +values - which can be queried using the Xprint API as well).
349 +Since printers can have "built in" fonts, the Xp Extension in
350 +the X-Server works with the print ddx drivers to make
351 +available (for printing only) additional fonts on a per print
354 +When a print context is created and set for a given printer,
355 +the X font calls may be able to access additional printer
356 +fonts. To do this (typically), the X-Server must have access
357 +to "printer metric files" (.pmf) that describe at minimum the
358 +metrics of the built in fonts.
361 +There are three tasks to start the X Print Service:
364 +configuring the X Print Server,
367 +starting the X Print Service
370 +configuring the user session so that clients can find the running X Print Service
373 +The tasks are described in detail below.
374 +.SH "SERVER CONFIGURATION"
375 +The X Print Server (Xprt) can read a number of configuration files which
376 +control its behavior and support for printers. Each vendor platform has
377 +a default location for this information. Xprt can also read the
378 +environment variable \fBXPCONFIGDIR\fR to locate alternate configuration
379 +directories. Common settings include:
381 +export XPCONFIGDIR=/X11/lib/X11/XpConfig/
383 +export XPCONFIGDIR=/proj/x11/xc/programs/Xserver/XpConfig/
386 +Xprt has many built-in defaults, and lacking any configuration files,
387 +will immediately try to support all printers visible via \fBlpstat\fR(1).
389 +In order of importance for configuration by a system administrator, the
390 +configuration files for a "C" locale are as follows (see \fBXprt\fR(__appmansuffix__) for more
391 +details (including support for non-"C" locales)):
393 +\fB${XPCONFIGDIR}/C/print/Xprinters\fR
394 +\&'Xprinters' is the top most configuration file. It tells
395 +Xprt which specific printer names (e.g. mylaser) should
396 +be supported, and whether \fBlpstat\fR(1) or other commands
397 +should be used to automatically supplement the list of
400 +\fB${XPCONFIGDIR}/C/print/attributes/printer\fR
401 +The 'printer' file maps printer names to model
402 +configurations (see 'model-config' below). For example,
403 +"mylaser" could be mapped to a "HPDJ1600C", and all other
404 +arbitrary printers could be mapped to a default, such as
405 +"HPLJ4SI". When depending on \fBlpstat\fR(1) in the Xprinters
406 +file, setting up defaults in 'printer' becomes all the
409 +\fB${XPCONFIGDIR}/C/print/attributes/document\fR
410 +The 'document' file specifies the initial document values
411 +for any print jobs. For example, which paper tray to
412 +use, what default resolution, etc.
414 +\fB${XPCONFIGDIR}/C/print/attributes/job\fR
415 +The 'job' file specifies the initial job values for any
416 +print jobs. For example, "notification-profile" can be
417 +set so that when a print job is successfully sent to a
418 +printer, e-mail is sent to the user.
420 +\fB${XPCONFIGDIR}/C/print/models/PSdefault/model\-config\fR, \fB${XPCONFIGDIR}/C/print/models/PSdefault/fonts/fonts.dir\fR, \fB${XPCONFIGDIR}/C/print/models/PSdefault/fonts/9nb00051.pmf\fR, \fB${XPCONFIGDIR}/C/print/models/PSdefault/fonts/9nb00093.pmf\fR
421 +The 'model-config' file has attributes that describe the
422 +printer model\(cqs capabilities and default settings.
423 +Printer model fonts may also be present. The model-config
424 +file also identifies the print ddx driver to be used.
425 +For each printer model supported, a complete hierarchy of
426 +files should exist. In most cases, these files do not
427 +need to be modified.
429 +\fB${XPCONFIGDIR}/C/print/ddx\-config/raster/pcl\fR, \fB${XPCONFIGDIR}/C/print/ddx\-config/raster/pdf\fR, \fB${XPCONFIGDIR}/C/print/ddx\-config/raster/postscript\fR
430 +The print ddx drivers can have highly specific
431 +configuration files to control their behavior. In most
432 +cases, these files do not need to be modified.
434 +More information in how to configure and customize the X print server can be found in the
435 +\fBXprt\fR(__appmansuffix__)
438 +The summary checklist for starting the X Print Service is as follows:
441 +Choose an execution model for the X Print Service. The X
442 +Print Service can be run on a per-user session basis, per
443 +machine basis, or can be run on a few machines globally
444 +available to a number of users.
447 +If print jobs are to be submitted to a spooler (almost always
448 +the case), make sure all needed printers are available to the
449 +spooler subsystem (most often \fBlp\fR(1))
450 +on the same machine running the X Print Service.
453 +Configure the X Print Server. See ``X Print Server
457 +Depending on #1, start the X Print Server process "Xprt", and
458 +then the toolkit-specific Print Dialog Manager Daemon process
459 +(such as CDEnext's "dtpdmd") at the appropriate times.
460 +Note that libXprintUtils-based applications/toolkits do not need
461 +a Print Dialog Manager Daemon process to use Xprint.
463 +The details are described below.
465 +Because the X Print Service is based on X, it can be easily distributed.
466 +The most significant factors in which execution model to choose will be
470 +how many printers will be accessable through the printer
471 +subsystem on any given machine. A system administrator may
472 +choose to cluster printers on a few given machines, or
473 +scatter them across an organization and possibly make
474 +extensive use of remote spoolers to make them globally
478 +how many machines will need a copy of the X Print Server
479 +configuration files. The files have been architected so
480 +that one super-set version of them can be maintained and
481 +distributed (e.g. via NFS), and a per-machine or per-user
482 +version of the `Xprinters' is all that is needed to have the
483 +appropriate information in them utilized or ignored.
486 +how many users can demand services from a given X Print
489 +With the above in mind, some obvious execution models include:
492 +Global - in this model, the system administrator is choosing
493 +to run the X Print Service on a *few* select machines with
494 +appropriate printers configured, and allow clients access to
495 +the global resource. This can centralize the administration
496 +of printers and configuration files, but may have to be
497 +monitored for performance loading.
499 +Startup would likely be done by boot-up scripts (such as \fB/etc/init.d/xprint\fR).
502 +Per-machine - every machine with potential X Print Service
503 +users would run the service. Printer and configuration file
504 +administration is decentralized, and usage would be limited
505 +to the users on the machine.
507 +Startup would likely be done by boot-up scripts (such as \fB/etc/init.d/xprint\fR).
510 +Per-user session - every user would run an entire X Print
511 +Service for themselves. In the future, the Video X Server
512 +normally started may contain Print X Server capability, so
513 +this model becomes very natural.
515 +Startup would likely be done at session login or by
516 +launching actions or processes manually once the user
517 +logs in. Note: Deamons like "dtpdmd" must be started after Xprt.
520 +Starting of the processes is straight forward. In strict order (example is for manually starting the X print server for CDEnext usage):
525 +[machineA] % Xprt [\-XpFile <Xprinters file>] [:dispNum] &
529 +Note that Xprt will look for configuration files in either
530 +a default location or where \fBXPCONFIGDIR\fR points.
532 +\fB\-XpFile\fR specifies an alternate `Xprinters' file, rather
533 +than the default one or `\fB${XPCONFIGDIR}/C/print/Xprinters\fR'.
538 +[machineA] % dtpdmd \-d machineA[:dispNum] [\-l /tmp/dtpdmd.log] &
542 +The dtpdmd will maintain an X-Selection on the X-Server,
543 +and will start dtpdm's as required to service requests.
546 +In all but the per-user session model, the machine running the dtpdmd
547 +(thus dtpdm's) will need display authorization to the users video
549 +.SH "CLIENT CONFIGURATION"
550 +Once a X Print Server and dtpdmd have been started -- many of them
551 +in some cases -- clients will need to find and use them. There are
552 +two mechanisms that allow clients to discover X Print Servers and
556 +"X Print Specifier" - assuming usage of the DtPrint/XprintUtils-based print
557 +applications, the following notation is understood:
561 +printer_name@machine[:dispNum]
573 +In the above example, the X Print Server running at `printhub:2'
574 +is assumed to support the printer named `colorlj7'.
577 +\fB${XPSERVERLIST}\fR - assuming usage of the DtPrint print dialogs,
578 +the environment variable \fB${XPSERVERLIST}\fR can contain a list
579 +of X Print Servers. For example:
583 +XPSERVERLIST="printhub:2 printhub:3 otherdept:0"
587 +Then in the dialogs, only a printer name needs to be entered.
588 +The dialog will then search the X Print Servers in \fB${XPSERVERLIST}\fR
589 +for a server than supports the printer, and then establish
592 +.SH "END-USER SEQUENCE"
593 +From most CDEnext applications, printing is accomplished by bringing
594 +down the <File> menu and selecting <Print...>. This will result in
595 +the DtPrintSetupBox dialog, which will request the name of a printer,
596 +and offer limited capability to configure print options (e.g. number
597 +of copies). If the user wishes, they can select <Setup...>, which
598 +will start a dtpdm capable of modifying additional print options.
599 +Finally, the user should select <Print>.
602 +\fB${XPCONFIGDIR}\fR
603 +This environment variable points to the root
604 +of the Xprint server configuration directory hierarchy.
605 +If the variable is not defined, the default
606 +path is be assumed. The default path may be
607 +\fB/usr/X11R6/lib/X11/xserver/\fR,
608 +\fB/usr/lib/X11/xserver/\fR,
609 +\fB/usr/share/Xprint/xserver/\fR or
610 +\fB/usr/openwin/server/etc/XpConfig\fR, depending on the
611 +system, and may be configured in \fB/etc/init.d/xprint\fR.
614 +This environment variable selects the locale settings used by the Xprint server.
615 +Xprt allows language-specific settings (stored in \fB${XPCONFIGDIR}/${LANG}/print/\fR)
616 +which will override the default settings (stored in \fB${XPCONFIGDIR}/C/print/\fR).
617 +If \fB${LANG}\fR is not set "C" is assumed.
619 +\fB${XPSERVERLIST}\fR
620 +The environment variable \fB${XPSERVERLIST}\fR contains a list
621 +of display identifiers (separated by whitespace) which tell an
622 +application where it can find the Xprint servers. Usually
623 +\fB${XPSERVERLIST}\fR is set by the profile startup scripts (e.g.
624 +\fB/etc/profile\fR or \fB/etc/profile.d/xprint.sh\fR) using the output of
625 +\fB/etc/init.d/xprint get_xpserverlist\fR.
631 + export XPSERVERLIST="`/etc/init.d/xprint get_xpserverlist`"
635 +Alternatively \fB${XPSERVERLIST}\fR can be set
640 + export XPSERVERLIST="littlecat:80 bitdog:72"
643 +instructs an application to find an Xprint server at display
644 +80 on the machine "littlecat" and at display 72 on the
648 +The environment variable \fB${XPRINTER}\fR
649 +defines the default printer used by print
650 +applications. The syntax is either
651 +\fIprintername\fR or
652 +\fIprintername\fR@\fIdisplay\fR.
657 +\fBXPRINTER=ps003\fR
658 +tells an application to look for the
659 +first printer named "ps003" on all Xprint
662 +\fBXPRINTER=hplaser19@littlecat:80\fR
663 +tells an application to use the printer "hplaser19"
664 +on the Xprint server at display
669 +If \fB${XPRINTER}\fR is not set the applications
670 +will examine the values of the \fB${PDPRINTER}\fR,
671 +\fB${LPDEST}\fR, and
672 +\fB${PRINTER}\fR environment variables (in that order).
674 +\fBX11\fR(__miscmansuffix__), \fBxplsprinters\fR(__appmansuffix__), \fBxprehashprinterlist\fR(__appmansuffix__), \fBxphelloworld\fR(__appmansuffix__), \fBxpxmhelloworld\fR(__appmansuffix__), \fBxpawhelloworld\fR(__appmansuffix__), \fBxpxthelloworld\fR(__appmansuffix__), \fBxpsimplehelloworld\fR(__appmansuffix__), \fBXserver\fR(__appmansuffix__), \fBXprt\fR(__appmansuffix__), \fBlibXp\fR(__libmansuffix__), \fBlibXprintUtils\fR(__libmansuffix__), \fBlibXprintAppUtils\fR(__libmansuffix__), \fBXmPrintShell\fR(__libmansuffix__), \fBXawPrintShell\fR(__libmansuffix__), Xprint FAQ (http://xprint.mozdev.org/docs/Xprint_FAQ.html), Xprint main site (http://xprint.mozdev.org/)
676 +This manual page was written by
677 +Roland Mainz <roland.mainz@nrubsig.org> based on the original X11R6.6
678 +\fBxc/programs/Xserver/XpConfig/README\fR.
projects / ravenports.git / blob