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

Community Tip - Your Friends List is a way to easily have access to the community members that you interact with the most! X

tag not in insert markup dialog

ebheadrick
1-Newbie

tag not in insert markup dialog

I am trying to figure out why a tag might not be showing up in the insert markup dialog. I have combed through the DCF file and it isn't listed as hidden. I have scanned our ACL code to see if it might be doing something and didn't find any mention of it there.

When I turned contect rules off, it was listed there and I was able to insert it and all the tags listed in the DCF to auto insert also got inserted. Turning context rules back on there were no completeness errors.

Is there someplace else I should be looking?

Thanks for any ideas,
Ellen

version 5.2 M020

8 REPLIES 8

Hi Ellen,

Sometimes it's to do with how the DTD is structured. For example, if you
have a mixed content structure in the DTD you may not be able to insert
that particular element until it meets the structure outlined
specifically in the DTD.

Cheers,
Juliette

I am pretty sure that is not the case.

| warning )*) | ( para | fig | table | caution | note | warning )+
) , S* >
^ this is the one not
showing up but it sees the A

We just tried using <oxygen/> and the parser there saw both the A and P.a.
So our guess right now is that the parser is not seeing this correctly.

Ellen

"Juliette Gibb" <juliette.gibb@virginblue.com.au> wrote on 01/21/2009

Ellen,
Thinking I had forgotten/overlooked something in DTD construction, I did a little quick (emphasis on 'quick') research, but I'm still stumped.

What does the ", S*" do for you in your element definition (following the content model)? And is this an SGML or an XML DTD?

Thanks,
Steve Thompson
TAD Technical
Boeing-IDS Technical Publications
+1(316)977-0515
MC K83-08
The truth is the truth even if nobody believes it, and a lie is a lie even if everyone believes it.

NOTICE: This communication may contain proprietary or other confidential information. If you are not the intended recipient, or believe that you have received this communication in error, please do not print, copy, retransmit, disseminate, or otherwise use the information. Also, please indicate to the sender that you have received this e-mail in error, and delete the copy you received. Any and all views expressed are the current understanding of the sender and should not be interpreted as an expression of official Boeing Company policy or position.

Les renseignements contenus dans ce message peuvent être confidentiels. Si vous n'êtes pas le destinataire visé ou une personne autorisée à lui remettre ce courriel, vous êtes par la présente avisé qu'il est strictement interdit d'utiliser, de copier ou de distribuer ce courriel, de dévoiler la teneur de ce message ou de prendre quelque mesure fondée sur l'information contenue. Vous êtes donc prié d'aviser immédiatement l'expéditeur de cette erreur et de détruire ce message sans garder de copie.


The Editor has some issues in this area back in 5.2 and early versions
of 5.3. We think we fixed them in 5.3 M030. You should try downloading a
newer version of 5.3 and see if your issue is addressed. If it is fixed,
you have a reason to think about upgrading. If not, you should file a
call with our Technical Support people.

John Dreystadt
Software Development Director
Arbortext - PTC
734-352-2835
-


Thank you for the information. I will check the newer version.

Ellen

"Dreystadt, John" <-> wrote on 01/22/2009 11:21:06 AM:

> The Editor has some issues in this area back in 5.2 and early
> versions of 5.3. We think we fixed them in 5.3 M030. You should try
> downloading a newer version of 5.3 and see if your issue is
> addressed. If it is fixed, you have a reason to think about
> upgrading. If not, you should file a call with our Technical Support
people.
>
> John Dreystadt
> Software Development Director
> Arbortext - PTC
> 734-352-2835
> -
>
>

All,
My apologies if my reply sounded like a real newbie question, but it wasn't rhetorical. If that construct is somehow flawed, that could explain why one parser does one thing, and another does something else. It would depend on the 'strictness' of the parser.

I ask again, what's the ", S*" intended to do?

But, more to the point, why would you expect to see a P.a after an A? According to the structure, you have EITHER a single A or a single P.a, followed by any number of para, fig, etc. OR at least one and possibly more of para, fig, etc. To have both an A and a P.a, the first portion of the structure should be "(A | P.a)+" or "(A | P.a)*".

Excerpt of your element structure:
( ( A | P.a) , ( para | fig | table | caution | note | warning )*)

As it is, the "," says that what is in those parentheses is followed by what is in the next parentheses. Since there's only one instance of the first parentheses (no "+" or "*"), you shouldn't be able to have one of either A or P.a followed by one of the other. If one of the parsers is allowing the P.a after an A, that parser is not following this part of the structure. The part of the structure not shown here, the "or" ("|") part doesn't include "A" or "P.a", so it doesn't affect your problem.

Or did I still miss something?
Steve Thompson
+1(316)977-0515

When I retyped (and shorten) it I might have missed a parentheses, but yes
you can only have (A or P.a) and the S* is to allow nesting. And the
problem is that the P.a never shows up in the insert dialog box at the S
level. I hope that helps, I still need to try the newer version.

Ellen

"EXT-Thompson, Steve" <steve.thompson2@boeing.com> wrote on 01/22/2009
01:09:22 PM:

> All,
> My apologies if my reply sounded like a real newbie question, but it
> wasn't rhetorical. If that construct is somehow flawed, that could
> explain why one parser does one thing, and another does something
> else. It would depend on the 'strictness' of the parser.
>
> I ask again, what's the ", S*" intended to do?
>
> But, more to the point, why would you expect to see a P.a after an
> A? According to the structure, you have EITHER a single A or a
> single P.a, followed by any number of para, fig, etc. OR at least
> one and possibly more of para, fig, etc. To have both an A and a P.
> a, the first portion of the structure should be "(A | P.a)+" or "(A |
P.a)*".
>
> Excerpt of your element structure:
> ( ( A | P.a) , ( para | fig | table | caution | note | warning )*)
>
> As it is, the "," says that what is in those parentheses is followed
> by what is in the next parentheses. Since there's only one instance
> of the first parentheses (no "+" or "*"), you shouldn't be able to
> have one of either A or P.a followed by one of the other. If one of
> the parsers is allowing the P.a after an A, that parser is not
> following this part of the structure. The part of the structure not
> shown here, the "or" ("|") part doesn't include "A" or "P.a", so it
> doesn't affect your problem.
>
> Or did I still miss something?
> Steve Thompson
> +1(316)977-0515

In trying to open the call I found something in the knowledgebase!!! This
works! Why, I have no idea!

Resolution
The problem is that the "autoinsert" entry for <list> is not correct in
the dcf file. White space is significant in that section so you can't have
newlines. If you change the entry to be all on one line like:

<insertautowithin element="list" <br="/>xmlns:foo="foo.dtd"><foo:i><insertautocaret/></foo:i></insertautowithin>

You will see the missing (list) element show up in the insert markup panel
and in quicktags.

Ellen
Top Tags