Any chance of including in 11.0? It would be much better and more up-to-date to be able to print to pdf rather than ps which is becoming a rarity. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Sid Boyce wrote:
Any chance of including in 11.0? It would be much better and more up-to-date to be able to print to pdf rather than ps which is becoming a rarity.
Why that? Which advantage of the cups-pdf backend do you expect? Regards, Klaus. -- Klaus Singvogel SUSE LINUX Products GmbH Maxfeldstr. 5 E-Mail: Klaus.Singvogel@SuSE.de 90409 Nuernberg Phone: +49 (0) 911 740530 Germany GnuPG-Key-ID: 1024R/5068792D 1994-06-27 SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Klaus Singvogel wrote:
Sid Boyce wrote:
Any chance of including in 11.0? It would be much better and more up-to-date to be able to print to pdf rather than ps which is becoming a rarity.
Why that? Which advantage of the cups-pdf backend do you expect?
Regards, Klaus.
To be able to get a .pdf file output from firefox instead of .ps. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
To be able to get a .pdf file output from firefox instead of .ps.
You could use kprinter in firefox to achieve that, assuming you are using KDE: http://gentoo-wiki.com/HOWTO_Integrate_Firefox_with_KDE#Printing:_KPrinter Best regards Marcio Ferreira --- Druid --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Druid wrote:
To be able to get a .pdf file output from firefox instead of .ps.
You could use kprinter in firefox to achieve that, assuming you are using KDE: http://gentoo-wiki.com/HOWTO_Integrate_Firefox_with_KDE#Printing:_KPrinter
Best regards
Marcio Ferreira --- Druid
Thanks, I shall have a look. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Why isn't Firefox setup by default to use Kprinter??? I mean they hack the hell out of PHP to make it incompatible with some scripts, hack the hell out of firefox so it crashes when I use Yahoo maps so why not just add one annoynace to the list? Actually strike hack and replace with optimise and I'm quite annoyed at Firefox not using Kprinter by default. And on the not-sarcastic note I had no idea such a change could be made. On Feb 5, 2008 5:43 PM, Druid <marcio.ferreira@gmail.com> wrote:
To be able to get a .pdf file output from firefox instead of .ps.
You could use kprinter in firefox to achieve that, assuming you are using KDE: http://gentoo-wiki.com/HOWTO_Integrate_Firefox_with_KDE#Printing:_KPrinter
Best regards
Marcio Ferreira --- Druid
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
* Andrew Joakimsen <joakimsen@gmail.com> [02-06-08 17:28]: ...
I'm quite annoyed at Firefox not using Kprinter by default. And on the not-sarcastic note I had no idea such a change could be made.
sorry your annoyed, but it's not hard. Edit ~/.mozilla/firefox/xxxxxxxx.default/prefs.js and change user_pref("print.print_printer", "CUPS/esp925"); to user_pref("print.print_printer", "kprinter"); I believe is all that is necessary. ps: Please trim your quotes. -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Patrick Shanahan wrote:
* Andrew Joakimsen <joakimsen@gmail.com> [02-06-08 17:28]: ...
I'm quite annoyed at Firefox not using Kprinter by default. And on the not-sarcastic note I had no idea such a change could be made.
sorry your annoyed, but it's not hard.
Edit
~/.mozilla/firefox/xxxxxxxx.default/prefs.js
and change user_pref("print.print_printer", "CUPS/esp925"); to user_pref("print.print_printer", "kprinter");
I believe is all that is necessary.
I didn't find any such variable in my prefs.js Running Firefox and using URL "about:config" (without quotes) shows these two related variables: print.postscript.print_command print.print_command You might want to edit those? Regards, Klaus. -- Klaus Singvogel SUSE LINUX Products GmbH Maxfeldstr. 5 E-Mail: Klaus.Singvogel@SuSE.de 90409 Nuernberg Phone: +49 (0) 911 740530 Germany GnuPG-Key-ID: 1024R/5068792D 1994-06-27 SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Hello, On Feb 5 22:30 Sid Boyce wrote (shortened):
Klaus Singvogel wrote:
Sid Boyce wrote:
Any chance of including in 11.0? It would be much better and more up-to-date to be able to print to pdf rather than ps which is becoming a rarity.
Why that? Which advantage of the cups-pdf backend do you expect?
To be able to get a .pdf file output from firefox instead of .ps.
User applications (including user print dialog programs like "kprinter") run on the user's local machine as a user's process under the user's ID (i.e. they run in the user's personal environment). Therefore applications can store files (e.g. PDFs) in the user's home directory (or wherever the user has specified in the application). On the other hand the processes of the printing system do not run under the user's ID and in case of printing in the network they even run on an arbitrary different machine in the network. Therefore the printing system cannot store files in whatever place which was specified by a user who has submitted a print job. Of course you can use some of the hacks for single-user stand-alone systems to "print" whatever output format you like into a static file but obviously static file locations cannot work in a multi-tasking multi-user networked system and therefore we cannot provide out-of-the-box support for such evil hacks. Also "print to ps file" is done by the user application itself. No printing system is involved when the user application does not send its printing output to a print queue but instead stores it into whatever file the user likes. If you like "print to PDF file" in whatever user application, file seperated enhancement requests for each of those applications. For KDE and/or Gnome only two such enhancement requests should be enough because all KDE and/or Gnome applications should use the same KDE and/or Gnome printing engine so that it should be sufficient to implement a "print to PDF file" function in the KDE and/or Gnome printing engines. I don't know if any KDE application print dialog offers a "print to PDF file" or if this can be only done via "kprinter". Rgegarding "print to PS/PDF" and "PS/PDF printer" versus "save as PS/PDF": Only the latter is the correct wording for what actually happens. Also "print as PS file" is misleading because what actually happens is "save as PS". I think the reason for the confusion with the wording is that the "save as PS" functionality is often not found in the "file" menue. Instead in the "print" menue a "print to file" option can be found and fortunately this results a PostScript file so that for the user it looks as if printing is done when he likes to do "save as PS". If it would have been "save as PS" under the "file" menue, nobody would ask if CUPS could somehow provide a "save as PDF" option in the application programs. An example how it can be implemented correctly is the "xv" program. Here it is the "save" menue where one can select "PostScript" among various other types and there is no "print to file" option for the "print" functionality. Some time ago I checked OpenOffice: There is no "save as PS" option under the "file" menue but one can print into a file via the "print" menue. Strictly speaking "save as PS" and "print to file" are not the same regarding the result. Only "save as PS" guarantees that the result is a PostScript file. In contrast "print to file" can result whatever arbitrary printer-specific (binary) data which the application produces to be sent as print job (e.g. Gimp can produce arbitrary printer-specific data). Only by chance (more precisely because PS is the usual data format when Unix/Linux applications produce data for print jobs) it happens that "print to file" can be misused when there is no "save as PS" functionality in the application. But even this is no guarantee that such a PostScript file would print on any printer because it can be printer-specific PostScript. E.g. OpenOffice is known to produce printer-specific PostScript so that such a PostScript file may only print on the printer for which OpenOffice has made it. As far as I understand what you actually request is: - A "save as PS" option which results printer-independent PostScript. - A "save as PDF" option which results a portable, archivable, and printable PDF file i.e. PDF/A (for archiving) or even better PDF/X (for printing) which are both subsets of PDF leaving out PDF features not suited for reliable archiving and printing respectively. Again: This has nothing to do with the printing system. It belongs only to the application programs. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Johannes Meixner wrote:
Hello,
On Feb 5 22:30 Sid Boyce wrote (shortened):
Klaus Singvogel wrote:
Sid Boyce wrote:
Any chance of including in 11.0? It would be much better and more up-to-date to be able to print to pdf rather than ps which is becoming a rarity. Why that? Which advantage of the cups-pdf backend do you expect? To be able to get a .pdf file output from firefox instead of .ps.
User applications (including user print dialog programs like "kprinter") run on the user's local machine as a user's process under the user's ID (i.e. they run in the user's personal environment). Therefore applications can store files (e.g. PDFs) in the user's home directory (or wherever the user has specified in the application).
On the other hand the processes of the printing system do not run under the user's ID and in case of printing in the network they even run on an arbitrary different machine in the network.
Therefore the printing system cannot store files in whatever place which was specified by a user who has submitted a print job.
Of course you can use some of the hacks for single-user stand-alone systems to "print" whatever output format you like into a static file but obviously static file locations cannot work in a multi-tasking multi-user networked system and therefore we cannot provide out-of-the-box support for such evil hacks.
Also "print to ps file" is done by the user application itself. No printing system is involved when the user application does not send its printing output to a print queue but instead stores it into whatever file the user likes.
If you like "print to PDF file" in whatever user application, file seperated enhancement requests for each of those applications.
For KDE and/or Gnome only two such enhancement requests should be enough because all KDE and/or Gnome applications should use the same KDE and/or Gnome printing engine so that it should be sufficient to implement a "print to PDF file" function in the KDE and/or Gnome printing engines.
I don't know if any KDE application print dialog offers a "print to PDF file" or if this can be only done via "kprinter".
Rgegarding "print to PS/PDF" and "PS/PDF printer" versus "save as PS/PDF":
Only the latter is the correct wording for what actually happens. Also "print as PS file" is misleading because what actually happens is "save as PS".
I think the reason for the confusion with the wording is that the "save as PS" functionality is often not found in the "file" menue. Instead in the "print" menue a "print to file" option can be found and fortunately this results a PostScript file so that for the user it looks as if printing is done when he likes to do "save as PS".
If it would have been "save as PS" under the "file" menue, nobody would ask if CUPS could somehow provide a "save as PDF" option in the application programs.
An example how it can be implemented correctly is the "xv" program. Here it is the "save" menue where one can select "PostScript" among various other types and there is no "print to file" option for the "print" functionality.
Some time ago I checked OpenOffice: There is no "save as PS" option under the "file" menue but one can print into a file via the "print" menue.
Strictly speaking "save as PS" and "print to file" are not the same regarding the result. Only "save as PS" guarantees that the result is a PostScript file. In contrast "print to file" can result whatever arbitrary printer-specific (binary) data which the application produces to be sent as print job (e.g. Gimp can produce arbitrary printer-specific data).
Only by chance (more precisely because PS is the usual data format when Unix/Linux applications produce data for print jobs) it happens that "print to file" can be misused when there is no "save as PS" functionality in the application. But even this is no guarantee that such a PostScript file would print on any printer because it can be printer-specific PostScript. E.g. OpenOffice is known to produce printer-specific PostScript so that such a PostScript file may only print on the printer for which OpenOffice has made it.
As far as I understand what you actually request is:
- A "save as PS" option which results printer-independent PostScript.
- A "save as PDF" option which results a portable, archivable, and printable PDF file i.e. PDF/A (for archiving) or even better PDF/X (for printing) which are both subsets of PDF leaving out PDF features not suited for reliable archiving and printing respectively.
Again: This has nothing to do with the printing system. It belongs only to the application programs.
Kind Regards Johannes Meixner
On reflection, it's really an application problem, specifically mozilla/firefox "Print to File" giving ps as the only option. I shall enter a feature request with mozilla. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Sid Boyce wrote:
Klaus Singvogel wrote:
Sid Boyce wrote:
Any chance of including in 11.0? It would be much better and more up-to-date to be able to print to pdf rather than ps which is becoming a rarity.
Why that? Which advantage of the cups-pdf backend do you expect?
To be able to get a .pdf file output from firefox instead of .ps.
I agree to Johannes posting earlier this day on this mailing list. Please have a look at it. It is not the job of the printing system to generate user specific file types. Including "cups-"pdf for generation of such user specific file printouts might result in major security issues. Such an enhancement contradicts the design of the printing system. We don't mind, if you include this backend at your own installation. But we cannot do this in our distribution for all customers. The risks are too high. But another solution for you might be: - save the output into a .ps file - and run 'ps2pdf' on the .ps file Regards, Klaus. -- Klaus Singvogel SUSE LINUX Products GmbH Maxfeldstr. 5 E-Mail: Klaus.Singvogel@SuSE.de 90409 Nuernberg Phone: +49 (0) 911 740530 Germany GnuPG-Key-ID: 1024R/5068792D 1994-06-27 SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (6)
-
Andrew Joakimsen -
Druid -
Johannes Meixner -
Klaus Singvogel -
Patrick Shanahan -
Sid Boyce