cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Hi Adepters,

ebenton
1-Newbie

Hi Adepters,

Any time you change an external entity file, you must recompile your
doctype. You are correct about Epic writing binary files, but it doesn't do
this automatically whenever you change the file. You must force Epic to
rewrite the binary files to find the changed entities, by using the
compile_doctype command.
See the help about compiling doctypes.
13 REPLIES 13
lhales
1-Newbie
(To:ebenton)


Dave,

Take a look in the Options | Preferences under the File tab. There is an
option to enter a graphics path. If you have the "bad" graphics path in
there it could be causing your problem. Doesn't sound like it is, but
might be worth a look.

Lynn


Dave Burkhart
<burkhard to:=" adepters@arbortext.com=" <br="/> @spar.ca> cc:
Sent by: Subject: Re: RE: Hi Adepters,
owner-adepter
s


05/08/2002

I've had problems when the entry in the graphics.ent file, and the entry in the catalog, were not quite the same.

from one of my catalogs:

PUBLIC "-//CDN-DND::LITTON//NONSGML z-tp440amf01-00001 Automated Maintenance Support SystemRF ATMSSRF//EN"
"..\..\..\systems\t\tp\tp4\tp44\tp440\tp440a\tp440am\tp440amf\tp440amf01\graphics\z-tp440amf01-00001a.tif"

from one of my graphic.ent files:



You could also try rebooting your desktop rather than just restarting epic. I've found this to be helpful when behavioral problems occur.

Greg
🙂

Mr. Gregory B. MacKenzie B.F.A.
Publishing Applications Specialist
Publications Management Services
Litton Systems Canada
Division of Litton Systems Canada Limited

The only entry in my Options/Preferences/File/Graphics Path box was to the catalog I changed.

Turns out the problem is path related though. I had another person open the document on her machine and the graphic resolved correctly.

These were her Options/Preferences/File/Catalog Path entries:
k:\epicdoctypes\dnd\cals\source\doctypes;
K:\data\cftos\000mn001book3;
k:\data\gen_pub\000mn001book3;
C:\Program Files\Epic\doctypes;
k:\epicdoctypes\dnd\cals\source\entites\fosi\fragment

These were mine:
k:\epicdoctypes\dnd\cals\source\doctypes;
K:\dnd\cals\source;
C:\Program Files\Epic\doctypes;
k:\data\gen_pub\000mn001book3;
k:\data\cftos\000mn001book3;
k:\epicdoctypes\dnd\cals\source\entites\fosi\fragment

The catalog I had changed was in k:\data\cftos\000mn001book3 which appeared in both Catalog Path boxes.

When I made my paths identical to my co-worker's, the graphic resolved on my machine.

So it looks like the order in which the paths appear is important.

Thanks for your help folks.

Dave

>>> "Benton, Ed L" <-> 05/08 7:24 AM >>>
Good point, Lynn. There are also those damn "epicprefs.acl" files that can
have graphics paths in them that will override anything set in an APTGRPATH
environmental variable or pubrc or doctype.acl file. Anything that gets
changed or entered into that Options/Preferences dialog graphic path field,
and then saved, will get written to the "epicprefs.acl" file.
lhales
1-Newbie
(To:ebenton)


Dave,

Your assumption that catalog path order is important is correct. The
catalog uses that old inventory approach of FIFO (first in, first out). If
you have two public identifiers pointing to different documents, the first
one encountered will be the one that is resolved. So not only is the
catalog path sequence important, but so is the order of entry in the
catalog file itself.

One other thing to keep in mind with Epic on Windoze. When working from a
command line or script input, Epic does not like the space in the
C:\program files\epic
path unless it is either delimited by single or double quotes, or you use
the tilde "~" to shorten the path name. Even in the APTPATH variable.

I am adding this as you said when you made the changed the order to match
the other workers path things worked. I would believe you have a duplicate
catalog entry or the path is resolved prior to getting to the space. Did
your error message say something like "file not" something like a valid
command?

Lynn E. Hales
Information Technology Consultant
lhales@csc.com
(757) 262-3495


