1 diff -Nru jade-1.2.1/jade.1 jade-1.2.1.new/jade.1
2 --- jade-1.2.1/jade.1 Thu Jan 1 01:00:00 1970
3 +++ jade-1.2.1.new/jade.1 Tue Sep 21 22:48:19 1999
6 +.\" NAME should be all caps, SECTION should be 1-8, maybe w/ subsection
7 +.\" other parms are allowed: see man(7), man(1)
9 +jade \- James' DSSSL Engine
12 +.I "[options] files ..."
14 +This manual page documents briefly the
17 +This manual page was written for the Debian GNU/Linux distribution
18 +(but may be used by others), because the original program does not
20 +Instead, it has documentation in HTML format; see below.
23 +is an implementation of the DSSSL style language.
24 +The current version is 1.1.
26 +For a complete description, see the html files.
28 +The programs are documented fully in
29 +.B /usr/doc/jade/jade.htm
31 +This manual page was written by Mark W. Eichin <eichin@kitten.gen.ma.us>,
32 +for the Debian GNU/Linux system.
33 diff -Nru jade-1.2.1/nsgmls/nsgmls.1 jade-1.2.1.new/nsgmls/nsgmls.1
34 --- jade-1.2.1/nsgmls/nsgmls.1 Thu Jan 1 01:00:00 1970
35 +++ jade-1.2.1.new/nsgmls/nsgmls.1 Tue Sep 21 22:48:19 1999
55 +nsgmls \- a validating SGML parser
57 +An \*S System Conforming to
59 +International Standard ISO 8879 \(em
61 +Standard Generalized Markup Language
86 +.BI \-o output_option
98 +This manual page may be out of date. Consult the HTML documentation for
99 +the most up-to-date information concerning this program.
102 +parses and validates
103 +the \*S document whose document entity is specified by the system identifiers
105 +and prints on the standard output a simple text representation of its
106 +Element Structure Information Set.
107 +(This is the information set which a structure-controlled
108 +conforming \*S application should act upon.)
109 +The form of system identifiers is described in detail below;
110 +a system identifier that does not start with
112 +and does not look like an absolute URL will be treated as a filename.
113 +If more than one system identifier is specified,
114 +then the corresponding entities will be concatenated to form
115 +the document entity.
116 +Thus the document entity may be spread amongst several files;
117 +for example, the SGML declaration, prolog and document
118 +instance set could each be in a separate file.
119 +If no system identifiers are specified, then
121 +will read the document entity from the standard input.
122 +A command line system identifier of
124 +can be used to refer to the standard input.
125 +(Normally in a system identifier,
127 +is used to refer to standard input.)
129 +The following options are available:
135 +Not all ESIS information is output in this case:
136 +the active LPDs are not explicitly reported,
137 +although each link attribute is qualified with
139 +there is no information about result elements;
140 +when there are multiple link rules applicable to the
143 +always chooses the first.
149 +See the description below of the
151 +storage manager attribute for more information.
155 +.IR filename \|.\|.\|.
156 +arguments specify catalog files rather than the document entity.
157 +The document entity is specified by the first
159 +entry in the catalog files.
164 +for files specified in system identifiers.
168 +See the description of the
170 +storage manager for more information about file searching.
173 +Describe open entities in error messages.
174 +Error messages always include the position of the most recently
175 +opened external entity.
180 +This is useful mainly with shells that do not support redirection
184 +Show the \s-1GI\s0s of open elements in error messages.
190 +.BI <!ENTITY\ %\ name\ \(tsINCLUDE\(ts>
192 +occurs at the start of the document type declaration subset
193 +in the \*S document entity.
194 +Since repeated definitions of an entity are ignored,
195 +this definition will take precedence over any other definitions
196 +of this entity in the document type declaration.
199 +options are allowed.
200 +If the \*S declaration replaces the reserved name
202 +then the new reserved name will be the replacement text of the entity.
203 +Typically the document type declaration will contain
205 +.BI <!ENTITY\ %\ name\ \(tsIGNORE\(ts>
209 +in the status keyword specification of a marked section declaration.
210 +In this case the effect of the option will be to cause the marked
211 +section not to be ignored.
215 +Map public identifiers and entity names to system identifiers
216 +using the catalog entry file whose system identifier is
220 +options are allowed.
221 +If there is a catalog entry file called
223 +in the same place as the document entity,
224 +it will be searched for immediately after those specified by
228 +Generate system identifiers for notations.
231 +command will be output before each
233 +command for a notation for which a system identifier could be generated.
235 +.BI \-o output_option
236 +Output additional information accordig to
241 +Output definitions of all general entities
242 +not just for data or subdoc entities that are referenced or named in an
243 +ENTITY or ENTITIES attribute.
246 +Distinguish attributes whose declared value is ID.
251 +commands giving the current line number and filename.
256 +command for included subelements.
260 +options are allowed.
264 +Parse only the prolog.
266 +will exit after parsing the document type declaration.
272 +Error messages will still be printed.
277 +the RAST result as defined by
278 +ISO/IEC 13673:1995 (actually this isn't quite an IS yet;
279 +this implements the Intermediate Editor's Draft of 1994/08/29,
280 +with changes to implement ISO/IEC JTC1/SC18/WG8 N1777).
281 +The normal output is not produced.
284 +Print the version number.
287 +Control warnings and errors.
290 +options are allowed.
291 +The following values of
297 +Warn about mixed content models that do not allow #pcdata anywhere.
300 +Warn about various dubious constructions in the SGML declaration.
303 +Warn about various recommendations made in ISO 8879 that the document
304 +does not comply with.
305 +(Recommendations are expressed with ``should'', as distinct from
306 +requirements which are usually expressed with ``shall''.)
309 +Warn about defaulted references.
312 +Warn about duplicate entity declarations.
315 +Warn about undefined elements: elements used in the DTD but not defined.
318 +Warn about unclosed start and end-tags.
321 +Warn about empty start and end-tags.
324 +Warn about net-enabling start-tags and null end-tags.
327 +Warn about minimized start and end-tags.
328 +Equivalent to combination of
336 +Warn about unused short reference maps: maps that are declared with a
337 +short reference mapping declaration but never used in a short
338 +reference use declaration in the DTD.
341 +Warn about parameter entities that are defined but not used in a DTD.
344 +Warn about conditions that should usually be avoided
345 +(in the opinion of the author).
358 +A warning can be disabled by using its name prefixed with
361 +.B -wall\ -wno-duplicate
362 +will enable all warnings except those about duplicate entity
365 +The following values for
370 +Do not give an error for an ID reference value
371 +which no element has as its ID.
372 +The effect will be as if each attribute declared as
373 +an ID reference value had been declared as a name.
376 +Do not give an error when a character that is not a significant
377 +character in the reference concrete syntax occurs in a literal in the
378 +SGML declaration. This may be useful in conjunction with certain
382 +The following options are also supported for backwards compatibility
401 +.SS "System identifiers"
402 +A system identifier can either be a formal system identifier
403 +or a simple system identifier.
404 +A system identifier that is a formal system identifier
405 +consists of a sequence of one or more storage object specifications.
406 +The objects specified by the storage object specifications
407 +are concatenated to form the entity.
408 +A storage object specification consists of an SGML start-tag in the
409 +reference concrete syntax followed by character data content.
410 +The generic identifier of the start-tag is the name of a storage manager.
411 +The content is a storage object identifier which identifies
412 +the storage object in a manner dependent on the storage manager.
413 +The start-tag can also specify attributes giving additional information
414 +about the storage object.
415 +Numeric character references are recognized in storage object identifiers
416 +and attribute value literals in the start-tag.
417 +Record ends are ignored in the storage object identifier as with SGML.
418 +A system identifier will be interpreted as a formal system identifier
421 +followed by a storage manager name, followed by
425 +otherwise it will be interpreted as a simple system identifier.
426 +A storage object identifier extends until the end of the
427 +system identifier or until the first occurrence of
429 +followed by a storage manager name, followed by
434 +The following storage managers are available:
437 +The storage object identifier is a filename.
438 +If the filename is relative it is resolved using
440 +Normally the base filename is the name of
441 +the file in which the storage object identifier was
442 +specified, but this can be changed using the
445 +The filename will be searched for first in the directory of
447 +If it is not found there,
448 +then it will be searched for in directories specified with the
450 +option in the order in which they were specified on the command line,
451 +and then in the list of directories
452 +specified by the environment variable
453 +.BR \s-1SGML_SEARCH_PATH\s0 .
454 +The list is separated by colons under Unix
455 +and by semi-colons under MSDOS.
458 +The storage object identifier is an integer specifying a file descriptor.
459 +Thus a system identifier of
461 +will refer to the standard input.
464 +The storage object identifier is a URL.
467 +scheme is currently supported and not on all systems.
470 +The storage manager is the storage manager of storage object
471 +in which the system identifier was specified
473 +.IR "underlying storage manager" ).
474 +However if the underlying storage manager does not support named
475 +storage objects (ie it is
477 +then the storage manager will be
479 +The storage object identifier is treated as a relative, hierarchical
480 +name separated by slashes
482 +and will be transformed as appropriate for the underlying storage manager.
484 +The following attributes are supported:
487 +This describes how records are delimited in the storage object:
491 +Records are terminated by a carriage return.
494 +Records are terminated by a line feed.
497 +Records are terminated by a carriage return followed by a line feed.
500 +Records are terminated by whichever of
505 +is first encountered in the storage object.
508 +No recognition of records is performed.
512 +except for NDATA entities for which the default is
515 +When records are recognized in a storage object,
516 +a record start is inserted at the beginning of
517 +each record, and a record end at the end of each record. If there is a
518 +partial record (a record that doesn't end with the record terminator)
519 +at the end of the entity, then a record start will be inserted before it
520 +but no record end will be inserted after it.
522 +The attribute name and
524 +can be omitted for this attribute.
528 +This specifies whether a Control-Z character that occurs as the final byte
529 +in the storage object should be stripped.
530 +The following values are allowed:
534 +A final Control-Z should be stripped.
537 +A final Control-Z should not be stripped.
541 +except for NDATA entities,
542 +entities declared in storage objects with
544 +and storage objects with
547 +The attribute name and
549 +can be omitted for this attribute.
553 +The bctf (bit combination transformation format)
554 +attribute describes how the bit combinations of the
555 +storage object are transformed into the sequence of bytes
556 +that are contained in the object identified by the storage object identifier.
557 +This inverse of this transformation is performed when the entity manager
558 +reads the storage object.
559 +It has one of the following values:
563 +Each bit combination is represented by a single
567 +Each bit combination is represented by exactly 2
568 +bytes, with the more significant byte first.
571 +Each bit combination is represented by a variable
572 +number of bytes according to UCS Transformation
573 +Format 8 defined in Annex P to be added by the first
574 +proposed drafted amendment (PDAM 1) to ISO/IEC
578 +Each bit combination is treated as a pair of bytes, most significant
579 +byte first, encoding a character using the
580 +Extended_UNIX_Code_Fixed_Width_for_Japanese Internet charset, and is
581 +transformed into the variable length sequence of octets that would
582 +encode that character using the
583 +Extended_UNIX_Code_Packed_Format_for_Japanese Internet charset.
586 +Each bit combination is treated as a pair of bytes, most significant
587 +byte first, encoding a character using the
588 +Extended_UNIX_Code_Fixed_Width_for_Japanese Internet charset, and is
589 +transformed into the variable length sequence of bytes that would
590 +encode that character using the Shift_JIS Internet charset.
593 +Each bit combination is represented by 2 bytes.
594 +The bytes representing the entire storage object may be preceded
595 +by a pair of bytes representing the byte order mark character (0xFEFF).
596 +The bytes representing each bit combination are in the system byte order,
597 +unless the byte order mark character is present, in which case
598 +the order of its bytes determines the byte order.
599 +When the storage object is read, any byte order mark character
604 +can be any single digit other than 0.
605 +Each bit combination is interpreted as the number of a character
606 +in ISO/IEC 10646 and is represented by the single byte that would
607 +encode that character in ISO
609 +These values are not supported with the
615 +are supported only with the multi-byte version of
620 +This specifies whether line boundaries should be tracked
624 +specifies that they should;
627 +specifies that they should not.
628 +The default value is
630 +Keeping track of where line boundaries occur in a storage object
631 +requires approximately one byte of storage per line
632 +and it may be desirable to disable this for very large storage objects.
634 +The attribute name and
636 +can be omitted for this attribute.
639 +When the storage object identifier specified in the content of the
640 +storage object specification is relative, this specifies the base
641 +storage object identifier relative to which that storage object
642 +identifier should be resolved.
643 +When not specified a storage object identifier is interpreted
644 +relative to the storage object in which it is specified,
645 +provided that this has the same storage manager.
646 +This applies both to system identifiers specified in SGML
647 +documents and to system identifiers specified in the catalog entry
651 +The value is a single character that will be recognized
652 +in storage object identifiers
653 +(both in the content of storage object specifications
657 +as a storage manager character reference delimiter
658 +when followed by a digit.
659 +A storage manager character reference is like an SGML numeric character
660 +reference except that the number is interpreted as a character number
661 +in the inherent character set of the storage manager rather than
662 +the document character set.
663 +The default is for no character to be recognized as
664 +a storage manager character reference delimiter.
665 +Numeric character references cannot be used to prevent
666 +recognition of storage manager character reference delimiters.
669 +This applies only to the
672 +It specifies whether the storage object identifier should
673 +be folded to the customary case of the underlying storage manager
674 +if storage object identifiers for the underlying storage manager
676 +The following values are allowed:
680 +The storage object identifier will be folded.
683 +The storage object identifier will not be folded.
685 +The default value is
687 +The attribute name and
689 +can be omitted for this attribute.
691 +For example, on Unix filenames are case-sensitive and the customary
693 +So if the underlying storage manager were
695 +and the system was a Unix system, then
696 +.B \%<neutral>FOO.SGM
697 +would be equivalent to
698 +.BR \%<osfile>foo.sgm .
701 +A simple system identifier is interpreted as a storage object identifier
702 +with a storage manager that depends on where the system identifier
704 +if it was specified in a storage object whose storage manager was
706 +or if the system identifier looks like an absolute URL in a supported scheme,
707 +the storage manager will be
709 +otherwise the storage manager will be
711 +The storage manager attributes are defaulted as for a formal system
713 +Numeric character references are not recognized in simple system
715 +.SS "System identifier generation"
716 +The entity manager generates an effective system identifier for every external
717 +entity using catalog entry files in the format defined
718 +by SGML Open Technical Resolution 9401:1994.
719 +The entity manager will give an error if it is unable to generate
720 +an effective system identifier for an external entity.
721 +Normally if the external identifier for an entity includes a system
722 +identifier then the entity manager will use that as the
723 +effective system identifier for
724 +the entity; this behaviour can be changed using OVERRIDE or SYSTEM
725 +entries in a catalog entry file.
727 +A catalog entry file contains a
728 +sequence of entries in one of the following forms:
730 +.BI PUBLIC\ pubid\ sysid
733 +should be used as the effective system identifier if the public
737 +is a system identifier as defined in ISO 8879 and
739 +is a public identifier as defined in ISO 8879.
741 +.BI ENTITY\ name\ sysid
744 +should be used as the effective system identifier if the entity is a general
745 +entity whose name is
748 +.BI ENTITY\ % name\ sysid
751 +should be used as the effective system identifier if the entity is a parameter
752 +entity whose name is
754 +Note that there is no space between the
759 +.BI DOCTYPE\ name\ sysid
762 +should be used as the effective system identifier if the entity is an
763 +entity declared in a document type declaration whose document type name is
766 +.BI LINKTYPE\ name\ sysid
769 +should be used as the effective system identifier if the entity is an
770 +entity declared in a link type declaration whose link type name is
773 +.BI NOTATION\ name\ sysid
776 +should be used as the effective system identifier for a notation whose name is
778 +This is an extension to the SGML Open format.
779 +This is relevant only with the
783 +.B OVERRIDE\ YES\fR|\fPNO
784 +This sets the overriding mode for entries up to the next
785 +occurrence of OVERRIDE or the end of the catalog entry file.
786 +At the beginning of a catalog entry file the overriding mode
788 +A PUBLIC, ENTITY, DOCTYPE, LINKTYPE or NOTATION entry with an overriding
789 +mode of YES will be used whether or not the external identifier
790 +has an explicit system identifier;
791 +those with an overriding mode of NO will be ignored if
792 +external identifier has an explicit system identifier.
793 +This is an extension to the SGML Open format.
795 +.BI SYSTEM\ sysid1\ sysid2
798 +should be used as the effective system identifier if the system identifier
799 +specified in the external identifier was
801 +This is an extension to the SGML Open format.
804 +This specifies that if the document does not contain an SGML declaration,
805 +the SGML declaration in
810 +This specifies that the document entity is
812 +This entry is used only with the
819 +is the system identifier of an additional catalog entry file to be
820 +read after this one.
823 +entries are allowed and will be read in order.
824 +This is an extension to the SGML Open format.
826 +The delimiters can be omitted from the
828 +provided it does not contain any white space.
829 +Comments are allowed between parameters delimited by
833 +The environment variable
834 +.B \s-1SGML_CATALOG_FILES\s0
835 +contains a list of catalog entry files.
836 +The list is separated by colons under Unix
837 +and by semi-colons under MSDOS.
838 +These will be searched after any catalog entry files specified
842 +and after the catalog entry file called
844 +in the same place as the document entity.
845 +If this environment variable is not set,
846 +then a system dependent list of catalog entry files will be used.
847 +In fact catalog entry files are not restricted to being files:
848 +the name of a catalog entry file is interpreted as a system identifier.
850 +A match in one catalog entry file will take precedence
851 +over any match in a later catalog entry file.
852 +A match in a catalog entry file for a SYSTEM entry will take
853 +precedence over a match in the same file for a PUBLIC, ENTITY,
854 +DOCTYPE, LINKTYPE or NOTATION entry.
855 +A match in a catalog entry file for a PUBLIC entry will take
856 +precedence over a match in the same file for an ENTITY,
857 +DOCTYPE, LINKTYPE or NOTATION entry.
860 +.SS "System declaration"
861 +The system declaration for
867 +c1 s1 s1 s1 s1 s1 s1 s1 s
882 +SYSTEM "ISO 8879:1986"
884 +BASESET&"ISO 646-1983//CHARSET
885 +&\h'\w'"'u'International Reference Version (IRV)//ESC 2/5 4/0"
887 +CAPACITY&PUBLIC&"ISO 8879:1986//CAPACITY Reference//EN"
889 +MINIMIZE&DATATAG&NO&OMITTAG&YES&RANK&YES&SHORTTAG&YES
890 +LINK&SIMPLE&YES 65535&IMPLICIT&YES&EXPLICIT&YES 1
891 +OTHER&CONCUR&NO&SUBDOC&YES 100&FORMAL&YES
893 +SYNTAX&PUBLIC&"ISO 8879:1986//SYNTAX Reference//EN"
894 +SYNTAX&PUBLIC&"ISO 8879:1986//SYNTAX Core//EN"
896 +&GENERAL&YES&MODEL&YES&EXCLUDE&YES&CAPACITY&NO
897 +&NONSGML&YES&SGML&YES&FORMAL&YES
905 +The limit for the \s-1SUBDOC\s0 parameter is memory dependent.
907 +Any legal concrete syntax may be used.
908 +.SS "\*S declaration"
909 +If the \*S declaration is omitted
910 +and there is no applicable
913 +the following declaration will be implied:
916 +c1 s1 s1 s1 s1 s1 s1 s1 s
919 +<!SGML "ISO 8879:1986"
921 +BASESET&"ISO 646-1983//CHARSET
922 +&\h'\w'"'u'International Reference Version (IRV)//ESC 2/5 4/0"
923 +DESCSET&\0\00\0\09\0UNUSED
933 +CAPACITY&PUBLIC&"ISO 8879:1986//CAPACITY Reference//EN"
936 +SHUNCHAR&CONTROLS 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
937 +&18 19 20 21 22 23 24 25 26 27 28 29 30 31 127 255
938 +BASESET&"ISO 646-1983//CHARSET International Reference Version
939 +&\h'\w'"'u'(IRV)//ESC 2/5 4/0"
951 +&NAMECASE&GENERAL&YES
953 +DELIM&GENERAL&SGMLREF
977 +LINK&SIMPLE&YES\01000
981 +&SUBDOC&YES\099999999
987 +with the exception that all characters that are neither significant
988 +not shunned will be assigned to \s-1DATACHAR\s0.
990 +A character in a base character set is described either by giving its
991 +number in a universal character set, or by specifying a minimum
992 +literal. The constraints on the choice of universal character set are
993 +that characters that are significant in the SGML reference concrete
994 +syntax must be in the universal character set and must have the same
995 +number in the universal character set as in ISO 646 and that each
996 +character in the character set must be represented by exactly one
997 +number; that character numbers in the range 0 to 31 and 127 to 159 are
998 +control characters (for the purpose of enforcing SHUNCHAR CONTROLS).
999 +It is recommended that ISO 10646 (Unicode) be used as the universal
1000 +character set, except in environments where the normal document
1001 +character sets are large character set which cannot be compactly
1002 +described in terms of ISO 10646.
1003 +The public identifier of a base character set can be associated
1004 +with an entity that describes it by using a
1006 +entry in the catalog entry file.
1007 +The entity must be a fragment
1008 +of an SGML declaration
1010 +portion of a character set description,
1011 +following the DESCSET keyword,
1012 +that is, it must be a sequence of character descriptions,
1013 +where each character description specifies a described character
1014 +number, the number of characters and
1015 +either a character number in the universal character set, a minimum literal
1018 +Character numbers in the universal character set can be as big as
1023 +has built in knowledge of a few character sets.
1024 +These are identified using the designating sequence in the
1025 +public identifier. The following designating sequences are
1033 +Designating&ISO&Minimum&Number&Description
1034 +Escape&Registration&Character&of&
1035 +Sequence&Number&Number&Characters&
1037 +ESC 2/5 4/0&-&0&128&full set of ISO 646 IRV
1038 +ESC 2/8 4/0&2&0&128&G0 set of ISO 646 IRV
1039 +ESC 2/8 4/2&6&0&128&G0 set of ASCII
1040 +ESC 2/1 4/0&1&0&32&C0 set of ISO 646
1043 +The graphic character sets do not strictly include
1044 +C0 and C1 control character sets.
1047 +augments the graphic character sets with the appropriate
1048 +control character sets.
1050 +It is not necessary for every character set used in the SGML
1051 +declaration to be known to
1053 +provided that characters in the document character set that are
1054 +significant both in the reference concrete syntax and in the described
1055 +concrete syntax are described using known base character sets and that
1056 +characters that are significant in the described concrete syntax are
1057 +described using the same base character sets or the same minimum
1058 +literals in both the document character set description and the syntax
1059 +reference character set description.
1061 +The public identifier for a public concrete syntax can be associated
1062 +with an entity that describes using a
1064 +entry in the catalog entry file.
1065 +The entity must be a fragment of an SGML declaration
1066 +consisting of a concrete syntax description
1070 +as in an SGML declaration.
1071 +The entity can also make use of the following extensions:
1075 +can be expressed as a parameter literal
1078 +The replacement for a reference reserved name
1079 +can be expressed as a parameter literal instead of a name.
1087 +keywords may each be followed by more than one parameter literal. A
1088 +sequence of parameter literals has the same meaning as a single
1089 +parameter literal whose content is the concatenation of the content of
1090 +each of the literals in the sequence. This extension is useful
1091 +because of the restriction on the length of a parameter literal in the
1092 +SGML declaration to 240 characters.
1094 +The total number of characters specified for
1098 +may exceed the total number of characters specified for
1107 +which does not have a corresponding character in the same position in
1111 +is simply assigned to UCNMCHAR or UCNMSTRT
1112 +without making it the upper-case form of any character.
1114 +A parameter following any of
1124 +and another parameter literal.
1125 +This has the same meaning as the two parameter literals
1126 +with a parameter literal in between
1127 +containing in order each character whose number
1128 +is greater than the number of the last character in
1129 +the first parameter literal and less than the
1130 +number of the first character in the second
1132 +A parameter literal must contain at least one character for each
1134 +to which it is adjacent.
1136 +A number may be used as a parameter following the
1142 +keywords or as a delimiter in the
1144 +section with the same meaning as a parameter literal
1145 +containing just a numeric character reference with that number.
1147 +The parameters following the
1153 +keywords may be omitted.
1154 +This has the same meaning as specifying
1155 +an empty parameter literal.
1157 +Within the specification of the short reference delimiters,
1158 +a parameter literal containing exactly one character
1159 +may be followed by the name token
1161 +and another parameter literal containing exactly one character.
1162 +This has the same meaning as a sequence of parameter literals
1163 +one for each character number that is greater than or equal
1164 +to the number of the character in the first parameter literal
1165 +and less than or equal to the number of the character in the
1166 +second parameter literal.
1168 +The public identifier for a public capacity set can be associated
1169 +with an entity that describes using a
1171 +entry in the catalog entry file.
1172 +The entity must be a fragment of an SGML declaration
1173 +consisting of a sequence of capacity names and numbers.
1174 +.SS "Output format"
1175 +The output is a series of lines.
1176 +Lines can be arbitrarily long.
1177 +Each line consists of an initial command character
1178 +and one or more arguments.
1179 +Arguments are separated by a single space,
1180 +but when a command takes a fixed number of arguments
1181 +the last argument can contain spaces.
1182 +There is no space between the command character and the first argument.
1183 +Arguments can contain the following escape sequences.
1190 +A record end character.
1193 +Internal \s-1SDATA\s0 entities are bracketed by these.
1196 +The character whose code is
1200 +A record start character will be represented by
1202 +Most applications will need to ignore
1209 +The character whose number is
1213 +can have any number of digits.
1214 +This is used for characters that are not representable by the
1215 +encoding translation used for output
1216 +(as specified by the
1219 +environment variable).
1220 +This will only occur with the multibyte version of nsgmls.
1222 +The possible command characters and arguments are as follows:
1225 +The start of an element whose generic identifier is
1227 +Any attributes for this element
1228 +will have been specified with
1233 +The end of an element whose generic identifier is
1240 +A reference to an external data entity
1243 +will have been defined using an
1248 +A processing instruction with data
1252 +The next element to start has an attribute
1256 +which takes one of the following forms:
1260 +The value of the attribute is implied.
1263 +The attribute is character data.
1264 +This is used for attributes whose declared value is
1267 +.BI NOTATION\ nname
1268 +The attribute is a notation name;
1270 +will have been defined using a
1273 +This is used for attributes whose declared value is
1274 +.BR \s-1NOTATION\s0 .
1276 +.BI ENTITY\ name\|.\|.\|.
1277 +The attribute is a list of general entity names.
1278 +Each entity name will have been defined using an
1284 +This is used for attributes whose declared value is
1287 +.BR \s-1ENTITIES\s0 .
1289 +.BI TOKEN\ token\|.\|.\|.
1290 +The attribute is a list of tokens.
1291 +This is used for attributes whose declared value is anything else.
1294 +The attribute is an ID value.
1295 +This will be output only if the
1297 +option is specified.
1300 +will be used for ID values.
1303 +.BI D ename\ name\ val
1304 +This is the same as the
1306 +command, except that it specifies a data attribute for an
1307 +external entity named
1311 +commands will come after the
1313 +command that defines the entity to which they apply, but
1318 +commands that reference the entity.
1320 +.BI a type\ name\ val
1321 +The next element to start has a link attribute with link type
1327 +which takes the same form as with the
1334 +This command will be preceded by a
1336 +command if the notation was declared with a public identifier,
1339 +command if the notation was declared with a system identifier.
1342 +option was specified,
1343 +this command will also be preceded by an
1345 +command giving the system identifier generated by the entity manager
1346 +(unless it was unable to generate one).
1347 +A notation will only be defined if it is to be referenced
1352 +command for an attribute with a declared value of
1353 +.BR \s-1NOTATION\s0 .
1355 +.BI E ename\ typ\ nname
1356 +Define an external data entity named
1360 +.RB ( \s-1CDATA\s0 ,
1366 +This command will be preceded by an
1368 +command giving the system identifier generated by the entity manager
1369 +(unless it was unable to generate one),
1372 +command if a public identifier was declared for the entity,
1375 +command if a system identifier was declared for the entity.
1377 +will have been defined using a
1380 +Data attributes may be specified for the entity using
1385 +option is not specified,
1386 +an external data entity will only be defined if it is to be referenced in a
1390 +command for an attribute whose declared value is
1393 +.BR \s-1ENTITIES\s0 .
1395 +.BI I ename\ typ\ text
1396 +Define an internal data entity named
1410 +option was specified,
1411 +in which case it can also be
1415 +(for an \*S text entity).
1418 +option is not specified,
1419 +an internal data entity will only be defined if it is referenced in an
1421 +command for an attribute whose declared value is
1424 +.BR \s-1ENTITIES\s0 .
1427 +Define a subdocument entity named
1429 +This command will be preceded by an
1431 +command giving the system identifier generated by the entity manager
1432 +(unless it was unable to generate one),
1435 +command if a public identifier was declared for the entity,
1438 +command if a system identifier was declared for the entity.
1441 +option is not specified,
1442 +a subdocument entity will only be defined if it is referenced
1448 +command for an attribute whose declared value is
1451 +.BR \s-1ENTITIES\s0 .
1454 +Define an external SGML text entity named
1456 +This command will be preceded by an
1458 +command giving the system identifier generated by the entity manager
1459 +(unless it was unable to generate one),
1462 +command if a public identifier was declared for the entity,
1465 +command if a system identifier was declared for the entity.
1466 +This command will be output only if the
1468 +option is specified.
1471 +This command applies to the next
1477 +command and specifies the associated system identifier.
1480 +This command applies to the next
1486 +command and specifies the associated public identifier.
1489 +This command applies to the next
1495 +option was specified,
1497 +command and specifies the system identifier
1498 +generated by the entity manager from the specified external identifier
1499 +and other information about the entity or notation.
1502 +The start of the \*S subdocument entity
1505 +will have been defined using a
1510 +The end of the \*S subdocument entity
1516 +Set the current line number and filename.
1519 +argument will be omitted if only the line number has changed.
1520 +This will be output only if the
1522 +option has been given.
1525 +An \s-1APPINFO\s0 parameter of
1527 +was specified in the \*S declaration.
1528 +This is not strictly part of the ESIS, but a structure-controlled
1529 +application is permitted to act on it.
1532 +command will be output if
1533 +.B \s-1APPINFO\s0\ \s-1NONE\s0
1537 +command will occur at most once,
1538 +and may be preceded only by a single
1543 +This command indicates that the document was a conforming \*S document.
1544 +If this command is output, it will be the last command.
1545 +An \*S document is not conforming if it references a subdocument entity
1546 +that is not conforming.
1551 +If this is set to one of
1557 +then that BCTF will be used as the default BCTF
1558 +for everything (including file input, file output, message output,
1559 +filenames and command line arguments).
1561 +The \*S Handbook, Charles F. Goldfarb
1563 +\s-1ISO\s0 8879 (Standard Generalized Markup Language),
1564 +International Organization for Standardization
1569 +is all ESIS information for LINK is reported.
1572 +James Clark (jjc@jclark.com).
1573 diff -Nru jade-1.2.1/spam/spam.1 jade-1.2.1.new/spam/spam.1
1574 --- jade-1.2.1/spam/spam.1 Thu Jan 1 01:00:00 1970
1575 +++ jade-1.2.1.new/spam/spam.1 Tue Sep 21 22:48:19 1999
1581 +spam \- an SGML markup stream editor
1583 +An \*S System Conforming to
1585 +International Standard ISO 8879 \(em
1587 +Standard Generalized Markup Language
1594 +.BI \-c catalog_file
1603 +.BI \-m markup_option
1606 +.BI \-o entity_name
1609 +.BI \-w warning_type
1613 +This manual page may be out of date. Consult the HTML documentation for
1614 +the most up-to-date information concerning this program.
1618 +is an SGML markup stream editor implemented using the SP parser.
1620 +parses the SGML document contained in
1622 +and copies to the standard output
1623 +the portion of the document entity containing the document
1624 +instance, adding or changing markup as specified by the
1629 +option can be used to include the SGML declaration and prolog
1633 +option can be used to output other entities.
1636 +option can be used to expand entity references.
1638 +For more information about the underlying SGML parser and entity
1642 +The following options are available:
1645 +Use the catalog entry file
1651 +for files specified in system identifiers.
1654 +options are allowed.
1657 +for more information about file searching.
1660 +Describe open entities in error messages.
1665 +This is useful mainly with shells that do not support redirection
1669 +Hoist omitted tags out from the start of internal entities.
1670 +If the text at the beginning of an internal entity causes
1671 +a tag to be implied,
1672 +the tag will usually be treated as being in that internal entity;
1673 +this option will instead cause it to be treated as being in the entity
1674 +that referenced the internal entity.
1675 +This option makes a difference in conjunction with
1684 +.BI <!ENTITY\ %\ name\ \(tsINCLUDE\(ts>
1686 +occurs at the start of the document type declaration subset
1687 +in the \*S document entity.
1692 +Added names that were subject to upper-case substitution
1693 +will be converted to lower-case.
1695 +.BI \-m markup_option
1696 +Change the markup in the output according to the value
1703 +Add tags that were omitted using omitted tag minimization.
1704 +End tags that were omitted because the element has
1705 +a declared content of
1707 +or an explicit content reference
1711 +Replace short references by named entity references.
1714 +Change null end-tags
1715 +into unminimized end-tags,
1716 +and change net-enabling start-tags
1717 +into unminimized start-tags.
1720 +Change empty tags into unminimized tags.
1723 +Change unclosed tags into unminimized tags.
1726 +Add omitted attribute names and
1730 +Add literal delimiters omitted from attribute values.
1733 +Add omitted attribute specifications.
1736 +Add omitted attribute specifications for current attributes.
1737 +This option is implied by the
1742 +Equivalent to combination of
1753 +Add omitted rank suffixes.
1756 +Put reserved names in upper-case.
1759 +Remove marked section declarations whose effective status
1760 +is IGNORE, and replace each marked section declaration
1761 +whose effective status is INCLUDE by its marked section.
1762 +In the document instance, empty comments will be added
1763 +before or after the marked section declaration to ensure
1764 +that ignored record ends remain ignored.
1768 +options are allowed.
1772 +Output the general entity
1774 +instead of the document entity.
1775 +The output will correspond to the first time
1776 +that the entity is referenced in content.
1779 +Output the part of the document entity containing the SGML declaration
1780 +(if it was explicitly present in the document entity)
1781 +and the prolog before anything else.
1782 +If this option is specified two or more times,
1783 +then all entity references occurring between declarations
1784 +in the prolog will be expanded;
1785 +this includes the implicit reference to the entity
1786 +containing the external subset of the DTD, if there is one.
1787 +Note that the SGML declaration will not be included if it was
1788 +specified by an SGMLDECL entry in a catalog.
1791 +Don't perform any conversion on RSs and REs when outputting the entity.
1792 +The entity would typically have the storage manager attribute
1796 +Print the version number.
1799 +Control warnings and errors according to
1803 +for the allowed values of
1807 +Expand references to entities that are changed.
1808 +If this option is specified two or more times,
1809 +then all references to entities that contain tags
1813 +Omitted tags are added at the point where they are
1814 +implied by the SGML parser (except as modified
1817 +option); this is often not quite where they are wanted.
1819 +The case of general delimiters is not preserved.
1821 +Incorrect results may be produced if a variant concrete syntax is used
1822 +which is such that there are delimiters in markup to be added that have a
1823 +prefix that is a proper suffix of some other delimiter.
1825 +If an entity reference in a default value uses the default entity and
1826 +an entity with that name is subsequently defined and that default
1827 +value is added to the document instance, then the resulting document
1828 +may not be equivalent to the original document.
1830 +will give a warning when the first two conditions are met.
1833 +James Clark (jjc@jclark.com).
1836 diff -Nru jade-1.2.1/spent/spent.1 jade-1.2.1.new/spent/spent.1
1837 --- jade-1.2.1/spent/spent.1 Thu Jan 1 01:00:00 1970
1838 +++ jade-1.2.1.new/spent/spent.1 Tue Sep 21 22:48:19 1999
1842 +spent \- print SGML entity on the standard output
1853 +This manual page may be out of date. Consult the HTML documentation for
1854 +the most up-to-date information concerning this program.
1857 +(SGML print entity)
1858 +prints the concatenation of the entities with system identifiers
1860 +on the standard output.
1861 +The format of the system identifiers is described in
1864 +The following options are available:
1867 +Use the BCTF with name
1870 +Available BCTFs are described in
1874 +Don't perform any conversion on RSs and REs when printing the entity.
1875 +The entity would typically have the storage manager attribute
1879 +Print the version number.
1882 +James Clark (jjc@jclark.com).
projects / packages / JADE.git / blob