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

Groups > comp.lang.postscript > #2743 > unrolled thread

News from the SO [postscript] tag

Back to article view | Back to comp.lang.postscript

Contents

  News from the SO [postscript] tag luser droog <luser.droog@gmail.com> - 2016-08-09 09:42 -0700
    Re: News from the SO [postscript] tag ken <ken@spamcop.net> - 2016-08-10 07:48 +0100
      Re: News from the SO [postscript] tag luser droog <luser.droog@gmail.com> - 2016-08-13 14:46 -0700
        Re: News from the SO [postscript] tag Lawrence D’Oliveiro <lawrencedo99@gmail.com> - 2016-08-13 23:02 -0700
    Re: News from the SO [postscript] tag Terry Burton <terry.burton@gmail.com> - 2016-08-24 06:22 -0700
      Re: News from the SO [postscript] tag luser droog <luser.droog@gmail.com> - 2016-08-27 21:13 -0700
        Re: News from the SO [postscript] tag luser droog <luser.droog@gmail.com> - 2016-09-01 00:19 -0700
          Re: News from the SO [postscript] tag luser droog <luser.droog@gmail.com> - 2016-09-05 20:08 -0700
            Re: News from the SO [postscript] tag Alan <alan.isaac@gmail.com> - 2016-09-06 10:24 -0700
              Re: News from the SO [postscript] tag jdaw1 <jdawiseman@gmail.com> - 2016-09-06 16:23 -0700
              Re: News from the SO [postscript] tag luser droog <luser.droog@gmail.com> - 2016-09-06 22:45 -0700
              Re: News from the SO [postscript] tag luser droog <luser.droog@gmail.com> - 2016-09-06 22:57 -0700

#2743 — News from the SO [postscript] tag

By my reckoning, Ken is just 4 upvotes away from getting
the first Silver [Postscript] tag badge. This is after
swooshing the first Bronze one a few years ago. So watch
for it, it's coming. And congratulations!

We need 2 more committers to the Documentation part to
start contributing examples.

And as always, need more interesting questions!

[toc] | [next] | [standalone]

#2745

In article <eeaa5472-c5f3-443a-a9e6-3a9e83fd13d4@googlegroups.com>, 
luser.droog@gmail.com says...

> the first Silver [Postscript] tag badge. This is after
> swooshing the first Bronze one a few years ago. So watch
> for it, it's coming. And congratulations!

:-D Thanks, I didn't realise I was being stalked :-)

 
> We need 2 more committers to the Documentation part to
> start contributing examples.

I did consider signing up for that, but.... I'm not sure what to add to 
'documentation' over and above the excellent PLRM, the Green, Blue, 
Black and White Books and the huge series of Adobe Technical Notes. Did 
you have any ideas ?



				Ken

[toc] | [prev] | [next] | [standalone]

#2768

On Wednesday, August 10, 2016 at 1:48:56 AM UTC-5, ken wrote:
> In article <eeaa5472-c5f3-443a-a9e6-3a9e83fd13d4@googlegroups.com>, 
> luser.droog@gmail.com says...
> 
> > the first Silver [Postscript] tag badge. This is after
> > swooshing the first Bronze one a few years ago. So watch
> > for it, it's coming. And congratulations!
> 
> :-D Thanks, I didn't realise I was being stalked :-)
> 

Well, I got impatient and went on a "Fremen"[1] voting
spree. 
  
> > We need 2 more committers to the Documentation part to
> > start contributing examples.
> 
> I did consider signing up for that, but.... I'm not sure what to add to 
> 'documentation' over and above the excellent PLRM, the Green, Blue, 
> Black and White Books and the huge series of Adobe Technical Notes. Did 
> you have any ideas ?
> 

Not specifically. I felt inspired by viewing the beginning
of the C part. http://stackoverflow.com/documentation/c/topics
Once it opens up, users can request topics. So it's not /all/ "push".

I think there's expected to be a lot of overlap with the
existing material in the PLRM, blue book, FAQs, that Paul Bourke
tutorial that's easy to find with google, .... The only specific
thing I have so far is that trick to fake Small Caps by applying
a matrix to regular caps. Not the most thrilling (or typographically
sound) thing to want to do, but that's what popped in my head, fwiw.


[1] Similar to the method of passing the deserts of
Arrakis 'without rhythm' so as not to summon a Worm,
performing a voting spree (aka "love fest") on SO
involves a very slow process of waiting 10-15 min
between votes and visiting other parts of the site
to ward-off the eye of the vote-fraud detection scripts.
cf. http://meta.stackexchange.com/questions/114404/i-got-enough-votes-yesterday-for-a-mortarboard-today-still-mortarboard-but-no

[toc] | [prev] | [next] | [standalone]

#2770

On Sunday, August 14, 2016 at 9:46:23 AM UTC+12, luser droog wrote:
> The only specific thing I have so far is that trick to fake Small Caps by
> applying a matrix to regular caps.

You need OpenType font features <http://default-cube.deviantart.com/art/Font-Features-626399449>.

[toc] | [prev] | [next] | [standalone]

#2790

On Tuesday, 9 August 2016 17:42:24 UTC+1, luser droog  wrote:
> We need 2 more committers to the Documentation part to
> start contributing examples.

I invited Kurt Pfeifle who has taken the bait, so the topic is now open...

Thanks Kurt.

[toc] | [prev] | [next] | [standalone]

#2795

