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


Groups > comp.lang.postscript > #2994

Re: Welcome to comp.lang.postscript!

From ken <ken@spamcop.net>
Newsgroups comp.lang.postscript
Subject Re: Welcome to comp.lang.postscript!
Date 2017-01-27 08:08 +0000
Message-ID <MPG.32f5103f50fd5f7d989913@usenet.plus.net> (permalink)
References (8 earlier) <o5fflc$2nad$1@news.kjsl.com> <o5jg13$r6u$1@news.kjsl.com> <53e6fb83-a795-4e1b-9af9-0ec30f9a5bb6@googlegroups.com> <d5d06860-41b3-44a4-9f73-2e9954100756@googlegroups.com> <bf7ac368-5667-436c-a3b1-8e1a56acf8e5@googlegroups.com>

Show all headers | View raw


In article <bf7ac368-5667-436c-a3b1-8e1a56acf8e5@googlegroups.com>, 
luser.droog@gmail.com says...

> answer Ken writes on SO says pretty much this:
> 
> > There are no foolproof, omnipotent, programmable, programmed or universally simple methods for fixing Adobe PostScript files! There is a mathematical proof of the Halting Problem which is the reason why such methods do not exist. `Fixing' includes changing PS into EPS, making a file universally printable or viewable, rearranging or removing graphic elements from an image, etc.
> 
> > Methods do exist for specific situations such as Adobe PostScript files generated by specific versions of specific applications. Program do exist that can modify the output of a large number of versions of a large number of commerically available applications. This is not the general case.

LOL I'm pretty sure I never said that, though I wish I had, its better
written than anything I come up with :-)


Ken

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


Thread

Welcome to comp.lang.postscript! luser droog <luser.droog@gmail.com> - 2016-07-07 23:22 -0700
  Re: Welcome to comp.lang.postscript! Lawrence D’Oliveiro <lawrencedo99@gmail.com> - 2016-08-04 17:05 -0700
  Re: Welcome to comp.lang.postscript! Martin Leese <please@see.Web.for.e-mail.INVALID> - 2016-08-04 23:12 -0600
  Re: Welcome to comp.lang.postscript! luser droog <luser.droog@gmail.com> - 2017-01-02 16:28 -0800
    Re: Welcome to comp.lang.postscript! Carlos <angus@quovadis.com.ar> - 2017-01-03 15:24 +0100
      Re: Welcome to comp.lang.postscript! Michael Unger <spam.to.unger@spamgourmet.com> - 2017-01-03 17:27 +0100
      Re: Welcome to comp.lang.postscript! luser droog <luser.droog@gmail.com> - 2017-01-03 09:46 -0800
        Re: Welcome to comp.lang.postscript! luser droog <luser.droog@gmail.com> - 2017-01-11 20:03 -0800
          Re: Welcome to comp.lang.postscript! luser droog <luser.droog@gmail.com> - 2017-01-11 20:09 -0800
        Re: Welcome to comp.lang.postscript! tlvp <mPiOsUcB.EtLlLvEp@att.net> - 2017-01-12 03:35 -0500
          Re: Welcome to comp.lang.postscript! Ross Presser <rpresser@gmail.com> - 2017-01-12 20:02 -0800
            Re: Welcome to comp.lang.postscript! tlvp <mPiOsUcB.EtLlLvEp@att.net> - 2017-01-13 23:22 -0500
              Re: Welcome to comp.lang.postscript! helbig@asclothestro.multivax.de (Phillip Helbig (undress to reply)) - 2017-01-14 07:58 +0000
                Re: Welcome to comp.lang.postscript! tlvp <mPiOsUcB.EtLlLvEp@att.net> - 2017-01-14 23:09 -0500
                Re: Welcome to comp.lang.postscript! helbig@asclothestro.multivax.de (Phillip Helbig (undress to reply)) - 2017-01-15 09:33 +0000
                Re: Welcome to comp.lang.postscript! tlvp <mPiOsUcB.EtLlLvEp@att.net> - 2017-01-16 00:38 -0500
                Re: Welcome to comp.lang.postscript! helbig@asclothestro.multivax.de (Phillip Helbig (undress to reply)) - 2017-01-16 22:04 +0000
                Re: Welcome to comp.lang.postscript! luser droog <luser.droog@gmail.com> - 2017-01-24 10:11 -0800
                Re: Welcome to comp.lang.postscript! luser droog <luser.droog@gmail.com> - 2017-01-26 09:58 -0800
                Re: Welcome to comp.lang.postscript! luser droog <luser.droog@gmail.com> - 2017-01-26 10:04 -0800
                Re: Welcome to comp.lang.postscript! ken <ken@spamcop.net> - 2017-01-27 08:08 +0000

csiph-web