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

problem w/ <?Pub...

megan.rock
1-Newbie

problem w/ <?Pub...

Hello Adepters,

One of my co-workers is having problems with a manual he is working on in Epic 4.3.1A. Every time he edits part of the manual, he sees a red strike-through attribute on every element. Here is an example of what he is seeing in the XML source:

<para sdgzgr8="3">The M-710iT is a six axis...

When I edit the same part of the manual, I do not see the red strike-through attributes. The XML source looks like this to me:

<para>The M-710iT is a six axis...

This is the only manual that is displaying for him this way. The other manuals seem to be fine and display the same way for us both. We are running identical installations of Epic 4.3.1A.

Does anyone have any ideas why this one manual is displaying differently for us?

Thanks,
Megan
5 REPLIES 5


Megan,

I am assuming that the way the XML appears in your instance is correct, the
SDGZGR8 is supposed to be in a PI and is not an attribute of <para>. This
is the same file correct or are one of you using a copy (either
intentionally or accidentally)? What is in the actual source file, not
what do you see when you View|Edit as XML? If the what you are seeing is
correct, then the XML source file should reflect the PI.

Have you tried using the find_pi() or find_pi_string() functions in the
suspect instance(s)? See if you can find the PI. If that fails, then use
the find tag/attribute an look for the attribute value in a para tag. It
does not seem right that Epic would read a PI as an elements attribute in
one case and as the PI on another system. I'm sure you recognize the
redline in the <para> attribute as an attribute value in the start tag that
is not in the DTD.

Next thing I would do is recompile the DTD on the authors machine, forcing
everything to recompile. A real simple way to do this is to delete the PTD
and PRO files. If Epic cannot find the compiled files, it will ask you if
you want to recompile and the compile will default as 'force'. Make sure
you specify XML if you are asked.

Lynn


"Rock, Megan"
<megan.rock to:=" <adepters@arbortext.com=">
@fanucrobotics.c cc: "Wylie, John" <john.wylie@fanucrobotics.com>
om> Subject: problem w/ Sent by:
owner-adepters


03/12/2003 08:33
AM
Please respond
to adepters



Hello Adepters,

One of my co-workers is having problems with a manual he is working on in
Epic 4.3.1A. Every time he edits part of the manual, he sees a red
strike-through attribute on every element. Here is an example of what he
is seeing in the XML source:

<para sdgzgr8="3">The M-710iT is a six axis...

When I edit the same part of the manual, I do not see the red
strike-through attributes. The XML source looks like this to me:

<para>The M-710iT is a six axis...

This is the only manual that is displaying for him this way. The other
manuals seem to be fine and display the same way for us both. We are
running identical installations of Epic 4.3.1A.

Does anyone have any ideas why this one manual is displaying differently
for us?

Thanks,
Megan


Hi Megan,

I remember having the same problem a few years back. We were doing a
project with Astoria and the Astoria bridge was inserting all these
processing instructions.
Reason for this extra pseudo attibute to display in the editor is when the
file attiattr.cf file is missing in the doctype directory when compiling
the doctype. I assume recompiling the doctype would do the trick.
Actually, I'm not sure if the file atiattr.cf would be called the same in
Epic 4.3 as we used Adept 9 at that time.

Hope that helps

Petra

FYI, it's still called atiattr.cf. And I think this is the correct
diagnosis.

Our problem seems to have magically fixed itself. We hadn't done anything to try to straighten things out when everything suddenly started working normally again for my co-worker, after two days of the processing instructions showing up as pseudo attributes.

Thanks for everyone's suggestions, though!
Megan


Return Receipt

Your problem w/ document
:

was Allen Seifert/xsystems
received
by:

at: 03/15/2003 11:32:59 PM



Announcements