All of lore.kernel.org
 help / color / mirror / Atom feed
From: Till Kamppeter <till.kamppeter@gmail.com>
To: Koji Otani <sho@bbr.jp>
Cc: toratani.yasumasa@canon.co.jp,
	printing-architecture@lists.linux-foundation.org
Subject: Re: [Printing-architecture] PDF CUPS filter packages
Date: Wed, 04 Jun 2008 13:59:44 +0200	[thread overview]
Message-ID: <484683B0.2060708@gmail.com> (raw)
In-Reply-To: <20080604.181746.02274177.sho@bbr.jp>

Thank you, now the package rebuilds correctly for me. Next step to fix 
now for you is to eliminate the necessity of full copies of the Poppler 
and CUPS source code in the package.

Another issue are the cost factors in the .convs files. They must 
prioritize the PDF workflow. Note here that lower cost factors give 
higher priority.

I suggest the following:

pdftopdf:
application/pdf         application/vnd.cups-pdf        33   pdftopdf

pdftoraster:
application/vnd.cups-pdf application/vnd.cups-raster    66   pdftoraster

imagetopdf:
image/gif               application/vnd.cups-pdf        50   imagetopdf
...
image/x-sun-raster      application/vnd.cups-pdf        50   imagetopdf

(all lines 50 as cost factor)

We will also need a pstopdf filter to handle PostScript input. This 
filter can be a simple script which can be easily derived from the 
pstoraster filter. It will need the following conversion rule:

pstopdf:
application/postscript   application/pdf                   0 pstopdf

We also need to add the following rule to make native PostScript 
printers working with the PDF workflow (the filter comes already with CUPS):

pdftops:
application/vnd.cups-pdf application/vnd.cups-postscript   0 pdftops


Also a problem are the PPD files shipped with the package. They need 
certain OpenPrinting Vector driver modules which do not ship with the 
package. The PPD files need to be moved into the packages which ship the 
driver modules, as otherwise a printer setup tool will list the 
appropriate printers but printing on them will not work. In addition, 
PPD files should not be put directly into /usr/share/ppd, but into 
/usr/share/ppd/<supplier>/<manufacturer>.


I have also run lintian and linda, reporting the following smaller 
issues with the package:

------------------------------------------------------------------------
till@till-laptop:~/ubuntu/opfc-pdf-filters/opfc-pdf-filters-0.4.1$ linda 
../opfc-pdf-filters_0.4.1-1ubuntu804_amd64.deb
W: opfc-pdf-filters; File 
/usr/share/doc/opfc-pdf-filters/imagetopdf/LICENSE.txt.gz is considered 
to be an extra license file.
W: opfc-pdf-filters; Binary /usr/lib/cups/filter/pdftoopvp compiled with 
an RPATH of /usr/lib.
till@till-laptop:~/ubuntu/opfc-pdf-filters/opfc-pdf-filters-0.4.1$ 
lintian ../opfc-pdf-filters_0.4.1-1ubuntu804_amd64.deb
W: opfc-pdf-filters: extra-license-file 
usr/share/doc/opfc-pdf-filters/imagetopdf/LICENSE.txt.gz
W: opfc-pdf-filters: copyright-without-copyright-notice
till@till-laptop:~/ubuntu/opfc-pdf-filters/opfc-pdf-filters-0.4.1$
------------------------------------------------------------------------

    Till



Koji Otani wrote:
> From: Till Kamppeter <till.kamppeter@gmail.com>
> Subject: Re: [Printing-architecture] PDF CUPS filter packages
> Date: Wed, 04 Jun 2008 11:07:09 +0200
> Message-ID: <48465B3D.4080809@gmail.com>
> 
> till.kamppeter> Koji Otani wrote:
> till.kamppeter> > Hi Till,
> till.kamppeter> > 
> till.kamppeter> > I'm Koji Otani.
> till.kamppeter> > 
> till.kamppeter> > Thank you for trying PDF filters.
> till.kamppeter> > 
> till.kamppeter> > I'm wondering that error with dpkg-buildpackage is caused by using
> till.kamppeter> > the compiler for 64bits. I'll see and fix it.
> till.kamppeter> > 
> till.kamppeter> > Errors with manually compiling are caused by wrong specified
> till.kamppeter> >   --with-poppler-source option. That's option's value should be
> till.kamppeter> >   specified with full path. (See INSTALL please)
> till.kamppeter> >
> till.kamppeter> 
> till.kamppeter> I have used the full path now and the problem still occurs. See below.
> till.kamppeter> 
> till.kamppeter>     Till
> till.kamppeter> 
> 
> Sorry, these problem was caused by newer GCC (>= 4.2).
> I've fixed these and uploaded new packages for Ubuntu 8.04 and Fedora 9.
> Please try these.
> 
> ------------
> Koji Otani.
> 


  parent reply	other threads:[~2008-06-04 11:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-03  6:43 [Printing-architecture] PDF CUPS filter packages TORATANI Yasumasa
2008-06-03 13:06 ` Till Kamppeter
     [not found]   ` <20080604.105602.104056266.sho@bbr.jp>
2008-06-04  9:07     ` Till Kamppeter
     [not found]       ` <20080604.181746.02274177.sho@bbr.jp>
2008-06-04 11:59         ` Till Kamppeter [this message]
2008-06-04 23:16           ` Olaf Meeuwissen
     [not found]             ` <20080605.181530.212681540.sho@bbr.jp>
2008-06-05 23:35               ` Olaf Meeuwissen
     [not found]           ` <20080605.153828.28801505.sho@bbr.jp>
2008-06-05  7:25             ` Till Kamppeter
     [not found]               ` <20080605.193227.233691471.sho@bbr.jp>
2008-06-05 10:53                 ` Till Kamppeter
     [not found]                   ` <20080606.145117.189705417.sho@bbr.jp>
2008-06-06  6:55                     ` Till Kamppeter
2008-06-05 21:34                 ` Till Kamppeter
2008-06-05 21:46                 ` Till Kamppeter
2008-06-05 22:07                 ` Till Kamppeter

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=484683B0.2060708@gmail.com \
    --to=till.kamppeter@gmail.com \
    --cc=printing-architecture@lists.linux-foundation.org \
    --cc=sho@bbr.jp \
    --cc=toratani.yasumasa@canon.co.jp \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.