public inbox for gentoo-doc-cvs@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Josh Saddler" <nightmorph@lark.gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] cvs commit: printing-howto.xml
Date: Tue, 28 Nov 2006 19:21:12 +0000	[thread overview]
Message-ID: <20061128192209.5DAF464971@smtp.gentoo.org> (raw)

nightmorph    06/11/28 19:21:12

  Modified:             printing-howto.xml
  Log:
  Lots o' printing-howto updates for the new stabilized CUPS 1.2, thanks to genstef for answering a few questions on IRC

Revision  Changes    Path
1.63                 xml/htdocs/doc/en/printing-howto.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/printing-howto.xml?rev=1.63&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/printing-howto.xml?rev=1.63&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/printing-howto.xml?r1=1.62&r2=1.63

Index: printing-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/printing-howto.xml,v
retrieving revision 1.62
retrieving revision 1.63
diff -u -r1.62 -r1.63
--- printing-howto.xml	28 Nov 2006 18:10:50 -0000	1.62
+++ printing-howto.xml	28 Nov 2006 19:21:12 -0000	1.63
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding="UTF-8"?>
 
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/printing-howto.xml,v 1.62 2006/11/28 18:10:50 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/printing-howto.xml,v 1.63 2006/11/28 19:21:12 nightmorph Exp $ -->
 
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
@@ -8,7 +8,7 @@
 <title>Gentoo Printing Guide</title>
 
 <author title="Author">
-  <mail link="swift@gentoo.org">Sven Vermeulen</mail>
+  <mail link="sven.vermeulen@siphos.be">Sven Vermeulen</mail>
 </author>
 <author title="Editor">
   <mail link="nightmorph@gentoo.org">Joshua Saddler</mail>
@@ -24,7 +24,7 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>2.94</version>
+<version>2.95</version>
 <date>2006-11-28</date>
 
 <chapter>
@@ -236,6 +236,14 @@
   <th>Impact on CUPS</th>
 </tr>
 <tr>
+  <ti>dbus</ti>
+  <ti>Adds support for the <c>dbus</c> system message bus.</ti>
+</tr>
+<tr>
+  <ti>jpeg</ti>
+  <ti>Adds support for printing JPEG images.</ti>
+</tr>
+<tr>
   <ti>nls</ti>
   <ti>
     Enable National Language Support. With nls in place, CUPS is able to deliver
@@ -251,6 +259,21 @@
   </ti>
 </tr>
 <tr>
+  <ti>php</ti>
+  <ti>Adds support for php scripting.</ti>
+</tr>
+<tr>
+  <ti>png</ti>
+  <ti>Adds support for printing PNG images.</ti>
+</tr>
+<tr>
+  <ti>ppds</ti>
+  <ti>
+    Adds support for automatically generated ppd (printing driver) files. See
+  <uri link="#installing_best">Installing the Best Driver</uri>.
+  </ti>
+</tr>
+<tr>
   <ti>samba</ti>
   <ti>
     If you want to be able to share locally attached printers to Windows systems
@@ -275,6 +298,17 @@
     SSL must be available on all participating systems in your network.
   </ti>
 </tr>
+<tr>
+  <ti>tiff</ti>
+  <ti>Adds support for printing TIFF images.</ti>
+</tr>
+<tr>
+  <ti>X</ti>
+  <ti>
+    Allows you to use your desktop menu to load the CUPS configuration webpage
+    into your preferred browser.
+  </ti>
+</tr>
 </table>
 
 <p>
@@ -285,10 +319,10 @@
 
 <pre caption="USE flag settings for CUPS">
 # <i>emerge -pv cups</i>
-[ebuild N     ] net-print/cups-1.1.23-r1  +nls +pam -samba -slp +ssl 0 kB
+[ebuild N     ] net-print/cups-1.2.6  "X dbus jpeg nls pam png ppds ssl -php -samba -slp -tiff" 0 kB
 
 <comment>(For instance, to enable SAMBA support for CUPS)</comment>
-# <i>vim /etc/portage/package.use</i>
+# <i>nano -w /etc/portage/package.use</i>
 net-print/cups samba
 </pre>
 
@@ -398,6 +432,15 @@
 </p>
 
 <pre caption="Port configuration in /etc/cups/cupsd.conf">
+Listen *:631
+</pre>
+
+<note>
+If you are still using CUPS 1.1 (which is now deprecated), then you will need to
+use a different syntax for remote printing requests:
+</note>
+
+<pre caption="Deprecated CUPS 1.1 configuration">
 Port 631
 <comment>(make sure the next two lines are commented out)</comment>
 #Listen 127.0.0.1:631
@@ -699,7 +742,7 @@
 
 </body>
 </section>
-<section>
+<section id="installing_best">
 <title>Installing the Best Driver</title>
 <body>
 



-- 
gentoo-doc-cvs@gentoo.org mailing list



             reply	other threads:[~2006-11-28 19:22 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-28 19:21 Josh Saddler [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-06-16  1:08 [gentoo-doc-cvs] cvs commit: printing-howto.xml Joshua Saddler
2008-05-07  0:29 Joshua Saddler
2008-05-03 16:00 Sven Vermeulen
2008-05-03 15:59 Sven Vermeulen
2008-02-20 21:07 Sven Vermeulen
2007-02-05 14:14 Xavier Neys
2007-02-02  8:10 Josh Saddler
2006-11-28 18:10 Josh Saddler
2006-09-14 11:21 Josh Saddler
2006-09-04  2:19 Josh Saddler
2006-09-04  1:50 Josh Saddler
2006-03-20 20:21 Josh Saddler
2006-03-19 17:29 Josh Saddler
2006-03-14 18:55 Josh Saddler
2006-03-11 16:21 swift
2006-03-05 10:29 swift
2005-11-21 15:44 Xavier Neys
2005-11-05 17:29 swift
2005-09-09 13:19 Jan Kundrat

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20061128192209.5DAF464971@smtp.gentoo.org \
    --to=nightmorph@lark.gentoo.org \
    --cc=docs-team@lists.gentoo.org \
    --cc=gentoo-doc-cvs@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox