printing docu

[Duane Clark]

Andreas Mohr wrote:

> Hi all,
> 
> while trying to configure Wine for printing in order to be able to use
> Windows Acrobat Reader instead of Linux acroread which is crashing on certain
> PDF files, I remembered that the printing docu is everything but perfect.
> 
> Updated printing docu a bit.

 >

> ...
> -      <sect3>
>          <title>Spooling</title>
>          <para>
>            Spooling is rather primitive. The [spooler] section of
> @@ -82,13 +82,14 @@
>            example the following lines
>          </para>
>          <screen>
> -"LPT1:" = "foo.ps" "LPT2:" = "|lpr"
> +"LPT1:" = "foo.ps"
> +"LPT2:" = "|lpr"
>          </screen>
>          <para>
>            map <systemitem>LPT1:</systemitem> to file <filename>foo.ps</filename>
>            and <systemitem>LPT2:</systemitem> to the <command>lpr</command>
> -          command. If a job is sent to an unlisted port then a file is created
> -          with that port's name e.g. for <systemitem>LPT3:</systemitem> a file
> +          command. If a job is sent to an unlisted port, then a file is created
> +          with that port's name; e.g. for <systemitem>LPT3:</systemitem> a file
>            called <systemitem>LPT3:</systemitem> would be created.
>          </para>
>  	<para>



While it used to work that way, for me at least, the part about - a job 
that is sent to an unlisted port will create a file with the port's name 
- stopped working a few months ago. And I just tested it a few minutes 
ago and it still does not work (for me). I don't know where the data 
goes, but it does not appear to be written to a file anywhere.

Actually, I think that is probably a good thing. In most cases, the 
print dialog should have a "Print to file" button. And if there is no 
way to specify a file name, then the ~/.wine/config entry
"FILE:" = "foo.ps"
will control where it is written, and in this case it will in fact be 
correctly written to the indicated file name.

Duane