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


Groups > comp.lang.postscript > #1315

Re: 'eofill'ing areas

From Helge Blischke <h.blischke@acm.org>
Newsgroups comp.lang.postscript
Subject Re: 'eofill'ing areas
Followup-To comp.lang.postscript
Date 2013-03-13 18:20 +0100
Message-ID <aqbqrkFio4fU1@mid.individual.net> (permalink)
References (2 earlier) <aq6figFc882U1@mid.individual.net> <aq6h17FciaaU1@mid.individual.net> <aq986fF11urU1@mid.individual.net> <aqb4g9Fdk4tU1@mid.individual.net> <aqbpu1Fih0uU1@mid.individual.net>

Followups directed to: comp.lang.postscript

Show all headers | View raw


Michael Unger wrote:

> On 2013-03-13 11:59, "Helge Blischke" wrote:
> 
>> Probably it is an distiller issiue with the charpath operator.
> 
> Apparently, yes, and a rather nasty bug.
> 
>>                                                                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).
>> 
>> [...]
> 
> I tried another approach as well: using "eoclip" instead of "eofill" to
> define just a clipping area, and then re-drawing the rectangle and
> filling it, which didn't work either.
> 
> So I'll have to print white text onto a coloured background.
> 
> By the way: using the "charpath" operator with a simple "clip" to define
> a clipping area _does_ work as expected. Therefore the bug may as well
> be within Distiller's "even-odd" logic.
I don't think it is the even-odd logic.As you see from my attached example, 
the rectangular path is present prior to the execution of chaqrpath but has 
disappeared afterwards.

> 
> Michael
> 
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