| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 613.1 | Here's the fix | VAXUUM::SEGAL | | Wed Jul 08 1987 13:40 | 9 |
| This is fixed in V1.0 using the following code. It should be safe
to use in BL7 and BL8 as well:
\def\setwidecodexample{\sevenpointmono%
\setbox0=\hbox{0}\obeyedspacewd=\wd0 %Leave this space here!
}% decrease point size; adjust space char width
Lee
|
| 613.2 | | AUTHOR::WELLCOME | Steve | Thu Jul 09 1987 16:50 | 5 |
| So...what do I do with it? I am one of DOCUMENT's naive users who
neither knows nor cares about anything except what I put in my
.GNC file.
(Seriously, I really don't know. How do I use your fix?)
|
| 613.3 | | MARTY::FRIEDMAN | | Thu Jul 09 1987 17:08 | 7 |
| The fix is done by your document administrator, by putting the code
in the doctype or in a file included by all doctypes called
DOC$LOCAL_ELEMENTS.
(Steve--done!)
Marty
|
| 613.4 | One more | VAXUUM::SEGAL | | Fri Jul 10 1987 15:33 | 13 |
| Steve: Sorry ... I assumed you were working in the DESIGN file.
My apologies; anyone who needs to use brute force for a single
file until V1.0 could use <include_tex_file>(fixfile.tex) to
get the fix code into an individual job.
Marty: check local doctype design files if you're relying
on DOC$LOCAL_ELEMENTS to patch the macro definition for the
entire installation. Some doctypes might contain yet another
version of the macro definition which
will conflict (at least in the point size) with your new default.
The most significant possibility I can think of is OVERHEADS.
Lee
|
| 613.5 | finger trip | VAXUUM::SEGAL | | Fri Jul 10 1987 17:00 | 21 |
| \setwidecodexample and \setfullpagewidthexample can both
be adjusted on a doctype basis, or local basis, to adjust
margins and point sizes for oversize monospaced examples.
The quick fix I provided is appropriate for document styles
which do NOT allow wider right margins and do not use left
gutters (i.e, REPORT). In other styles, where WIDE triggers
use of the left gutter (SOFTWARE.REFERENCE), you can use the
same method of adjusting the font and space width character
but invoke it with \setfullpagewidthexample (from MAXIMUM in
the user's source file) rather than \setwidecodexample.
Most styles don't change the point size if you only use WIDE,
(and may/may not adjust left or right margins)
but most do if you use MAXIMUM. So, getting the cart right after
the horse ... use the temporary fix only for
\setfullpagewidthexample (triggered via MAXIMUM), and allow
WIDE to adjust the margins.
V1.0 makes adjustments in system defaults, and in DESIGN files.
Lee
|
| 613.6 | Is there a solution, I wonder | RDGENG::VAL_K | | Wed Jul 15 1987 06:57 | 27 |
| Many thanks to those who replied. The fix suggested in 613.1 and
613.4 - namely that of including a "fix" file - did not work
with BL7 nor BL8. It had no effect at. I did try moving the
<INCLUDE.....> tag to inside the <CODE_EXAMPLE>, outside it, and
at the top of the whole file, with no effect. I even tried to graft
the whole 3-line fix into the .TEX file.
I finally found what does work. I introduced a <ALIGN_CHAR>(#)
just before the <CODE_EXAMPLE>(WIDE\MAXIMUM) tag and closed it at
the end of the example. Then all spaces were replaced with #.
There is a snag however, (isn't there always?). Leading #'s cause
extra blank lines to be thrown up. So I used spaces only in leading
positions, after carefully re-aligning the report.
WORKS FINE ! ! ! in BL7 ***BUT***
In BL8 the character font has been changed to a wider one, and my
report falls off the right-hand edge. It is very frustrating to
spend long hours trying to bend ones work to fit the tools in order
to achieve a goal, when someone up there keeps moving the goal-posts.
Does anyone know how I can access the small font as used in BL7
from later versions of DOCUMENT?
Val.
|
| 613.7 | Step back | CLOSET::SEGAL | | Wed Jul 15 1987 17:18 | 10 |
| If you still have the standard font file and fonts from BL7
you could build a local doctype and replace the courier
monospace (new font) with the AMTT monospace (old font)
in the local font file. You will lose the DOCUMENT standard
character and font support, though, if you disable the
Courier monospace. As for moving the goal posts, well,
not exactly. AMTT was included in the FT kit because the (complete)
fonts weren't ready when we were.
Lee
|