Dave Burkhart
<burkhard to:=" adepters@arbortext.com=" <br="/> @spar.ca> cc:
Sent by: Subject: Re: RE: RE: Hi Adepters,
owner-adepter
s


05/08/2002
10:31 AM
Please
respond to
adepters



The only entry in my Options/Preferences/File/Graphics Path box was to the
catalog I changed.

Turns out the problem is path related though. I had another person open the
document on her machine and the graphic resolved correctly.

These were her Options/Preferences/File/Catalog Path entries:
k:\epicdoctypes\dnd\cals\source\doctypes;
K:\data\cftos\000mn001book3;
k:\data\gen_pub\000mn001book3;
C:\Program Files\Epic\doctypes;
k:\epicdoctypes\dnd\cals\source\entites\fosi\fragment

These were mine:
k:\epicdoctypes\dnd\cals\source\doctypes;
K:\dnd\cals\source;
C:\Program Files\Epic\doctypes;
k:\data\gen_pub\000mn001book3;
k:\data\cftos\000mn001book3;
k:\epicdoctypes\dnd\cals\source\entites\fosi\fragment

The catalog I had changed was in k:\data\cftos\000mn001book3 which appeared
in both Catalog Path boxes.

When I made my paths identical to my co-worker's, the graphic resolved on
my machine.

So it looks like the order in which the paths appear is important.

Thanks for your help folks.

Dave

>>> "Benton, Ed L" <-> 05/08 7:24 AM >>>
Good point, Lynn. There are also those damn "epicprefs.acl" files that can
have graphics paths in them that will override anything set in an APTGRPATH
environmental variable or pubrc or doctype.acl file. Anything that gets
changed or entered into that Options/Preferences dialog graphic path field,
and then saved, will get written to the "epicprefs.acl" file.

Yes, the order is important. If there are duplicate PUBLIC names in two
catalogs, Epic will use the one in the first catalog. This can cause
problems if the two catalogs point to two different locations for the same
PUBLIC name. You may want it to use the second one, but Epic will always
use the first one. You could "fix" this by changin your own APTCATPATH to
have the second catalog come first, but this is a kluge. You should avoid
this situation. We only use one catalog outside of the Epic\doctypes
catalog. It's easier to avoid errors that way.

I just wanted to see how many "RE:"s I could get in the subject line.

Thanks Ed, I agree. I think we have enough kludges in our system here for now -- I won't be adding any more.

I will experiment a bit and see if we can maybe get by with only one "uber catalog" for each book that we can point to from both directories in use.

Dave

>>> "Benton, Ed L" <-> 05/08 10:46 AM >>>
Yes, the order is important. If there are duplicate PUBLIC names in two
catalogs, Epic will use the one in the first catalog. This can cause
problems if the two catalogs point to two different locations for the same
PUBLIC name. You may want it to use the second one, but Epic will always
use the first one. You could "fix" this by changin your own APTCATPATH to
have the second catalog come first, but this is a kluge. You should avoid
this situation. We only use one catalog outside of the Epic\doctypes
catalog. It's easier to avoid errors that way.
lhales
1-Newbie
(To:ebenton)


Ed,

Looks like you're capped at three from my end.

Are you going to burn the midnight oil in Montreal next week to keep all
the Adepters posts up to date?

Lynn


Sounds like fun - here's another one.

>>> "Benton, Ed L" <-> 05/08 11:07 AM >>>
I just wanted to see how many "RE:"s I could get in the subject line.

I guess Outlook 97 stops at 3. Keeping the Adepters up depends upon whether
or not I can scam a laptop to take with me. Otherwise, I'll just have to be
satisfied with keeping my blood alcohol level up.

I guess you aren't familiar with the price of alcohol in Canada...

>>> - 05/08/02 02:56PM >>>
I guess Outlook 97 stops at 3. Keeping the Adepters up depends upon whether
or not I can scam a laptop to take with me. Otherwise, I'll just have to be
satisfied with keeping my blood alcohol level up.



I think you guys have beaten this one to death. Can we focus on my problem now?

Many Thanks,
Sean

"Benton, Ed L" <-> on 05/08/2002 01:56:52 PM

Please respond to adepters@arbortext.com

Lynn,
At the risk of offending people with real problems...it's a deal!
Announcements