Hi,
On Mon, 2007-07-23 at 18:34 -0600, D. Stimits wrote:
So I pose this question...if print via PDF is to be considered, why
remove the existing PS system, which is pretty much the best quality
PostScript among all of the apps (commercial and free)?
We are not removing anything. So far
Hi,
On Mon, Jul 23, 2007 at 07:35:17PM +0200, Sven Neumann wrote:
If yes, a solution could be to not distinguish between a Postscript and a
PDF target (i.e. to embed only opaque images into a PDF despite the fact
that PDF can handle images with alpha values).
Would this approach have
Hi,
On Tue, 2007-07-24 at 16:47 +0200, Stefan Roellin wrote:
I think the current implementation of the print plugin is fine, i.e.
generate the PDF with opaque images. If someone needs to have a PDF with
images with alpha values, it would be possible to write a 'save-as-pdf
plugin' similar to
Hi,
On Tue, Jul 24, 2007 at 07:29:20PM +0200, Sven Neumann wrote:
I think the current implementation of the print plugin is fine, i.e.
generate the PDF with opaque images. If someone needs to have a PDF with
images with alpha values, it would be possible to write a 'save-as-pdf
plugin'
On 7/25/07, Stefan Roellin wrote:
Yes, this would of course also be possible and not too different from a
GtkPrint approach. GtkPrint offers dialogs to choose the PageSize etc, which
Cairo does not.
Export to PDF has often been requested. It would be particularly
interesting if it could
Alexandre Prokoudine ([EMAIL PROTECTED]) wrote:
- Will it be possible since GIMP doesn't use Cairo yet?
It does implicitely, since it already depends on a GTK+ version that
depends on cairo.
Bye,
Simon
--
[EMAIL PROTECTED] http://simon.budig.de/
Hi,
On Sun, 2007-07-22 at 14:10 +0200, Stefan Roellin wrote:
The current implementation/patch now has a disadvantage: if you print to a
postscript target, the image has to be exported TWICE: once for the 'print
preview widget' (with alpha) and once for the postscript target (without
alpha).
Sven Neumann wrote:
Hi,
On Sun, 2007-07-22 at 14:10 +0200, Stefan Roellin wrote:
The current implementation/patch now has a disadvantage: if you print to a
postscript target, the image has to be exported TWICE: once for the 'print
preview widget' (with alpha) and once for the postscript
Sven Neumann wrote:
Hi,
On Sun, 2007-07-22 at 14:43 -0600, D. Stimits wrote:
For me, it is a serious problem. I work in the print industry, typically
creating PostScript drivers. The PS output is quite good quality, and
every conversion generally suffers serious quality issues. Gimp is
Hi,
I have submitted a patch which (slightly) improves the quality of the print
plugin (see Bug #387604). The problem basically was that Postscript can't
cope with transparency. In contrast, PDF is able to do so.
The current implementation/patch now has a disadvantage: if you print to a
Stefan Roellin wrote:
Hi,
I have submitted a patch which (slightly) improves the quality of the print
plugin (see Bug #387604). The problem basically was that Postscript can't
cope with transparency. In contrast, PDF is able to do so.
The current implementation/patch now has a disadvantage: if
Does 2.0 have any functioning print plugin? If not, what changes need
to be made to the current 4.2-based plugin?
--
Robert Krawitz [EMAIL PROTECTED]
Tall Clubs International -- http://www.tall.org/ or 1-888-IM-TALL-2
Member of the League for
Hi,
Robert L Krawitz [EMAIL PROTECTED] writes:
Does 2.0 have any functioning print plugin? If not, what changes need
to be made to the current 4.2-based plugin?
It has a functional print plug-in based on gimp-print 4.2.
For GIMP-2.2, we'd like to provide a print plug-in based on a newer
Hi,
Robert L Krawitz wrote:
I'm the Gimp-Print project lead, that's why I asked the question :-)
I know :) Sorry to hear the 5.0 release is still a bit away.
In the 5.0 tree, the plugin has been split into two pieces, a UI
library (libgimpprintui) and the GIMP plugin proper (which is tiny,
and
Hi,
Robert L Krawitz [EMAIL PROTECTED] writes:
In the 5.0 tree, the plugin has been split into two pieces, a UI
library (libgimpprintui) and the GIMP plugin proper (which is tiny,
and contains all of the GIMP-specific code). We should work out the
appropriate ownership of of these two
Date: Fri, 12 Mar 2004 14:25:23 +0100
From: Dave Neary [EMAIL PROTECTED]
Hi,
Robert L Krawitz wrote:
I'm the Gimp-Print project lead, that's why I asked the question :-)
I know :) Sorry to hear the 5.0 release is still a bit away.
In the 5.0 tree, the plugin has been
From: Sven Neumann [EMAIL PROTECTED]
Date: 12 Mar 2004 14:19:13 +0100
Robert L Krawitz [EMAIL PROTECTED] writes:
In the 5.0 tree, the plugin has been split into two pieces, a UI
library (libgimpprintui) and the GIMP plugin proper (which is tiny,
and contains all of the
Hi,
Robert L Krawitz [EMAIL PROTECTED] writes:
libgimpprint is a GTK+ (1.2 right now) UI, without any linkage to
libgimp.
It will have to be ported to the GTK+-2.x API if you want it to be
useful. Are there any plans to do that?
Sven
___
From: Sven Neumann [EMAIL PROTECTED]
Date: 13 Mar 2004 03:45:21 +0100
Robert L Krawitz [EMAIL PROTECTED] writes:
libgimpprint is a GTK+ (1.2 right now) UI, without any linkage to
libgimp.
It will have to be ported to the GTK+-2.x API if you want it to be
useful. Are there
Hi,
Robert L Krawitz [EMAIL PROTECTED] writes:
I expect that we're going to go alpha with 4.2 in the relatively near
future, and then release some time this summer. What should we do
about syncing up?
What are you suggesting? I think we are willing to include
a new version with stable
From: Sven Neumann [EMAIL PROTECTED]
Date: 20 May 2001 13:47:36 +0200
Robert L Krawitz [EMAIL PROTECTED] writes:
I expect that we're going to go alpha with 4.2 in the relatively near
future, and then release some time this summer. What should we do
about syncing up?
I expect that we're going to go alpha with 4.2 in the relatively near
future, and then release some time this summer. What should we do
about syncing up?
--
Robert Krawitz [EMAIL PROTECTED] http://www.tiac.net/users/rlk/
Tall Clubs International -- http://www.tall.org/ or
22 matches
Mail list logo
