[pstricks] PSTricks Digest, Vol 133, Issue 14

Donut E. Knot the.counterterrorist at yahoo.com
Mon Feb 24 07:36:57 CET 2014


Thanks Jean for responding.

1. Why does \SpecialCoor break the compatibility in your case where you have PostScript expression in your old files? In my opinion, \SpecialCoor will enable PostScript expression in our files so what is wrong?

4. The introduction to !!CP syntax is available in pst-news13.pdf. You can locate this file by typing "texdoc pst-news13" (of course excluding the quotes) from your terminal or DOS prompt or whatever.


Thank you.


best regards,


The Last Error
(http://tex.stackexchange.com/users/19356)



On Monday, February 17, 2014 6:01 PM, "pstricks-request at tug.org" <pstricks-request at tug.org> wrote:
 
Send PSTricks mailing list submissions to
    pstricks at tug.org

To subscribe or unsubscribe via the World Wide Web, visit
    http://tug.org/mailman/listinfo/pstricks
or, via email, send a message with subject or body 'help' to
    pstricks-request at tug.org

You can reach the person managing the list at
    pstricks-owner at tug.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of PSTricks digest..."


Today's Topics:

   1. Feature request and suggestion (Donut E. Knot)
   2. Re: Feature request and suggestion (Jean-C?me Charpentier)


----------------------------------------------------------------------

Message: 1
Date: Sun, 16 Feb 2014 04:47:39 -0800
From: "Donut E. Knot" <the.counterterrorist at yahoo.com>
To: PSTricks <pstricks at tug.org>
Subject: [pstricks] Feature request and suggestion
Message-ID:
    <1392554859.81063.YahooMailNeo at web162603.mail.bf1.yahoo.com>
Content-Type: text/plain; charset="iso-8859-1"

Dear folks,

I have 3 ideas, probably they are good for us.

1. In this decade computers??with good performance?become cheaper and cheaper, so I think enabling \SpecialCoor by default will not be an issue. It will not break compatibility as well. What do you think?

2. Why doesn't pstricks.sty load indispensable multido by default?

3. \psrline should be moved to pstricks.sty.

4. !!CP should be deprecated because the syntax?with two exclamation marks?is a bit inconsistent and abnormal. ?I suggest the following.
\makeatletter

\pstVerb
{
/CPxy {CP \tx at UserCoor} def
/CPx {CPxy pop} def
/CPy {CPxy exch pop} def
}
\makeatother


Thank you for your consideration and I am sorry if my suggestion sounds offensive.

Best regards,

The Last Error
(http://tex.stackexchange.com/users/19356)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tug.org/pipermail/pstricks/attachments/20140216/c2bef2a2/attachment-0001.html>

------------------------------

Message: 2
Date: Sun, 16 Feb 2014 15:34:24 +0100
From: Jean-C?me Charpentier <jean-come.charpentier at wanadoo.fr>
To: <pstricks at tug.org>
Subject: Re: [pstricks] Feature request and suggestion
Message-ID: <5300CC70.7090408 at wanadoo.fr>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed

Le 16/02/2014 13:47, Donut E. Knot a ?crit :
> Dear folks,
>
> I have 3 ideas, probably they are good for us.
>
> 1. In this decade computers with good performance become cheaper and
> cheaper, so I think enabling \SpecialCoor by default will not be an
> issue. It will not break compatibility as well. What do you think?

   It will break compatibility and it will be horrible for me (and some 
other people). Please Herbert, don't change that! :-)
   If you change this behaviour, I have to recode all my files which use 
PostScript expression... and I will be not very happy.

> 2. Why doesn't pstricks.sty load indispensable multido by default?

   It is not as indispensable as you think but your question is more 
acceptable that the first one. Do you know about pst-all? It loads 
multido (amongs other pstricks packages).

> 3. \psrline should be moved to pstricks.sty.

   I don't know what decide Herbert to move something from pstricks-add 
to pstricks (.tex, not .sty) but it's not a good idea to move things too 
quickly. Remember that people haven't the last package version and then 
could have compatibility problems.

> 4. !!CP should be deprecated because the syntax with two exclamation
> marks is a bit inconsistent and abnormal.  I suggest the following.
> \makeatletter
> \pstVerb
> {
> /CPxy {CP \tx at UserCoor} def
> /CPx {CPxy pop} def
> /CPy {CPxy exch pop} def
> }
> \makeatother

   I don't know the syntax !!CP. What's that?

> Thank you for your consideration and I am sorry if my suggestion sounds
> offensive.

   I don't think there is something offensive here.

   Jean-C?me Charpentier


------------------------------

Subject: Digest Footer

_______________________________________________
PSTricks mailing list
PSTricks at tug.org
http://tug.org/mailman/listinfo/pstricks


------------------------------

End of PSTricks Digest, Vol 133, Issue 14
*****************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tug.org/pipermail/pstricks/attachments/20140223/39919390/attachment.html>


More information about the PSTricks mailing list