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

Notations

Highlighted
Newbie

Notations

Does anyone know how to accomplish the following with Adept?

In our SGML files, we have entity references like the following:

&somefile;

&somefile; is declared like this:



The problem is that somebody decided to put characters that are
important in SGML inside the file we are referencing. For instance,
there are lines like this:

SKEW SENSITIVITY OF SHELLS: 4 X 4 MESH, , DEG

where the information inside the angle brackets is completely
arbitrary -- i.e., we cannot define it inside the DTD.

I need a way to define the entity in such a way that the information
inside the file is not parsed as SGML. I thought that doing it
this way would work:



along with this:



and it does, at least as far as the parser is concerned. That is,
I can at least bring up the file containing the entity reference
in Adept and work with it.

The problem is that, since mynotation is unknown to Adept, the
information in the file entity is not printed at all when we compose
the output with Adept/Publisher. Does anybody know if there is a
special notation type or some other approach (no subdocs, please)
that will allow me to work around this problem?

An additional requirement: the information inside the file entity
needs to be formatted with carriage returns respected, since it
is nothing but a program listing.

--
Glenda Jeffrey Email: jeffrey@hks.com
Hibbitt, Karlsson & Sorensen, Inc Phone: 401-727-4200
1080 Main St. Fax: 401-727-4208
Pawtucket, RI 02860 Web: http://www.hks.com
Tags (2)
3 REPLIES 3
Highlighted

Notations

At 12:23 PM 5/7/98 -0400, Glenda Jeffrey wrote:
>I need a way to define the entity in such a way that the information
>inside the file is not parsed as SGML. I thought that doing it
>this way would work:

You might try using RCDATA marked sections instead. That will work as long
as there's nothing that looks like an entity reference inside the file
(which you declare as a text entity and not a data entity in this case):





--

W. Eliot Kimber, Senior Consulting SGML Engineer
ISOGEN International Corp.
2200 N. Lamar St., Suite 230, Dallas, TX 95202. 214.953.0004
www.isogen.com
</address>
Highlighted

Notations

On May 7, 1:01pm, W. Eliot Kimber wrote:
> Subject: Re: Notations
> At 12:23 PM 5/7/98 -0400, Glenda Jeffrey wrote:
> >I need a way to define the entity in such a way that the information
> >inside the file is not parsed as SGML. I thought that doing it
> >this way would work:
>
> You might try using RCDATA marked sections instead. That will work as long
> as there's nothing that looks like an entity reference inside the file
> (which you declare as a text entity and not a data entity in this case):
>
>
> &mytextentity;
> ]]>
>
>

This was the first thing I tried. Adept still complains that the
entity is out of context. Composition generates errors like this
for each bracketed item:

*** Error on line 1 in file /usr/abaqus60/external/doc/col/books/exa-inp/1010503.inp:
Unknown element in start tag.
There is no such element as 'elemtype'.

Hence the notation approach...

I just want to make sure I understand this statement:

> (which you declare as a text entity and not a data entity in this case):

Do you mean that the entity needs to be declared like this (which is
what I tried with the RCDATA approach you describe):



rather than like this (which I think should be valid only for the
notation-based approach I originally described):



or is there some other declaration trick I need to use?

--
Glenda Jeffrey Email: jeffrey@hks.com
Hibbitt, Karlsson & Sorensen, Inc Phone: 401-727-4200
1080 Main St. Fax: 401-727-4208
Pawtucket, RI 02860 Web: http://www.hks.com
Highlighted

Notations

At 02:42 PM 5/7/98 -0400, Glenda Jeffrey wrote:

>I just want to make sure I understand this statement:
>
>> (which you declare as a text entity and not a data entity in this case):
>
>Do you mean that the entity needs to be declared like this (which is
>what I tried with the RCDATA approach you describe):
>
>

Yes.

>rather than like this (which I think should be valid only for the
>notation-based approach I originally described):
>
>
>
>or is there some other declaration trick I need to use?

That's it.

I did a quick test, creating a valid document that references an external
text entity from an RCDATA marked section. ADEPT*Editor 7.0 reports that
the contents of the entity are out of context, although SP reports that the
document is valid (which it is).

Thus it would appear that ADEPT*Editor (and presumably Publisher) cannot
support this use of RCDATA marked sections :-(.

It would appear that your only other option is to pre-process the file to
escape any left angle brackets and then include it normally.

Cheers,

E.
--

W. Eliot Kimber, Senior Consulting SGML Engineer
ISOGEN International Corp.
2200 N. Lamar St., Suite 230, Dallas, TX 95202. 214.953.0004
www.isogen.com
</address>
Announcements