summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/generic/pstricks/pstricks.bug
blob: 247cd7dee599d47ee26d0163d7bd490742a26d45 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
%% BEGIN pstricks.bug
%%
%% Last modified: March 15, 2000
%%
%% This file list some bugs and latebreaking news for PSTricks 97
%%
%% This file is edited by Denis Girou <Denis.Girou@idris.fr>
%% and Sebastian Rahtz <sebastian.rahtz@computing-services.oxford.ac.uk>
%%

\def\fileversion{97 patch 5}
\def\filedate{2000/03/15}

\message{ v\fileversion, \filedate}

% PROBLEMS:

% 1. Inside the psmatrix environment, we can't use a parameter for the first
%    column definition if it's not the first row.
%    Reported by <Denis.Girou@idris.fr> in 1995.
%
%    It's a parsing problem, as the parser wait something like [3mm] after the
%    \\ and not something like [name=B].
%
%    In fact, this is the "standard" way in which LaTeX work, and this is
%    the same for the "tabular" environment, for instance.
%
%    Test file:
%
%    \documentclass{article}
%
%    \usepackage{pstricks}
%
%    \begin{document}
%    \begin{psmatrix}
%      [name=A] A \\
%      [name=B] B
%    \end{psmatrix}
%    \end{document}
%
%    Workaround: add [0pt] after the \\ in these cases:
%
%      [name=A] A \\[0pt]
%      [name=B] B

% 2. With the `french' package, there is a problem with the special
%    < and > characters used for diagram and tree annotations (they are
%    not correctly typed nor positioned).
%    N.B. This problem doesn't occur with the frenchb sub-option of the
%    `babel' package.
%    Reported by Philippe Esperet <pesperet@compuserve.com> in October 1996.
%
%    Test file:
%
%    \documentclass{article}
%
%    \usepackage{pstricks}
%    \usepackage{pst-node}
%    \usepackage{french}
%
%    \begin{document}
%    \begin{psmatrix}
%      E&F\\
%      G&H
%      \ncline{1,1}{1,2}^w
%      \ncline{2,1}{2,2}_f
%      \ncline{1,1}{2,1}<u
%      \ncline{1,2}{2,2}>v
%    \end{psmatrix}
%    \end{document}
%
%    Workaround: put the `psmatrix' environment inside an `english' one

% 3. When arrows are required, this change the way the curves are drawn.
%    In fact, the modification is small, and we must be very careful
%    to see that, but this effect can be clearly demonstrated if we
%    surimpose a grid. And it can be specially ennoying for Bezier curves.
%    Reported by Thomas Siegel <siegel@aix520.informatik.uni-leipzig.de>
%    in September 1997.
%
%    When an arrow is defined, the point used to draw line or curve is
%    the entry of the arrow, and no more the defined point itself.
%    It is difficult to say if it is a "bug or a feature" (seems rather
%    a bug for me - D.G.)
%
%    Test file:
%
%    \documentclass{article}
%
%    \usepackage{pstricks}
%
%    \pagestyle{empty}
%
%    \begin{document}
%
%    \begin{pspicture}(4,2)
%      \psgrid
%      \psdot*(1,1)
%      \psdot*(3,1)
%      \psset{arrowinset=0}
%      \psbezier[showpoints=true]{->}(1,1)(0,2)(4,2)(3,1)
%      \psbezier[showpoints=true]{<-}(1,1)(0,0)(4,0)(3,1)
%    \end{pspicture}
%
%    \vspace{1cm}
%    \begin{pspicture}(4,2)
%      \psgrid
%      \psdot*(1,1)
%      \psdot*(3,1)
%      \psbezier[showpoints=true](1,1)(0,2)(4,2)(3,1)
%      \psbezier[showpoints=true](1,1)(0,0)(4,0)(3,1)
%    \end{pspicture}
%    \vspace{2cm}
%
%    \begin{pspicture}(0,-2)(4,3)
%      \psbezier[arrowsize=2]{->}(1,1)(0,2)(4,2)(3,1)
%      \psbezier[arrowsize=2]{<-}(1,1)(0,0)(4,0)(3,1)
%    \end{pspicture}
%
%    \begin{pspicture}(0,-2)(4,3)
%      \pscurve[arrowsize=2]{->}(1,1)(0,2)(4,2)(3,1)
%      \pscurve[arrowsize=2]{<-}(1,1)(0,0)(4,0)(3,1)
%    \end{pspicture}
%
%    \clearpage
%
%    \makeatletter
%    % Version of the /Arrow macro which keep the coordinates of the point
%    % and doesn't used the entry of the arrow head for that
%    % (default was specially ennoying for \psbezier and when we use large
%    % value of arrowsize or arrowscale parameter)
%    % Work here on the current page
%    \pst@Verb{%
%    /Arrow { CLW mul add dup 2 div /w ED mul dup /h ED mul /a ED { 0 h T 1 -1
%    scale } if w neg h moveto 0 0 L w h L w neg a neg rlineto 
%    % DG modification begin - Sep. 25, 1997
%    0 0 moveto
%    % DG modification end
%    gsave fill grestore } def}
%    \makeatother
%
%    \begin{pspicture}(4,2)
%      \psgrid
%      \psdot*(1,1)
%      \psdot*(3,1)
%      \psset{arrowinset=0}
%      \psbezier[showpoints=true]{->}(1,1)(0,2)(4,2)(3,1)
%      \psbezier[showpoints=true]{<-}(1,1)(0,0)(4,0)(3,1)
%    \end{pspicture}
%
%    \begin{pspicture}(0,-2)(4,5)
%      \psbezier[arrowsize=2]{->}(1,1)(0,2)(4,2)(3,1)
%      \psbezier[arrowsize=2]{<-}(1,1)(0,0)(4,0)(3,1)
%    \end{pspicture}
%
%    \end{document}
%
%    Workaround: change the definition of the PostScript /Arrow macro,
%    as described above

