Hi, I´m allways using the recent versions from cvs (prebuild from dailywine) and I stated that I have to reconfigure my wine printing. Before I used the wineps.drv driver but now wine seams to work with the printers defined in /etc/printcap. But there are some little questions left by me although I got it printing well: 1. How can I make another printer as default printer different from the first one from /etc/printcap. I tried to edit win.ini but everytime wine is started the first printcap entry is installed as default printer. 2. How can I exclude some /etc/printcap printers from scanning by wine? Does it make sense to define printcap printers like ascii (my hp ps printer has three entries in printcap: ascii, lp, raw) in wine? Printing a document on the ascii printer the wine ps output is printed as ps source code, which is normal for the ascii spooler, which will pass the spooler input thru a2ps. 3.
In article <01051518130400.12207@lighthouse>, Marcus Roeckrath <wine-users@winehq.com> wrote:>Hi, > >I´m allways using the recent versions from cvs (prebuild from >dailywine) and I stated that I have to reconfigure my wine printing. > >Before I used the wineps.drv driver but now wine seams to work with >the printers defined in /etc/printcap. > >But there are some little questions left by me although I got it >printing well: > > >1. >How can I make another printer as default printer different from >the first one from /etc/printcap.This is currently not possible I am afraid.>I tried to edit win.ini but everytime wine is started the first >printcap entry is installed as default printer.Yes.>2. >How can I exclude some /etc/printcap printers from scanning by wine?>Does it make sense to define printcap printers like ascii (my hp ps >printer has three entries in printcap: ascii, lp, raw) in wine? >Printing a document on the ascii printer the wine ps output is >printed as ps source code, which is normal for the ascii spooler, >which will pass the spooler input thru a2ps.The current magic tries to autodetect postscript printers in /etc/printcap and only lists those.>3. >From where can I get ppd files for non ps printers?I have included a generic.ppd in documentation/samples/ which should work for all ghostscript emulated printers.>4. >Why does the former installed Wine PostScript Driver does not work >anymore?Huh, it still should? Ciao, Marcus
Marcus Roeckrath wrote:> > 1. > > How can I make another printer as default printer different from > the first one from /etc/printcap. >You can't.> 2. > > How can I exclude some /etc/printcap printers from scanning by wine? >You can't.> Does it make sense to define printcap printers like ascii (my hp ps > printer has three entries in printcap: ascii, lp, raw) in wine? > Printing a document on the ascii printer the wine ps output is > printed as ps source code, which is normal for the ascii spooler, > which will pass the spooler input thru a2ps. >It doesn't make sense. The scanning code tries to figure out if a printer is PostScript-capable or not, but the heuristics are pretty primitive at this point.> 3. > > From where can I get ppd files for non ps printers? >In general, there's no such thing. If, however, you're using Ghost- script to print to a non-PostScript laser printer, there's probably a PostScript-capable variant or PostScript option that will have a PPD file.> 4. > > Why does the former installed Wine PostScript Driver does not work > anymore? >What do you mean? The great to-do list in the sky includes adding a check for a [ppd] file entry in the Wine config file; if it isn't there, /etc/printcap scanning will be disabled, and you will have to set up Wine printers the "old fashioned" way. Would this work for you? -- =======================================================================Ian Pilcher ian.pilcher@home.com ========================================================================
Hi Marcus, Marcus Meissner wrote on Die, 15 Mai 2001 about Re: New printing concept of wine> The current magic tries to autodetect postscript printers in /etc/printcap > and only lists those.On my system all 10 queues are detected as postscript, while at maximum 4 of them are capable of postscript either directly (my postscript printer) or via ghostscript.> >From where can I get ppd files for non ps printers? > > I have included a generic.ppd in documentation/samples/ which should > work for all ghostscript emulated printers.I downloaded precompiled binaries from dailywine and dataparty. Both of them does not contain a generic ppd file. The dataparty rpm in addition has an older printing.sgml file which does not explain this new technologie. How it is possible to define a default ppd for printers that are not defined in ~/.wine/config? I tried something like "*"="somewhat.ppd" but this does not help. In addition it is very critical to have not defined an entry for one of the printers which is found by wine. I do not have the chance to print or setup printing in a windows app, if there are printcap printer and not a ppd file defined in config. So I have given all printers the same ppd file although I do not want to use most of them.> >4. > >Why does the former installed Wine PostScript Driver does not work > >anymore? > > Huh, it still should?I did not have any success. I have used the wineps.drv method before in the way it was described in the printing manual - means: made the additions to the system reg (from psdrv.reg) and the changes to the windows win.ini manually. This wineps driver can be choosed from the printer choose dialog in a win app but a setup of this printer or a printing on this one isn´t possible. I do not need this driver in future so I have deleted the driver from my wine registry and the win.ini. I think the new way is a better way handling wine printing but little approvements should be made: - only those printer from printcap which have a valid ppd file should be used. - the default printer from win.ini and/or system.reg should be honoured. (Why are the default entries in both files different? I can change the registry entry manually without having any effect.) Good work. Wines job is made better and better although there are little problems left. -- Gruss Marcus Marcus Roeckrath -- Vikarsbusch 8 -- D-48308 Senden -- Germany Phone : +49-2536-9944 -- Mailer/BBS/Fax : +49-2536-9943 (V34, X75) FidoNet: 2:2449/523 E-Mail : marcus.roeckrath@gmx.de WWW : http://home.foni.net/~marcusroeckrath/
I'm using the old wineps printing system in recent version of winex and it works OK. I've tried to figure out the print system but can't make any sense out of it. Is there a HOWTO that explains the new system or can someone clue me in on how to read the PRINTING.SGML file? Thanks, Rick Knight (rick@rlknight.com) Marcus Roeckrath wrote:> Hi, > > I?m allways using the recent versions from cvs (prebuild from > dailywine) and I stated that I have to reconfigure my wine printing. > > Before I used the wineps.drv driver but now wine seams to work with > the printers defined in /etc/printcap. > > But there are some little questions left by me although I got it > printing well: > > 1. > > How can I make another printer as default printer different from > the first one from /etc/printcap. > > I tried to edit win.ini but everytime wine is started the first > printcap entry is installed as default printer. > > 2. > > How can I exclude some /etc/printcap printers from scanning by wine? > > Does it make sense to define printcap printers like ascii (my hp ps > printer has three entries in printcap: ascii, lp, raw) in wine? > Printing a document on the ascii printer the wine ps output is > printed as ps source code, which is normal for the ascii spooler, > which will pass the spooler input thru a2ps. > > 3. > > From where can I get ppd files for non ps printers? > > 4. > > Why does the former installed Wine PostScript Driver does not work > anymore? > > -- > > Gruss Marcus > > Marcus Roeckrath -- Vikarsbusch 8 -- D-48308 Senden -- Germany > Phone : +49-2536-9944 -- Mailer/BBS/Fax : +49-2536-9943 (V34, X75) > FidoNet: 2:2449/523 > E-Mail : marcus.roeckrath@gmx.de > WWW : http://home.foni.net/~marcusroeckrath/ > > _______________________________________________ > wine-users mailing list > wine-users@winehq.com > http://www.winehq.com/mailman/listinfo/wine-users
why not use sgml2html? or sgml2info sgml2latex sgml2lyx sgml2rtf sgml2txt sgml2xml ? (included in package sgmltools on suse7.2)
why write something in a format you have to translate to read? if abiword, staroffice, or even koffice had support for it i could understand but as it stands it seems like a waste of time. the whole point of writting the docs is to help those that are new to something. Why stack more on the plate. On Thursday 26 July 2001 08:35, you wrote:> why not use sgml2html? > > or > > sgml2info > sgml2latex > sgml2lyx > sgml2rtf > sgml2txt > sgml2xml ? > > (included in package sgmltools on suse7.2) > _______________________________________________ > wine-users mailing list > wine-users@winehq.com > http://www.winehq.com/mailman/listinfo/wine-users
On Tue, 31 Jul 2001, pfrostie@yahoo.com wrote:> why write something in a format you have to translate to read? if abiword, > staroffice, or even koffice had support for it i could understand but as it > stands it seems like a waste of time.Flexibility.> the whole point of writting the docs is to help those that are new to > something. Why stack more on the plate.Not everyone wants their documentation in the same format. SGML, LaTeX and DocBook allow the user (or the developer) to simultaneously release the docs in HTML, postscript, plain text, pdf, info pages, man pages and so forth without any extra work (beyond a couple of lines in a makefile). There are times when I want a printed manual that can sit by my desk as I develop. There are times when I want to know the page numbers of all the occurences of some text or phrase not referenced in the index. There are times when hyperlinked text allows rapid discovery of key information. Intermediate formats give that flexibility. Cheers, Toby Haynes -- Toby Haynes The views and opinions expressed in this message are my own, and do not necessarily reflect those of IBM Canada.