Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.postscript > #1313

Re: 'eofill'ing areas

Followups directed to: comp.lang.postscript

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

Michael Unger wrote:

> On 2013-03-11 18:02, "Helge Blischke" wrote:
> 
>> Dies the Acrobat 6 distiller emit any log messages?
> 
> There are log files created, but they are _very_ short (long line
> wrapped for readability):
> 
> ---><8------><8------><8------><8------><8------><8------><8------><8---
> 
> Processing prologue.ps...
> Done processing prologue.ps.
> Warning [DSC]:
>  PostScript code in the prolog should be in the procset resources
> Processing epilogue.ps...
> Done processing epilogue.ps.
> 
> ---><8------><8------><8------><8------><8------><8------><8------><8---
> 
> Sometimes when external code snippets are invoked ("run") there are more
> DSC warnings.
> 
> Michael
> 

Probably it is an distiller issiue with the charpath operator. The path 
generated by charpath should be appended to the current path (according to 
the PLRM) but it seems the distiller's implementation clears the current 
path in advance.
I tested this with Mac OS X pstopdf utility (which is used with the preview 
application as well).

For demonstrating this bug, I slightly modified your PS job by 
- only rendering the logo
- replacing the eofill by stroking

You will see that only the "test" outline gets visible, but if you
uncomment the line
% gsave 0 setgray 0.5 setlinewidth stroke grestore % uncomment this line for 
you will see the enclosing rectangle as well, which in this case is only 
retained because the stroke is enclosed in gsave and grestore

Helge

Back to comp.lang.postscript | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

'eofill'ing areas Michael Unger <spam.to.unger@spamgourmet.com> - 2013-03-10 18:46 +0100
  Re: 'eofill'ing areas Helge Blischke <h.blischke@acm.org> - 2013-03-10 22:22 +0100
    Re: 'eofill'ing areas Michael Unger <spam.to.unger@spamgourmet.com> - 2013-03-11 17:31 +0100
      Re: 'eofill'ing areas Helge Blischke <h.blischke@acm.org> - 2013-03-11 18:02 +0100
        Re: 'eofill'ing areas Michael Unger <spam.to.unger@spamgourmet.com> - 2013-03-12 18:45 +0100
          Re: 'eofill'ing areas Helge Blischke <h.blischke@acm.org> - 2013-03-13 11:59 +0100
            Re: 'eofill'ing areas Michael Unger <spam.to.unger@spamgourmet.com> - 2013-03-13 18:00 +0100
              Re: 'eofill'ing areas Helge Blischke <h.blischke@acm.org> - 2013-03-13 18:20 +0100
                Re: 'eofill'ing areas Olle <olavi.sakari@gmail.com> - 2013-03-19 00:25 -0700
                Re: 'eofill'ing areas Olle <olavi.sakari@gmail.com> - 2013-03-19 00:31 -0700
                Re: 'eofill'ing areas luser- -droog <mijoryx@yahoo.com> - 2013-03-20 13:28 -0700
                Re: 'eofill'ing areas Michael Unger <spam.to.unger@spamgourmet.com> - 2013-03-21 17:30 +0100
                Re: 'eofill'ing areas Helge Blischke <h.blischke@acm.org> - 2013-03-21 17:52 +0100
  Re: 'eofill'ing areas luser- -droog <mijoryx@yahoo.com> - 2013-03-10 18:48 -0700

csiph-web