| Title: | DOCUMENT T1.0 |
| Notice: | **New notesfile (DOCUMENT.NOTE) now available (see note 897)** |
| Moderator: | CLOSET::ADLER |
| Created: | Mon Feb 09 1987 |
| Last Modified: | Thu Oct 31 1991 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 897 |
| Total number of notes: | 4397 |
V1.0 (BL9)
I've just noticed a problem using <ALIGN_CHAR> and - (hyphen).
In the following fragment, the only difference between the two
<TABLE_ROW> arguments is the elimination of - from the second
<TABLE_ROW>. The output of the second column for the two rows looks
something like:
0-1
1-2
2-3
3-4
01
12
23
34
This "bug" (almost looks like it could be used as a feature) shows
up using SOFTWARE doctype as well as LYNX doctypes with POST as
a destination. Couldn't try LN03 (broke).
<ALIGN_CHAR>(#)
<TABLE>(Wall Below Grade Losses\BTU_BWBGL)
<TABLE_SETUP>(4\5\5\6)
<FOOTNOTE>(1\BTU/hr/ft<superscript>(2)/<mcs>(degree)F (Clifford, pp 317))
<FOOTNOTE>(2\SWAG)
<TABLE_HEADS>(Section\Feet Below Grade\BTU<FOOTREF>(1)\Totals)
<TABLE_ROW>(\#0-1
<LINE>#1-2
<LINE>#2-3
<LINE>#3-4
\0.410
<LINE>0.222
<LINE>0.155
<LINE>0.119\)
<TABLE_ROW>(\#01
<LINE>#12
<LINE>#23
<LINE>#34
\0.410
<LINE>0.222
<LINE>0.155
<LINE>0.119\)
<ENDTABLE>
<ENDALIGN_CHAR>
Joe
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 775.1 | Bug in Postscript hyphen (-) | CLOSET::ANKLAM | Tue Aug 11 1987 11:26 | 7 | |
See also 754 and 755. There is a bug (or several tiny bugs) in
the POSTSCRIPT fonts that are causing some erratic spacing. We'll
try to update you when we've nailed the problem down.
patti
| |||||
| 775.2 | Change 0-1 to 0--1 | VAXUUM::SEGAL | Tue Aug 11 1987 12:09 | 8 | |
Joe,
As a workaround, you can correct the alignment in the table
by using two successive dashes instead of one dash. This will
produce an endash for all devices, and will eliminate the
skewing caused by the misbehaving hyphen in PostScript output.
Gotta dash, Lee
| |||||
| 775.3 | An explanation | VAXUUM::DEVRIES | M.D. -- your Device Doctor | Tue Aug 11 1987 13:49 | 24 |
Yup, the problem is in the hyphen-that-comes-out-as-an-endash. In
DEC Multinational Character Set, character 45 (decimal) is called
"minus". This term dates from VT100s, etc., where minus and hyphen
are interchangeable terms.
But in the proportional spaced world of PostScript, minus is the
thing you use with numerals (which are often an "en" wide), so "minus"
gets you an endash. What you wanted here was a hyphen, and what
TeX counted was the width of a hyphen -- but PostScript was ultimately
told to put out a different character, "minus", which is wider.
This means what is printed is slightly different from what the
formatter asked for.
The problem will be fixed in the next version. In the meantime,
if you don't want to code each row of the table as a separate row,
Lee's workaround in .2 will at least get you sensible output, even
though it's not perfect.
FYI: As it happens the same problem occurs with hyphens used for
line breaks. So if you see a PostScript line hanging out
in the margin, but get no line-too-long errors, see if the line
contains these "long hyphens".
--Mark
| |||||
| 775.4 | Help is on the way -- it's here now, even. | VAXUUM::DEVRIES | M.D. -- your Device Doctor | Tue Aug 11 1987 16:33 | 20 |
> The problem will be fixed in the next version.
(My, they're building versions closer and closer together.)
For the fix you need, copy from VAXUUM or CLOSET this file:
KITS_:[DOCUMENT.V10]DVC$PROLOG.PS
into your VAX DOCUMENT directory identified by the logical:
DOC$PS_FONTS
This will cause the PostScript files you create from then on to
print out the skinny hyphen whenever you enter a single hyphen ('-')
into your source file; this is also the hyphen you'll get when
words are hyphenated. Thus the PostScript behavior will be consistent
with that of the LN03 support.
--Mark
| |||||