[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference vaxuum::document_ft

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

186.0. "DOCTYPE runs in one place, not another--why?" by COOKIE::JOHNSTON () Wed Apr 01 1987 20:39

I've encountered essentially the same problem in using a new doctype 
as the problem noted in 49.0, but with a new twist I think.  

Here's the scenario:

1.  I have a new doctype, CKDOC, that my group has been using for about 10 days.

2.  Today, everything broke if I tried processing a file outside of 
    [JOHNSTON.PERSONAL_FORMATS]CKDOC.DTP.  If CKDOC is called from
    DOC$BL07_ROOT:[LOCAL.FORMATS]CKDOC.DTP, processing stops with this
    error:

%TEX-I-ONPAGE, on page [1]

%TEX-I-OUTFILENAME, 'my$disk:[johnston.formats]TEST_PRO_CONTENTS.DVI_LPR'
text input levels=6].
l.97 \input DOC$$DEVICE_FONTS:
                              
If you really absolutely need more capacity,
you can ask a wizard to enlarge me.

No pages of output.
%TEX-I-PAGESOUT, 0 pages written.

%TEX-I-OUTFILENAME, 'my$disk:[johnston.formats]TEST_PRO_CONTENTS.DVI_LPR'


3.  This is how CKDOC is defined in DOC$DESIGNS.DAT:

name CKDOC/definitions=tag$s_specification/macros=ckdoc/fonts=tag$standard_fonts

4.  I did a diff on the files in both accounts; there are no differences.

5.  Why will it run in my own account still, but not from DOCTOOLS?

6.  A system manager double-checked this with me; we're both baffled!


HELP!!!!


Rose

T.R	Title	User	Personal Name	Date	Lines
186.1	too many \inputs	CLOSET::ANKLAM		`Thu Apr 02 1987 09:56`	10
	This came up already, in note #49. Something else must be different, since that error occurs with too many levels of \input inside local/personal DTP files. (for example it will occur if you have a local DTP that inputs doc$local_formats:cup$layered.dtp, which inputs doc$standard_formats:tag$s_handbook.dtp). I haven't worked out a solution/approach for this yet. patti
186.2	Hold my hand a while longer, please	COOKIE::JOHNSTON		`Thu Apr 02 1987 14:25`	40
	< Note 186.1 by CLOSET::ANKLAM > -< too many \inputs >- This came up already, in note #49. Something else must be different, since that error occurs with too many levels of \input inside local/personal DTP files. (for example it will occur if you have a local DTP that inputs doc$local_formats:cup$layered.dtp, which inputs doc$standard_formats:tag$s_handbook.dtp). I haven't worked out a solution/approach for this yet. patti CKDOC has \input doc$standard_formats:tag$s_specification.dtp TAG$S_SPECIFICATION inputs DOC$$DEVICE_FONTS:, for which I can find no translation. The error occurs only in the local .DTP files, not the personal. What else might be different that I can look at? Any suggestions for a quick, temporary if necessary, but acceptable fix? I'd abandon it until you worked out the right approach to handle these situations, but I'd rather not as the group has been using CKDOC for a couple of weeks now. Some documents are finished, others are being updated, all are being prepared for a review. Whatever is the best solution; your advice is solicited and welcomed. Thanx Rose
186.3	Some help?	BUNSUP::LITTLE	Todd Little NJCD SWS 323-4475	`Tue Apr 07 1987 10:51`	23
	What files are in what directories, and what do the "appropriate" DOC$DESIGNS.DAT files look like? Sounds to me like certain files are different in the local directory than in the personal directory. If memory serves me right, the logical DOC$$DEVICE_FONTS: is created on the fly by DOCUMENT to pass along the directory specification of the font files to TeX, since that information isn't known until the command line is parsed. This used to be done in the old command procedures, but is now probably done as part of the DOCUMENT image. I don't remember if its documented, but there might be a difference in where the files are being found and/or whether they are readable, i.e. appropriate protections on files and directories. The old administrators guide doesn't seem to indicate what defaults are applied to the file names that are specified in the DOC$DESIGNS.DAT. That could also be causing you problems. Can you post both copies of DOC$DESIGNS.DAT, verify that the files mentioned for your design are identical in both directories, and post the TeX files from both the working and non-working cases? -tl
186.4	Protection checked out ok...	COOKIE::JOHNSTON		`Tue Apr 07 1987 13:02`	25
	I sent copies of both DOC$DESIGNS.DAT files to Patti; ditto both .DTP files. I'll generate some .TEX files as well. The really baffling thing is that at one time it was available from DOC$LOCAL_FORMATS. Then suddenly one day it wasn't. I've done a diff on the .DTP files; there are no differences. In the meanwhile, I've simply copied all the Tag$s_specification defs into another .DTP file and modified where necessary, rather then \input it. If you really want me to post everything here, I will, but it might be better if I simply mailed them to you: 1. Directory listing of DOC$PERSONAL_FORMATS and DOC$LOCAL_FORMATS. 2. Both .DTP files 3. Working and non-working .TEX files 4. Both DOC$DESIGNS.DAT files Reply to this note or send mail; your wish is my temporary command. Thanx Rose
186.5	I'll look	BUNSUP::LITTLE	Todd Little NJCD SWS 323-4475	`Fri Apr 17 1987 13:23`	14
	Send away. I can't promise to spend a lot of time, but I'll try to look. -tl Also, do a SET HOST/LOG to your node and then do a: $ SHOW LOGICAL/FULL $ SHOW SYMBOL/ALL $ SHOW SYMBOL/GLOBAL/ALL $ DOCUMENT etc. for both the working and non-working cases and mail me those SETHOST.LOG files.