| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 398.1 | Sounds Like a VMS Issue | CLOSET::ETZEL | Mike | Wed May 20 1987 14:44 | 8 |
| Rose,
I believe the support for this is not yet provided by VMS, but have
sent mail to an appropriate developer. I'll post the reply here.
This sounds like a VMS print symbiont issue, not a DOCUMENT issue.
Mike
|
| 398.2 | How about not putting fonts in LNx output? | COOKIE::WITHERS | Le plus ca change... | Wed May 20 1987 15:13 | 20 |
| If we can't suppress the loading of the fonts into an LN03 for multiple
copies of a file, is there a way to load fonts from an external source
when we print documents? My thinking is thus...
I have a sample of a directory listing where the LN3 and LNO files are 12
times larger than the source. After generating lots of documents, this
starts to really eat up disk space. For example:
SW_REL_SYM_AT_FORD_AERO.GNC;64
27 19-MAY-1987 13:44 (RW,RWED,,RE)
SW_REL_SYM_AT_FORD_AERO.LN3;16
178 19-MAY-1987 13:46 (RW,RWED,,RE)
SW_REL_SYM_AT_FORD_AERO.LNO;10
148 19-MAY-1987 13:45 (RW,RWED,,RE)
If fonts have to be loaded every time we print something that's in LNO or
LN3 format, could we have some way of saving disk space?
Thanks,
BobW
|
| 398.3 | SMOP, right? | CUPOLA::HAKKARAINEN | Albatross! | Wed May 20 1987 17:24 | 5 |
| As Mike noted in .1, the solution is probably in the print symbiont.
The fonts could be loaded on the fly, saving users time and
disk space. DSRplus offers this on a limited basis for the ln01.
It still seems to be tricky business to do conditional font loads,
but that's what makes forums such as this so much fun.
|
| 398.4 | in the future -- maybe | VAXUUM::DEVRIES | Those are features, not bugs | Thu May 21 1987 17:30 | 15 |
| From a technical point of view, this is something a future print
symbiont (say, a "font server") might well be able to do.
But it brings up all kinds of management and legal questions. We
ship these printable files all over the net. If you want to print
such an in-the-future file where you are, then you would have to
have the fonts needed (a system management issue), which probably
means you would have had to pay many bucks for the royalties on
all the fonts you might ever want to print (a legal/business issue)
or the font server will have to have a "satisfactory" fallback plan
(both a system management and a technical issue).
So it's a great idea -- but not a *simple* idea.
Mark
|
| 398.5 | there's always a way | RDCV01::FSL | Rob Aldridge | Thu Jul 23 1987 01:10 | 18 |
| If you *really* need to print multiple copies of the same .LN3
file, you can break the file into its two pieces. The first
"half" of the file is the font information, the second "half" is
the encoded "text" to be printed.
Using EDT or other, you can Search for the end of the font-load.
(I believe that it ends with <ESCAPE>\ .) Then you can "cut" the file
into its two pieces. For more info, consult your LN03 programming
book.
If you manage to successfully cut the file into two, then you can
print the file containing the font-information ONCE, then print
the file containing the encoded-text as many times as you'd like.
All this takes some technical expertise. *Not recommended for the
novice!*
-Rob-
|
| 398.6 | Bravo! | GNUVAX::LIBRARIAN | Looking at the big sky | Thu Jul 23 1987 09:50 | 6 |
|
Bravely editing the un-editable...I love it! Carry on!
Lance
|
| 398.7 | It gets even worse! | VAXUUM::DEVRIES | M.D. -- your Device Doctor | Thu Jul 23 1987 13:46 | 43 |
| RE: .5
> If you *really* need to print multiple copies of the same .LN3
> file, you can break the file into its two pieces. The first
> "half" of the file is the font information, the second "half" is
> the encoded "text" to be printed.
The second half also ends with commands to clear all fonts and reset
the internal state, so your second copy of the text part would not see
the font load.
Even if you succeed in stripping out the reset stuff, you're not
out of the woods. In a very large file this pattern can be repeated:
<fonts><text><fonts><text> ...
so if you break up the document after the first font load and run
the rest of it TWICE, the second copy will start with the second
font load in place, not the first one.
> Using EDT or other...
Other, yes (TPU-based things, at least).
EDT, no. It reformats the output and truncates long records.
> If you manage to successfully cut the file into two, then you can
> print the file containing the font-information ONCE, then print
> the file containing the encoded-text as many times as you'd like.
If you are on a shared LN03, and you submit these pieces as separate
jobs, you must be sure that nobody else prints a job that fools
with fonts in between your jobs.
> All this takes some technical expertise. *Not recommended for the
> novice!*
Or the expert, either. :-)
--Mark
|