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

Groups > comp.lang.postscript > #2232

Re: setstrokeadjust: what's the disadvantage?

Show all headers | View raw

In article <0951df15-771a-4953-9561-2eff99e5a323@googlegroups.com>, 
jdawiseman@gmail.com says...
 
> So the disadvantage is all about processor time: thank you. 
> 
> My PLRM3 says "First printing February 1999".

Yes, but the feature it was introduced in 1990 in language level 2. 
There were custom implementations even before that if I remember 
correctly, you just couldn't control them, or at least not in a defined 
cross-printer manner.


> It seems likely that a 2015 printer has memory and CPU as good as 
those of a typical 1999 computer.

Hmm, I certainly wouldn't like to count on that.


> (Indeed, it seems likely that a 2015 phone has memory and CPU as good 
as those of a typical 1999 computer.)

That's undoubtedly true, but you might be surprised how hard 
manufacturers of printers strive to hold down the component cost.


> So, though there was a historical need for 'false setstrokeadjust', 
I'm guessing that the need has expired. At least mostly, and more and 
more with each passing year.

I guess it depends on whether you want your pages faster or (almost 
trivially, depending on resolution) 'better'.

Higher resolution (and printers do keep increasing resolution, albeit 
slowly) means more time taken to do scan conversion. If you add stroke 
adjustment, that takes still more time, and for less and less benefit as 
the resolution increases. Remember, the maximum error is 2 device 
pixels, whch is only 1/300 of an inch at 600 dpi. At 1440 dpi (not 
entriely atypical for inkjets) a 2 pixel difference in linewidth is 
1/720 inch. Unless you are drawing with something like 0 setlinewidth 
the differing stroke widths will be hard to see.

And if the resolution goes up again, even harder.


> Do you agree that strokeadjust'ing that should be swift on a modern 
printer?

It will still be slower than *not* doing it, and manufacturers like to 
quote pages per minute as high as possible....

Given that the benefit is minimal at higher resoltuions, why waste the 
time, however small it is ? Though at lower resolutions its defintely 
worth the effort.

And we *do* get beaten up by printer manufacturers over performance, 
seriously!


			Ken

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

Thread

setstrokeadjust: what's the disadvantage? jdaw1 <jdawiseman@gmail.com> - 2015-04-27 03:25 -0700
  Re: setstrokeadjust: what's the disadvantage? ken <ken@spamcop.net> - 2015-04-27 14:29 +0100
    Re: setstrokeadjust: what's the disadvantage? jdaw1 <jdawiseman@gmail.com> - 2015-04-27 08:56 -0700
      Re: setstrokeadjust: what's the disadvantage? tlvp <mPiOsUcB.EtLlLvEp@att.net> - 2015-04-27 14:59 -0400
        Re: setstrokeadjust: what's the disadvantage? jdaw1 <jdawiseman@gmail.com> - 2015-04-27 13:29 -0700
          Re: setstrokeadjust: what's the disadvantage? tlvp <mPiOsUcB.EtLlLvEp@att.net> - 2015-04-27 22:43 -0400
      Re: setstrokeadjust: what's the disadvantage? ken <ken@spamcop.net> - 2015-04-28 07:54 +0100
        Re: setstrokeadjust: what's the disadvantage? jdaw1 <jdawiseman@gmail.com> - 2015-04-28 02:01 -0700
          Re: setstrokeadjust: what's the disadvantage? ken <ken@spamcop.net> - 2015-04-28 11:27 +0100
            Re: setstrokeadjust: what's the disadvantage? jdaw1 <jdawiseman@gmail.com> - 2015-04-28 04:02 -0700
        Re: setstrokeadjust: what's the disadvantage? Mark Carroll <mtbc@bcs.org> - 2015-04-28 10:43 +0100
  Re: setstrokeadjust: what's the disadvantage? jdaw1 <jdawiseman@gmail.com> - 2015-05-01 15:16 -0700
    Re: setstrokeadjust: what's the disadvantage? ken <ken@spamcop.net> - 2015-05-02 09:13 +0100
      Re: setstrokeadjust: what's the disadvantage? jdaw1 <jdawiseman@gmail.com> - 2015-05-02 03:29 -0700

csiph-web