| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 216.1 | you could do a doctype | CLOSET::ANKLAM | | Thu Apr 09 1987 16:07 | 7 |
|
There must be something in the planets...I was asked this just
yesterday, and it was the first time in 3 years! I'll put that on
the list for 'minor enhancements' in the next version.
patti
|
| 216.2 | What to modify? | COOKIE::JOHNSTON | | Thu Apr 09 1987 18:59 | 11 |
| Which command in the .dtp file needs to be modified, and how?
I don't want anything more than double spacing for sentences contained within
paragraphs. Since new paragraphs are already double-spaced, and sometimes
not indented, an extra line before them or indenting would
be necessary to set the paragraphs off from other double-spaced text. Long
and windy, but I think you know what I mean.
Thanx
Rose
|
| 216.3 | baselineskip | CLOSET::ANKLAM | | Fri Apr 10 1987 08:53 | 8 |
|
I have never done it, but if I were to try what I would do is
\def\normaltextfontspecs{\tenpoint\baselineskip=22pt}
In other words, in whatever fonts are affected, just up the
baselineskip.
|
| 216.4 | Another vote | SARAH::P_DAVIS | Peter Davis, X-NYer | Fri Apr 10 1987 12:37 | 4 |
| I asked for this same feature in the DOCUMENT notes file, just to
add another vote. I'm not ready to start creating my own doctypes
yet, but this seems common enough that there should be pre-defined
ways to to it.
|
| 216.5 | PRINT/SPACE works for Draft Output Devices | CLOSET::ETZEL | Mike | Mon Apr 13 1987 15:42 | 8 |
| Try PRINT/SPACE to get double-spacing for an .LPR file (LINE), .TXT
file (MAIL), and .TT (TERMINAL). I don't think it works for other
devices.
Of course, you can specify it in the DOCUMENT command line:
DOCU/PRINT=(SPACE,NOTIFY) ...
|
| 216.6 | WARNING WARNING, Kludge approaching on vector... | BUNSUP::LITTLE | Todd Little NJCD SWS 323-4475 | Fri Apr 17 1987 14:28 | 31 |
| You can do as Patti suggests without creating a new doctype. All you
need is a <INCLUDE_TEX_FILE> tag in your GNC file and have the included
file contain the line modified from the design that defines the normal
font specification. The line as Patti gives it should work for most
designs.
\def\normaltextfontspecs{\tenpoint\baselineskip=22pt}
If you're concerned about making paragraghs easier to find then you can
also change:
\paravskip=36pt
\cparavskip=36pt
or some similar value.
I suspect to make it easier for your users, you could place the
<INCLUDE_TEX_FILE> tag in your symbol definition file if you have
one, and if not, just create a symbol definition file that includes
the tag. Your users can just say:
$ DOCUMENT/SYMBOL=DOUBLE-SPACE filename doctype destinition
Lastly, I agree that this would be a nice feature for DOCUMENT to
support directly. Would probably require a great many changes though
to support it "properly".
-tl
|
| 216.7 | might bite you ... | VAXUUM::SEGAL | | Fri Apr 17 1987 15:30 | 9 |
| Simply including TeX control sequences into a source file
won't always produce the expected result. You can define
the normal text font to be anything you like, but unless
you put the change into the design file your redefinition
will have no impact on the document until/unless
\normaltextfontspecs is actually invoked.
Lee
|