On Wednesday, August 24, 2016 at 8:22:54 AM UTC-5, Terry Burton wrote:
> On Tuesday, 9 August 2016 17:42:24 UTC+1, luser droog  wrote:
> > We need 2 more committers to the Documentation part to
> > start contributing examples.
> 
> I invited Kurt Pfeifle who has taken the bait, so the topic is now open...
> 
> Thanks Kurt.

Cool. I wrote some stuff. Awaiting review.

[toc] | [prev] | [next] | [standalone]

#2796

On Saturday, August 27, 2016 at 11:13:47 PM UTC-5, luser droog wrote:
> On Wednesday, August 24, 2016 at 8:22:54 AM UTC-5, Terry Burton wrote:
> > On Tuesday, 9 August 2016 17:42:24 UTC+1, luser droog  wrote:
> > > We need 2 more committers to the Documentation part to
> > > start contributing examples.
> > 
> > I invited Kurt Pfeifle who has taken the bait, so the topic is now open...
> > 
> > Thanks Kurt.
> 
> Cool. I wrote some stuff. Awaiting review.

Still waiting for it to be reviewed.

[toc] | [prev] | [next] | [standalone]

#2797

On Thursday, September 1, 2016 at 2:19:13 AM UTC-5, luser droog wrote:
> On Saturday, August 27, 2016 at 11:13:47 PM UTC-5, luser droog wrote:
> > On Wednesday, August 24, 2016 at 8:22:54 AM UTC-5, Terry Burton wrote:
> > > On Tuesday, 9 August 2016 17:42:24 UTC+1, luser droog  wrote:
> > > > We need 2 more committers to the Documentation part to
> > > > start contributing examples.
> > > 
> > > I invited Kurt Pfeifle who has taken the bait, so the topic is now open...
> > > 
> > > Thanks Kurt.
> > 
> > Cool. I wrote some stuff. Awaiting review.
> 
> Still waiting for it to be reviewed.

Would someone please review my changes? I'm not inclined
to write any more until I see something go through.

http://stackoverflow.com/documentation/proposed/changes/92384
http://stackoverflow.com/documentation/proposed/changes/91645

[toc] | [prev] | [next] | [standalone]

#2798

On Monday, September 5, 2016 at 11:08:05 PM UTC-4, luser droog wrote:
> http://stackoverflow.com/documentation/proposed/changes/92384

Is there any way to form a preference between the currentpoint test your document and the one Peter mentioned?

 { currentpoint } stopped { ...  % no
  } {                pop pop ...  % yes
  } ifelse 

> http://stackoverflow.com/documentation/proposed/changes/91645 

In section 3, I think sentence fragments read badly.  (And I'd like to see more references in general.)

On installation and setup, I think simply pointing to existing instructions may be preferable to replicating them.  That will make it easier to refer to other interpreters (including yours) without creating a mess.

The section on error handling should probably mention ehandler.ps.

Thanks!

[toc] | [prev] | [next] | [standalone]

#2799

On Tuesday, 6 September 2016 18:24:40 UTC+1, Alan  wrote:
> Is there any way to form a preference between the currentpoint test your document and the one Peter mentioned?

If the boolean output of is-there-a-currentpoint is going to be passed to ifelse, they are equivalent. 

But perhaps something else is to be done with it, such as being used by def? If so, 
	{currentpoint pop pop} stopped not  % bool
is more robust than
	{currentpoint} stopped {…} {… pop pop} ifelse  % -

[toc] | [prev] | [next] | [standalone]

#2800

On Tuesday, September 6, 2016 at 12:24:40 PM UTC-5, Alan wrote:
> On Monday, September 5, 2016 at 11:08:05 PM UTC-4, luser droog wrote:
> > http://stackoverflow.com/documentation/proposed/changes/92384
> 
> Is there any way to form a preference between the currentpoint test your document and the one Peter mentioned?
> 
>  { currentpoint } stopped { ...  % no
>   } {                pop pop ...  % yes
>   } ifelse 
> 
> > http://stackoverflow.com/documentation/proposed/changes/91645 
> 
> In section 3, I think sentence fragments read badly.  (And I'd like to see more references in general.)

Yes. I wiffle-waffle between that and "... : ... ; ... ; ...."
I think I felt that I needed a third item to use the one-sentence form. 
But the second one is so general that I couldn't think of a third.
Maybe bullet points would smoothe-over the fragmentary nature.

> On installation and setup, I think simply pointing to existing instructions may be preferable to replicating them.  That will make it easier to refer to other interpreters (including yours) without creating a mess.
> 

That is an excellent suggestion.

> The section on error handling should probably mention ehandler.ps.
> 
> Thanks!

Indeed. Thank You. I'll fire up some google tabs.

[toc] | [prev] | [next] | [standalone]

#2801

On Tuesday, September 6, 2016 at 12:24:40 PM UTC-5, Alan wrote:
> On Monday, September 5, 2016 at 11:08:05 PM UTC-4, luser droog wrote:
> > http://stackoverflow.com/documentation/proposed/changes/92384
> 
> Is there any way to form a preference between the currentpoint test your document and the one Peter mentioned?
> 
>  { currentpoint } stopped { ...  % no
>   } {                pop pop ...  % yes
>   } ifelse 
> 

I agree with jdaw's comments. If you're doing wildly different behaviors,
and really need the value in the true case, then it's silly to pop them
only to call for them again. But since I put the example under the topic
of Error Handling, I wanted it to clean up after itself.

In the places where I've used this, it has only been to choose between
moveto and lineto. I think it evolved into this form from something
closer to Peter's example. But I'd choose depending upon whether the
values are needed.

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.postscript

csiph-web