Your message dated Sun, 18 Jul 2010 03:21:45 +0900
with message-id <[email protected]>
and subject line poppler transition
has caused the Debian Bug report #362127,
regarding xpdf-utils: `pdftops' produces invalid PostScript when source PDF 
contains PS patterns (converted by GS)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
362127: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=362127
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: xpdf-utils
Version: 3.01-7
Severity: normal


Hello,

`pdftops' generates invalid PostScript when the source PDF comes from
a converted PostScript files containing patterns.  To be clearer, let
me illustrate this, using Lout (package `lout', version 3.31):

  $ cat << EOF | lout -o texture.ps
  @SysInclude { doc }
  @Doc
  @Text @Begin

  @Center @Box paint { black } texture { striped } { Bluuuuurps! }

  @End @Text
  EOF
  $ pdf2ps texture.ps  # GS happily does the job
  $ xpdf texture.pdf  # Here a box containing a striped texture is
                      # rendered, no problem.
  $ pdftops texture.pdf texture.broken.ps
  $ gv texture.broken.ps  # Here GS complains and fails to render
                          # the PS file.

Note that this problem does not occur with Xpdf 3.00 (from Debian).

I tried to reproduce the problem with a simple PS file but fail to do
so.  For instance, the following PS file (which produces a PS pattern
similar to that produced by Lout above) does no trigger this problem:

  %!
  <</PageSize [1000 1000] /Policies<</PageSize 1>> >>setpagedevice
  72 72 scale

  <<
      /PatternType 1 % tiling pattern
      /TilingType 1  % constant spacing
      /XStep 1
      /YStep 2
      /PaintType 1   % colored
      /PaintProc {
  pop 0 0 moveto
  1 1 add 0 lineto
  0 1 rlineto
  0 1 lineto
  closepath fill
  }
      /BBox [0 0 10 10]
  >>

  [1 0 0 1 0 0] % identity
  makepattern

  setpattern

  newpath
  0 0 moveto 0 200 lineto 200 100 lineto
  closepath
  fill

  showpage

It might be Lout's handling of PS patterns that is at fault, although
I'd suppose it is unlikely since GS doesn't complain about it.

I hope this is not too obscure.  I'd be glad to help further.

Thanks,
Ludovic.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-686-smp
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages xpdf-utils depends on:
ii  libc6                         2.3.6-4    GNU C Library: Shared libraries an
ii  libgcc1                       1:4.0.2-9  GCC support library
ii  libpaper1                     1.1.14-5   Library for handling paper charact
ii  libstdc++6                    4.0.2-9    The GNU Standard C++ Library v3
ii  xpdf-common                   3.01-7     Portable Document Format (PDF) sui

xpdf-utils recommends no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
fixed 521453 3.02-9
fixed 171956 3.02-9
fixed 409510 3.02-9
fixed 349556 3.02-9
fixed 349096 3.02-9
fixed 202138 3.02-9
fixed 551863 3.02-9
fixed 548766 3.02-9
fixed 521453 3.02-9
fixed 456669 3.02-9
fixed 442328 3.02-9
fixed 421600 3.02-9
fixed 298757 3.02-9
fixed 354506 3.02-9
fixed 359937 3.02-9
fixed 362127 3.02-9
fixed 406256 3.02-9
fixed 406568 3.02-9
fixed 406810 3.02-9
fixed 408342 3.02-9
fixed 411597 3.02-9
fixed 413628 3.02-9
thanks


Since xpdf uses poppler and do not provide programs such as
/usr/bin/pdftotext, I am closing all related bugs on xpdf-utils.

Osamu

[email protected], [email protected], 
[email protected], [email protected], 
[email protected], [email protected], 
[email protected], [email protected], 
[email protected], [email protected], 
[email protected], [email protected], 
[email protected], [email protected], 
[email protected], [email protected], 
[email protected], [email protected], 
[email protected], [email protected], 
[email protected], [email protected]


--- End Message ---

Reply via email to