| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 130.1 | will check | CLOSET::ANKLAM | | Fri Mar 20 1987 12:37 | 9 |
|
1. we will check on the POSTSCRIPT characters.
2. a line extends from one column into the next when the column
width is too short (for example, one long word on a line by itself)
is that what it is?
patti
|
| 130.2 | | SARAH::P_DAVIS | Peter Davis, X-NYer | Fri Mar 20 1987 13:13 | 10 |
| This table is the bibliography that I referred to in a note in the
DOCUMENT notes file. The left column is 8, so the right is, I guess,
52. What's happening is that text that should be in the right column
is wrapping around into the left. What's really peculiar is that
it's only happening in one line, whereas the rest of the page and
a half table contains multi-line entries which wrap correctly.
If you're interested, you can copy the file from
SARAH::USER3:[PDAVIS]REFERENCES.GNC
|
| 130.3 | an extra paren | CLOSET::ANKLAM | | Fri Mar 20 1987 13:59 | 25 |
|
The problem is unbalanced quotation marks. An extra ) in a table row
effectively terminates that row. The subsequent text is printed 'outside
the row' or over at the left margin. I changed:
<TABLE_ROW>(BRES65\Bresenham, J. E., <QUOTE>(Algorithm for Computer Control of
a Digital Plotter,) IBM System Journal, 4<OPAREN>1<CPAREN>), 1965, pp. 25-30.)
to:
<TABLE_ROW>(BRES65\Bresenham, J. E., <QUOTE>(Algorithm for Computer Control of
a Digital Plotter,) IBM System Journal, 4 (1), 1965, pp. 25-30.)
note the culprit was <oparen>1<cparen>) which was read as (1))
Another note: I see a lot of files in which people are using <oparen> and
<cparen> in places where they are not needed. The above is one instance.
<oparen> and <cparen> are almost never paired. They are required *only*
when both of the following are true:
1. they are part of text that is specified in an argument to a tag
2. they are not matched
--patti
|
| 130.4 | | SARAH::P_DAVIS | Peter Davis, X-NYer | Sat Mar 21 1987 13:11 | 11 |
| Thanks. I had just discovered the extra ")", and was just going
to enter my apology here.
By the way, I used <OPAREN> and <CPAREN> because the text is actually
part of the argument to the <TABLE_ROW> tag. However, it may be
that that's not necessary. I guess the parser is smart enough to
detect a "(" within a tag argument, and maintain a nesting level.
That would explain why only unbalanced parens need tagging.
Thanks.
-pd
|
| 130.5 | matched parens inside args okay | CLOSET::ANKLAM | | Mon Mar 23 1987 09:07 | 5 |
|
That's right. The tag translator does fine with nested parens, as
long as they are evenly matched. You are the second engineer who
second-guessed the use of these tags inside arguments, only to
find out that the tag translator was smarter than you thought!
|
| 130.6 | | SARAH::P_DAVIS | Peter Davis, X-NYer | Mon Mar 23 1987 10:35 | 7 |
| One other problem I've had is that an expression like
<QUOTE>(<MATH_SYMBOL>(CUP))
printed with the opening quote at the end of a line, and the math
symbol and closing quote at the start of the next line. This seems
kind of weird to me.
|
| 130.7 | 'nother small bug | CLOSET::ANKLAM | | Mon Mar 23 1987 18:05 | 4 |
|
yes, I am looking at that.
patti
|