<br><font size=2 face="sans-serif">Johannes,</font>
<br>
<br><font size=2 face="sans-serif">sounds like a plan already!</font>
<br><font size=2 face="sans-serif"><br>
Regards<br>
Uli Wehner<br>
Solutions Engineer<br>
(770) 493 2324</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Johannes Meixner <jsmeix@suse.de></b>
</font>
<br><font size=1 face="sans-serif">Sent by: desktop_printing-bounces@lists.osdl.org</font>
<p><font size=1 face="sans-serif">04/04/2006 02:37</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">desktop_printing@lists.osdl.org</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Re: [Fwd: Re: [Fwd: Re: AW: [Desktop_printing]
Role of CUPS and error handling]]</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt><br>
Hello,<br>
<br>
On Apr 3 10:15 Michael Sweet wrote (shortened):<br>
> Johannes Meixner wrote:<br>
> > What about "cups-config --version"?<br>
> Only available if the user has installed the corresponding<br>
> -devel package (at least on Linux)<br>
<br>
Because of a manufacturer driver which installs into wrong<br>
directories on 64-bit platform (AMD 64) we moved cups-config<br>
to the base CUPS library package (for Suse Linux 10.1).<br>
<br>
(I know that there is a discussion what the right directories<br>
are for 64-bit platforms but regardless of this topic,<br>
cups-config shows the right directory even if it is a<br>
non-standard directory.)<br>
<br>
<br>
> > > 3. It requires each vendor to develop their own setup<br>
> > > applications,<br>
> > <br>
> > Yes, this is a crucial point of the idea.<br>
> > But I didn't mean a big-and-fat arbitrary-printer setup application.<br>
> > I have something like a bash-script in mind.<br>
> > Only the manufacturer knows what exactly he needs to set up<br>
> > his one particular printer model.<br>
> > With this knowledge he can make a setup script which tests all<br>
> > what is needed and therefoere which will not show any user dialog<br>
> > except for fatal error messages after which the tool must exit.<br>
> > Then only a very generic message-popup with an [ok] button<br>
> > (e.g. "xmessage" if X is running) is sufficient.<br>
> <br>
> A script would be good, but I'd still like to give the manufacturers<br>
> something standard to work with (e.g. template or script that can<br>
> adapt based on files/configuration info) to make is easier and less<br>
> error prone.<br>
<br>
After we finally got the next Suse Linux version finished,<br>
I will make such a script as a simple first thing to start with<br>
based upon the Suse distribution.<br>
<br>
I will make it public available and then together with the CUPS<br>
people, the other distributors and the manufacturers we can<br>
enhance it step by step to get finally script which could<br>
(hopefully) work for any manufacturer and for any distributor<br>
and for any printing software project (e.g. Gutenprint).<br>
<br>
Furthermore:<br>
During this process we will detect many litte obstacles<br>
which lead to the known annoyance for the end-users and<br>
when we solve them step by step, we can get a common standard<br>
how to set up a printer which is not just a nice wish of a<br>
usability-expert but something which is tested that it works.<br>
<br>
<br>
Kind Regards<br>
Johannes Meixner<br>
-- <br>
SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix@suse.de<br>
90409 Nuernberg, Germany
WWW: http://www.suse.de/<br>
_______________________________________________<br>
Desktop_printing mailing list<br>
Desktop_printing@lists.osdl.org<br>
https://lists.osdl.org/mailman/listinfo/desktop_printing<br>
</tt></font>
<br>