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

Literal areas and FOSIs

Level 1

Literal areas and FOSIs

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Can any one of you kind folks point me in the correct direction so I
can get our tags set up to display properly? A
denotes an area where the text isn't to be formatted, just output as it
is. It may contain other tags or entity refs, though.

I've been 'round and 'round the mulberry bush trying to find the info
but I just haven't caught the weasel yet.

Thanks in advance for any help.

- --
Kenneth D. Weinert

Black holes are the manifestation of God dividing by zero.

** Tag(s) inserted by Bandit Tagger98 - http://www.gbar.dtu.dk/~c918704

PGP Public Key Fingerprint: A81E E71D 34EE 5AF2 6CB1 D899 690C 5981

-----BEGIN PGP SIGNATURE-----
Version: PGPsdk version 1.0 (C) 1997 Pretty Good Privacy, Inc

iQA/AwUBN4Iul2kMWYH60NHeEQIaWwCghtu4H8Q8/25aB40fZGcBvRyzrBIAn0zj
FT3C+gLXWGTA0LWhKX/lVuEi
=Kvcx
-----END PGP SIGNATURE-----
Tags (2)
7 REPLIES 7

Literal areas and FOSIs

Ken,

Your literal tag sounds pretty much like the verbatim tag we "borrowed" from
28001. If that is the case, you might want to try this e-i-c and see this
helps. The only thing with our verbatim element is the content model is
CDATA rather than PCDATA.



Literal areas and FOSIs

If I understand you correctly, you are trying to maintain the line breaks
and spaces in the source instance. This is achieved by setting the quadding
of the LIT e-i-c to none (as is).

Hope this helps

Gershon

Gershon Leib Joseph
DOCUMENTATION TECHNOLOGIES MANAGER
Comverse Network Systems

Literal areas and FOSIs

Literal areas and FOSIs

Thanks for everyone's help - I think I might have a handle on it now -
it helps to know the correct terminology and where to look :-)

Literal areas and FOSIs

Ken,

Your literal tag sounds pretty much like the verbatim tag we "borrowed" from
28001. If that is the case, you might want to try this e-i-c and see this
helps. The only thing with our verbatim element is the content model is
CDATA rather than PCDATA.



Literal areas and FOSIs

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Can any one of you kind folks point me in the correct direction so I
can get our tags set up to display properly? A
denotes an area where the text isn't to be formatted, just output as it
is. It may contain other tags or entity refs, though.

I've been 'round and 'round the mulberry bush trying to find the info
but I just haven't caught the weasel yet.

Thanks in advance for any help.

- --
Kenneth D. Weinert

Black holes are the manifestation of God dividing by zero.

** Tag(s) inserted by Bandit Tagger98 - http://www.gbar.dtu.dk/~c918704

PGP Public Key Fingerprint: A81E E71D 34EE 5AF2 6CB1 D899 690C 5981

-----BEGIN PGP SIGNATURE-----
Version: PGPsdk version 1.0 (C) 1997 Pretty Good Privacy, Inc

iQA/AwUBN4Iul2kMWYH60NHeEQIaWwCghtu4H8Q8/25aB40fZGcBvRyzrBIAn0zj
FT3C+gLXWGTA0LWhKX/lVuEi
=Kvcx
-----END PGP SIGNATURE-----

Literal areas and FOSIs

If I understand you correctly, you are trying to maintain the line breaks
and spaces in the source instance. This is achieved by setting the quadding
of the LIT e-i-c to none (as is).

Hope this helps

Gershon

Gershon Leib Joseph
DOCUMENTATION TECHNOLOGIES MANAGER
Comverse Network Systems