% 4. The \savedata macro must not be used inside another macro.
%    In such case, the drawing commands, like \dataplot, will show nothing.
%    The problem is related to some catcode changes that can't be made,
%    and in fact a delimiter is not introduced after each point defined,
%    so the curve will have at the end only one point, the last one.
%    It is the reason why nothing is shown later by a macro like \dataplot.
%    Reported by Ivan Maio <maio@pol88a.polito.it> in October 1997.
%
%    Test file:
%
%    \documentclass{article}
%
%    \usepackage{pst-plot}
%
%    \pagestyle{empty}
%
%    \begin{document}
%
%    \begin{pspicture}(-2,-2)(2,2)
%      \savedata{\test}[%
%     -1.09 -0.55
%     -0.4  -0.1
%      0     1.02
%      1.28  0.06
%      1.51  1.21]
%      \dataplot{\test}
%      \psaxes{<->}(0,0)(-2,-2)(2,2)
%    \end{pspicture}
%
%    \vspace{1cm}
%    \psframebox{%
%    \begin{pspicture}(-2,-2)(2,2)
%      \savedata{\test}[%
%     -1.09 -0.55
%     -0.4  -0.1
%      0     1.02
%      1.28  0.06
%      1.51  1.21]
%      \dataplot{\test}
%      \psaxes{<->}(0,0)(-2,-2)(2,2)
%    \end{pspicture}}
%
%    \savedata{\test}[%
%     -1.09 -0.55
%     -0.4  -0.1
%      0     1.02
%      1.28  0.06
%      1.51  1.21]
%
%    \vspace{1cm}
%    \psframebox{%
%    \begin{pspicture}(-2,-2)(2,2)
%      \dataplot{\test}
%      \psaxes{<->}(0,0)(-2,-2)(2,2)
%    \end{pspicture}}
%
%    \end{document}
%
%    Workaround: do not use \savedata inside another macro, as shown in the
%    previous example

% 5. Moves (by \rput for instance) of objects defined using nodes have
%    no effect. The position is not affected by the translation required.
%    Reported by Thomas Siegel <siegel@aix520.informatik.uni-leipzig.de>
%    in February 1998.
%
%    Test file:
%
%    \documentclass{article}
%
%    \usepackage{pst-node}
%
%    \pagestyle{empty}
%
%    \begin{document}
%
%    \SpecialCoor
%
%    \begin{pspicture}(5,5)
%      \qdisk(5,0){2.5mm}
%      \qdisk(0,5){2.5mm}
%      \rput(1,1){\psline(5,0)(0,5)}
%    \end{pspicture}
%    \begin{pspicture}(5,5)
%      \Cnode*(5,0){f1}
%      \Cnode*(0,5){f2}
%      \rput(1,1){\psline(f1)(f2)}
%    \end{pspicture}
%
%    \end{document}
%
%    Workaround: none is known for the moment.

% 6. When two labels are required for a node connection, the second one is
%    incorrectly positioned when at least one of them use also node
%    connections.
%    Reported by Anthony Doggett <adoggett@uiuc.edu> in December 1999.
%
%    Test file:
%
%    \documentclass{article}
%    
%    \usepackage{pst-node}
%    
%    \SpecialCoor
%    
%    \pagestyle{empty}
%    
%    \begin{document}
%    
%    \newcommand{\Label}{%
%    \pnode(0,0){A}
%    \pnode(2,0){B}
%    \psline(A)(B)}
%    %
%    \pcline(0,0)(3,-3)\naput{\Label}\nbput{Label} % Correct pos. for "Label"
%    %
%    \renewcommand{\Label}{%
%    \pnode(0,0){A}
%    \pnode(2,0){B}
%    \ncline{A}{B}}
%    %
%    \hfill
%    \pcline(0,0)(3,-3)\naput{\Label}\nbput{Label} % Uncorrect pos. for "Label"
%    
%    \end{document}
%
%    Workaround: none is known for the moment (without bad side effects)

%%
%% END pstricks.bug