| 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 |
Any suggestions for generating <CODE_EXAMPLE>
and <FORMAT> type output for overhead slides? The
typeface generated by these tags is too small.
Eileen
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 434.1 | Use <text_size> after <code_example> | COOKIE::JOHNSTON | Thu May 28 1987 16:16 | 18 | |
Enclose <text_size> and <endtext_size> between the <code_example> and <endcode_example>, such as: <code_example> <text_size>(table) This demonstrates that text size must be changed inside of an example if you want to control text size in an overhead. <endtext_size> <endcode_example> The order of the tags is important; <text_size> outside of the example will have no effect. Rose | |||||
| 434.2 | CUP overheads? | VAXUUM::SEGAL | Thu May 28 1987 17:26 | 11 | |
Default monospace for OVERHEADS is 16point courier.
I suspect your cluster is using a local doctype version of
OVERHEADS that replaces the courier with AMTT monospace,
which isn't available in a larger size. Use of <TEXT_SIZE>
will not result in a monospaced font even if used
within the bounds of <code_example>, <syntax>, <display>, etc.
Will change the fonts for format used in text on OVERHEADS--thanks
for catching that one.
Lee
| |||||