9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Rodolfo =?unknown-8bit?Q?Garc=EDa?= <kix@kix.es>
To: weigelt@metux.de,
	Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Ideas for an printer filesystem
Date: Fri, 30 Nov 2007 14:06:31 +0100	[thread overview]
Message-ID: <20071130130631.GA4274@darkside> (raw)
In-Reply-To: <20071130123249.GB14203@nibiru.local>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=unknown-8bit, Size: 1822 bytes --]

"Probably" you need three files:

1. The printer job, for example the .ps file
2. The printing options (orientation, ...)
3. The printer options (Filters, drivers, ...), in the printer directory

The printing options can be set with 'echo "A4,300ppp,protrait" >
/printers/LaserJet-A/ctl' The printer options must be in a file, and then you can print with something like 'cat myfile.ps > /printers/LaserJet-A/data'

Saludos.

On Fri, 30 Nov 2007, Enrico Weigelt escribió:

> * Francisco J Ballesteros <nemo@lsub.org> wrote:
> 
> Hi,
> 
> > Seem just too complex to me (the interface, I mean).
> > 
> > Wouldn't just a directory where files to be printed can be copied suffice?
> 
> No, I dont think so.
> Only copying one file is not enough, otherwise you have no chance
> for giving additional parameters like colorspace, orientation, 
> resolution, etc, etc, etc. The application would have to handle all 
> this by itself and would require more detailed information about the 
> printer (which would tie the job to one specific printer).
> 
> And I dont think its too complex. Starting a job is still simple:
> Just create a job dir, upload the content and write your parameters
> to the appropriate files.
> 
> cu
> -- 
> ---------------------------------------------------------------------
>  Enrico Weigelt    ==   metux IT service - http://www.metux.de/
> ---------------------------------------------------------------------
>  Please visit the OpenSource QM Taskforce:
>  	http://wiki.metux.de/public/OpenSource_QM_Taskforce
>  Patches / Fixes for a lot dozens of packages in dozens of versions:
> 	http://patches.metux.de/
> ---------------------------------------------------------------------

-- 
||// //\\// Rodolfo "kix" Garcia
||\\// //\\ http://www.kix.es/


  reply	other threads:[~2007-11-30 13:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-06 23:56 Enrico Weigelt
2007-09-07  8:44 ` Francisco J Ballesteros
2007-09-07 10:08   ` erik quanstrom
2007-09-07 10:17     ` Francisco J Ballesteros
2007-09-07 10:54       ` erik quanstrom
2007-11-30  7:19         ` Aki Nyrhinen
2007-11-30  3:37       ` Enrico Weigelt
2007-11-30  9:42         ` Francisco J Ballesteros
2007-11-30 12:32           ` Enrico Weigelt
2007-11-30 13:06             ` Rodolfo =?unknown-8bit?Q?Garc=EDa?= [this message]
2007-11-30 13:38               ` Enrico Weigelt
2007-11-30 16:56                 ` Rodolfo =?unknown-8bit?Q?Garc=EDa?=
2007-11-30 16:46             ` Anant Narayanan
2007-11-30 22:40               ` Lucas James
2007-12-01  4:42 ` ron minnich
2007-12-01  4:54   ` Bruce Ellis
2007-12-11 13:30     ` roger peppe
2007-12-11 20:36       ` Bruce Ellis

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=20071130130631.GA4274@darkside \
    --to=kix@kix.es \
    --cc=9fans@cse.psu.edu \
    --cc=weigelt@metux.de \
    /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;
as well as URLs for NNTP newsgroup(s).