1 
  2 09/21/87  compose
  3 Known errors in the current release of compose.
  4 #         Associated TR's
  5 Description
  6 
  7 1151
  8 The paragraph macros (..p0, etc.)  mishandle pending undents when
  9 interacting with table mode.
 10 
 11 1150
 12 In order to improve performance, various pdir database initialization
 13 statements are controlled by the -debug option switch.  One such
 14 controlled initialization step causes "loaner" charsets to be not
 15 loaded and leads to null pointer fault failures in x9700_writer_.
 16 
 17 1149
 18 If an output line in font A begins with ".ur %.fnt B%X ..." where X is
 19 borrowed from font A, X does not appear in the output.
 20 
 21 1148
 22 The underscore character is missing from the fonts used for level 0 and
 23 level 1 headers.
 24 
 25 1147
 26 The left and right double quotes characters are missing in the fonts
 27 used for level headers.
 28 
 29 1146
 30 If a font contains both borrowed and native characters, and the
 31 borrowed characters are given first, the wrong character set index
 32 value is emitted for the native characters.
 33 
 34 1145
 35 Compdv references an obsolete variable when calculating the size of a
 36 font size table.
 37 
 38 1144
 39 Certain short lines at the ends of paragraphs do not have change bars
 40 even though change bars are active.
 41 
 42 1143
 43 In certain cases, the presence of a .hit control in a compin file
 44 destroys the output format in galley mode by trying to emit page header
 45 slugs.
 46 
 47 1142
 48 If the first line in a block has a hanging undent, the x9700 module
 49 neglects to set the character set pointer and fails with a null pointer
 50 fault.
 51 
 52 1141
 53 In some cases, the program fails to detect an attempt to pop an empty
 54 font stack and fails with an indeterminant error caused by garbage
 55 being pointed to by an invalid pointer variable.
 56 
 57 1140
 58 Attempts to place text titles in keep blocks after table mode has been
 59 used (and properly exited) in the block fail with the subscriptrange
 60 error in comp_title_block_.
 61 
 62 1139
 63 Version mismatch problems were found in >exl>cd>macros>old.(l1h tab
 64 toc).compin.  They have been reinstalled.
 65 
 66 1138
 67 Artwork lines are not correctly counted in filled text.  This causes
 68 occasional failure to expand artwork when .bba N is used in filled
 69 text.
 70 
 71 1137  phx19820
 72 When switching from filled to unfilled text in the middle of a block,
 73 if the last line of filled text consists of nothing but a font change
 74 string, it is properly discarded, but the desired font change does get
 75 propagated to the first unfilled line.
 76 
 77 1136  phx19819
 78 A text <title> given in and intended for a table column, gets placed
 79 with the wrong margin values.
 80 
 81 1135
 82 Printwheel changing for the hyterm device is broken.
 83 
 84 1134  phx19665
 85 The version of compdv.incl.alm in >exl>cd>include isnt the version
 86 expected by >exl>cd>e>compdv.
 87 
 88 1133  phx19663 phx19664
 89 A zealous user has discovered several instances of illegal PL/I that
 90 are potential problem points.
 91 
 92 1132  phx19639
 93 The program fails when attempting to attach an unreferenced footnote to
 94 a text title block.
 95 
 96 1131  phx19964
 97 Under the "right" conditions, the program inserts hyphens into hanging
 98 undent fields.
 99 
