| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 735.1 | U.R. sure of an errorfree kit? | IJSAPL::KLERK | Theo de Klerk | Fri Jul 31 1987 12:57 | 8 |
| Are you sure your installation kit was copied without
any parity errors? It's known to happen occassionally when copying
savesets to Europe...
My DIGITAL.NFT seems to work fine.. you may wish to copy the file from
here (Holland) to you: IJSAPL::DOC$LN03_FONTS:DIGITAL.NFT
THEO
|
| 735.2 | does this help? | VAXUUM::KOHLBRENNER | | Fri Jul 31 1987 16:30 | 9 |
| what comes after the <endpreface><endfront_matter>?
I think you need a <chapter> or <appendix> or <part> tag.
as for not having the DECLOGO.NFT, did you install the DOCINT010
kit?
bill
|
| 735.3 | Answer to .1 and .2 | GVASA::SCHMID | Michel Schmid, Geneva | Mon Aug 03 1987 06:50 | 16 |
| re: .1, Theo, No, I'm absolutely not sure this kit is error-free. I've
copied your DECLOGO.*. It is exactly the same file as mine and shows
the same behavior. Thus I'm afraid that something else was corrupted in
the kit I did copy from Valbonne, on VISA::.
re: .2, Yes, Bill, There are indeed only <head1> and <head2> following
the <endpreface><endfront_matter> in my files. They were however
written using a previous version of DOCUMENT, and did print correctly
with this version (I ignore which one it was).
Anyway, maybe both problems have the same cause. I'll try to re-install
everything before looking further. Thus if somebody has a
parity-error-free kit, when possible in Europe, pls let me know.
Michel.
|
| 735.4 | you have a "chapter-oriented" document | VAXUUM::KOHLBRENNER | | Mon Aug 03 1987 10:46 | 8 |
| I checked with the authorities around here and they say, that unless
you are using a local doctype, there is no way to get the latest
<head> tag to print in the page header. The <endpreface> and
<endfront_matter> tags do not "turn off" the page heading, because
they assume that there is another element-heading tag coming along
which will set up the new page heading. So you once you use the
<preface> tag, you must use <chapter>, etc tags to control the
page heading. -bill
|
| 735.5 | <title> oriented document? | GVASA::SCHMID | Michel Schmid, Geneva | Mon Aug 03 1987 11:52 | 9 |
| It might well be that a local doctype was used: What was printed in the
page header wasn't the last <head> but the <title> from the
<title_page>.
Something else, when I ran doc$convert on the original .GNC files,
the <title> in the .SDML files where all preceded with a <COMMENT>
tag, maybe because the document structure looked not standard?
Michel.
|
| 735.6 | Try S.B | VAXUUM::SEGAL | | Mon Aug 03 1987 12:20 | 8 |
| You may be able to run with SOFTWARE.BROCHURE. That doctype
is sequentially numbered (chapter not required). It captures
the title and uses it for the running title. Perhaps your
local doctype was derived from the same design ?
The software.brochure design is approximately 7x9 inches (trim size),
but could be easily enlarged.
Lee
|
| 735.7 | baptism of fire | VAXUUM::KOHLBRENNER | | Mon Aug 03 1987 12:29 | 8 |
| Michel,
Converting someone else's GNC file, which was run under an unknown
doctype, to an SDML file to run under DOCUMENT V1.0 is an exacting
task for anyone. As a FIRST EXPERIENCE with DOCUMENT it will earn
you a special place in heaven.
Bill
|
| 735.8 | Still alive | GVASA::SCHMID | Michel Schmid, Geneva | Tue Aug 04 1987 05:05 | 15 |
| Bill,
I already felt my wings growing... But fortunately, just before
take-off, I could contact the guy who produced the .GNC files. He
used a special doctype, which he will send to me. So I'm more or
less back on the earth.
Regarding the other problem with the DEC logo, the same guy has also
installed V1.0 in Valbonne, and has experienced the same problem as I
have (Bad font file message). He is currently investigating.
If he can find something, I will communicate it here.
Michel.
|
| 735.9 | Logo problem cured | GVASA::SCHMID | Michel Schmid, Geneva | Mon Aug 10 1987 10:28 | 17 |
| The solution to the Digital logo problem has been found by Patrice
Dor� in Valbonne. The cause of the problem was a misunderstanding
of the installation instructions:
At some point of the installation of V1.0, I saw a question saying
that if LN03 fonts are not yet installed, full Ln03 support should
not be selected (I don't remember the exact terms) now, but rather
during a subsequent partial installation, following the font
installation. As I didn't had any fonts installed, I answered in
this sense to the question. The result was this problem with the
logo (and also with the font used with PICMODE figures).
The I re-started the full installation, with the fonts already loaded
from the first installation, and I didn't see that strange question
appear. And since then, this problem has gone.
Michel.
|