Pseudo-attributes

Submitted by: Jason Aiken Last Updated: 2006-09-02

I've supplied some additional info on pseudo-atts below (did you see help 25?).

There's some pseudo-attributes plugged into the outspec DTD. Check out [epic-path]\doctypes\outspec\atiattr.cf for some information on syntax. You can add an atiattr.cf file to your own custom doctype directory. Additional pseudo-attributes are added as sty: entries in the atiattr.cf file.

Attributes added in this way are considered valid on any element, but I'm not sure how to make the Epic GUI allow entering them via the modify attributes dialog.

I also believe that in order for the atiattr.cf file to be read, one must compile the DTD in Architect using the old Mark-It parser method. That is, you need this declaration as the first line of your DTD file:

<?aptxml version="1.0" encoding="utf-8"?>

(Editor's comment by Karl John Kleist: The GUI completely ignores pseudo-instructions. See also "help 1363". Think twice before using this ancient non-standard construct for anything but formating, they are supported by very few applications (one of them was the SGML document repository "Texcel Information Manager", a product well before its time when I worked with it ten years ago).)