100 1130
101 See #1129.  The same problem occurs with other file accessing errors,
102 such as no_r_permission or zero_length_seg.
103 
104 1129  phx19632
105 If compose is invoked with -pass 2 and an insert file is found to not
106 exist during pass 1, its name is not erased from the insert file
107 database and, during pass 2, finding that bogus insert file name causes
108 a failure with a subscriptrange error in comp_get_file_.
109 
110 1128  phx19630 phx19823
111 When an existing block is converted to a table block (.tan control) and
112 processing is sent to an unfilled table column (.tac control), the text
113 alignment mode (left/center/right/etc.)  for that table column isnt
114 propagated correctly.
115 
116 1127  phx19629
117 If a return (.rt) control is encountered within a conditional execution
118 group (.if/.endif) in a file given in the command line, the processing
119 of the file is aborted correctly but an extraneous error message
120 complains of nontermination of the conditional execution group.
121 
122 1124  phx19624
123 Font changes given between contiguous title lines (eg, .thl .../.fnt
124 A/.thl ...)  have no effect.
125 
126 1123  phx19550 phx14849 phx19860 phx19881
127 This entry is a "catchall" so as to provide a place to record TR
128 reported problems that can no longer be reproduced with DEV compose and
129 must be presumed fixed in the course of development.
130 
131 1122  phx19547
132 The merging of table entry lines at the same page depth is done at the
133 wrong place in the flow of processing.  Because of this, tables
134 inserted into embedded keeps are badly malformatted, and can cause
135 program aborts and fatal process errors.
136 
137 1121  phx19546
138 If .brp is given with "e" or "o" and the page number must be
139 incremented, the change takes place one page too late.
140 
141 1120  phx19545
142 "Popping" an empty font stack with ".fnt " (note the trailing blank)
143 causes a failure with a subscriptrange error.
144 
145 1119  phx19516
146 A footnote given in a short (<= twice the widow size) block is lost
147 when that block appears at the bottom of the page and *would* fit
148 without the note.
149 
150 1118
151 When the .wrt control is given a <path> longer than 32 characters, only
152 the first 32 are trimmed and rest get written to the target file.
153 
154 1117
155 If the .spd control is used to end a text block, the space used by that
156 block isnt counted and too much white space is inserted.
157 
158 1116
159 If the addition of a text line to a page signals a page overflow and
160 subsequent trimming of leading whitespace on that page allows the
161 remaining text to fit, the page is ejected anyway and the program fails
162 with a null pointer fault in comp_break_ on the next page.
163 
164 1115  phx19521
165 The program fails to diagnose an attempt to redefine columns within a
166 keep block and produces badly mangled output.  This attempt must be a
167 limitation since the program cannot know how the user intends the
168 subsequent text to be placed on the page.  A diagnostic message has
169 been added.
170 
171 1114  phx19495
172 The vip7801_writer_ module fails with a null pointer fault due to
173 improper output image initialization.
174 
175 1113  phx19482
176 All device writer modules fail with a null pointer fault when asked to
177 prepare an output page image with more than 32640 lines.
178 
179 1112
180 If a page contains only trimmable white space, the space is trimmed but
181 the page is left marked as already headed.  This can cause the next
182 page to have the wrong page number if that next page starts a new
183 section of a document (ie, it has a different page number structure).
184 
185 1111  phx19349
186 When the break-column (.brc) control is used to move from one column to
187 another on a multicolumn page, the space needed to fill out the current
188 column is added twice.  This causes the target column to start too low
189 on the page.
190 
191 1110  phx19426
192 Changes made for error 1104 have caused conditional execution group
193 (.if/.endif controls) nesting levels to be miscounted when processing
194 labels (.go and .la controls).  This causes error messages and macro
195 logic failures.
196 
197 1109
198 For the x9700 device, font characters that are "borrowed" from another
199 character set are not displayed.  Further, if there are explcit font
200 changes in the same line as the borrowed characters that invoke the
201 "borrowed from" character set, the x9700 module loops.
202 
203 1108
204 The apparent absence of the EMspace character in the X9700 character
205 set that supports the 'ascii' (aka 'typ') font causes lines using those
206 fonts to be mispositioned and/or overprinted.
207 
208 1107
209 For the x9700 device, if an output line has a left margin change mark,
210 has NO internal font changes, is longer than the hardware linelength
211 limitation (thus requiring an extension overlay for correct printing),
212 AND the first line of the text block also has a left margin change bar,
213 the extension overlay for the line is emitted with the font select
214 character for the left margin font of that first line.  This causes
215 certain extension overlays to be printed in the wrong font.
216 
217 1106  phx19310
218 The x9700_un gives the wrong value in the declaration of pixel size.
219 This causes positioning discrepancies when user given horizontal length
220 values (eg, .inl 3) are adjusted for device resolution.
221 
222 1105  phx19299
223 If the addition of a text line to the output page triggers a page
224 overflow event and the trimming of leading white space results in a
225 short page, the next input text line fails with a null pointer fault in
226 comp_.
227 
228 1104  phx19282
229 The limitation on use of .go exiting a conditional execution group isnt
230 properly diagnosed and reported.  Remove the limitation.
231 
232 1103  phx19272
233 A free standing picture that doesn't fit on the current page is placed
234 differently than an identical picture at the same page position that's
235 given within a text block.
236 
237 1102  phx19265
238 The program fails to detect and diagnose violations of the limit on
239 nesting of conditional execution groups (.if ...  .endif controls) and
240 fails with a subscriptrange condition.
241 
242 1101  phx19260
243 Differences in the declared length of two character string variables
244 cause failure with a stringrange error for the 101st label in a compin
245 file.
246 
247 1100  phx19239
248 The program is unable to handle zero widow size (.wi 0 control) and
249 fails trying to split a one line block.  The usual error is a
250 subscriptrange condition.
251 
252 1099  phx19248 phx19247
253 The program attempts to do preliminary syntax checking on active
254 strings (eg, %[string a b c]%) and sometimes makes egregious errors.
255 This prechecking is a leftover from an ancient cu_ interface and has
256 been removed.
257 
258 1098  phx19246
259 The text alignment mode (left, center, etc.)  isnt handled properly
260 when switching table mode formats.  This causes certain table lines to
261 be malformatted.
262 
263 1097
264 <title> lines in footnotes are not handled properly.
265 
266 1093
267 Extensive use of page header/footer redefinition by individual line
268 index numbers (eg, use of ".hla N ..." when there is already a page
269 header) in big files can result in a record-quota-overflow in the
270 process_directory.  Use of this feature should be limited to only those
271 places where it is absolutely necessary.
272 
273 1085  phx19068 phx19288
274 In some cases when the amount of text to be placed on a multicolumn
275 page is very small, the column balancing algorithm produces remarkably
276 poor output.
277 
278 1068  phx19125
279 If frob.compout is an addname on frob.compin, 'compose frob -of' fails
280 with a stringrange error when trying to report the input file overwrite
281 situation.
282 
283 985  phx15911
284 The artwork feature is limited to ONLY straight lines (horizontal,
285 vertical, and slanted), boxes, diamonds, and lozenges.  Any more
286 general graphic constructs such as 8-sided polygons and some 6-sided
287 polygons, and random combinations of line segments are not supported
288 and will not yield the desired results.
289 
290 946  phx15466
291 File content-dependent fields in page headers on multi-column pages are
292 not accurately shown because the page make-up process is asynchronous
293 with the text input stream.
294 
295 939
296 Input files with names of the form FOO.compin.compin are unacceptable.
297 
298 875  phx14759
299 The program is overzealous in "protecting" (escaping) the special
300 syntax characters (eg, quotes, asterisks,...)  in lines read by the
301 LineInput builtin.  This makes the passage of control lines with
302 variable fields through the interface virtually impossible.
303 
304 831  phx14380
305 When a titled picture block is inserted into a titled paragraph, the
306 page numbers for both may appear incorrectly in the TOC.
307 
308 824  phx14034 phx15334
309 The program does not allow mixing of held and printed footnotes in the
310 same document.
311 
312 759  phx11480
313 Table mode in special blocks (page headers, text headers, etc.)  is
314 mishandled.  This problem is classed as a limitation because it would be
315 very difficult to extend table mode into headers block and the probable
316 utility of doing so is judged quite small.