DTINFOSTYLEDTD(5)

πŸ“¦
version 2.5.3 Β· 2 versions
, in nixos 26.05

πŸ’… dtinfoStyle.dtd β€” the style sheet glow-up guide

okay bestie, welcome to dtinfoStyle.dtd(5), the file formats girlie of the CDE manual. this is the dtinfo style sheet document type definition and she is, genuinely, the blueprint for how your docs get their whole look. πŸŽ€


✨ NAME ✨

dtinfoStyle.dtd β€” dtinfo style sheet document type definition. yes that's the whole name, she's concise, she's iconic.

🌸 DESCRIPTION 🌸

dtinfoStyle.dtd describes the SGML features available for specifying how a document should be rendered. so like β€” style sheets are the thing that associates the elements in a given document hierarchy with on-line or print formatting characteristics, and they're part of the DtInfo Toolkit. it's giving wardrobe department for your markup. πŸ‘‘

With dtinfo, you use a single style sheet to specify both print and online rendering of the elements in your DTD. one sheet, two lewks, no cap. The print and online feature sets match in function, description, and specification β€” with just four exceptions for print-specific features. literally only four, we love a consistent queen. ✨

πŸ¦‹ Basic Style Sheet Format πŸ¦‹

The basic style sheet format first defines autonumbers. Then, for each element (Path) the style sheet defines its feature set. for the full lore, see "Understanding Dtinfo Style Sheets" and "Creating a Style Sheet" in CDE: Information Manager Author's and Programmer's Guide.

You can also find an ASCII file of the dtinfoStyle.dtd in:

/nix/store/6waxpwr8lzfzc9ka48gl7yh60rqvlkdb-cde-2.5.3/infolib/%L/SGML/dtinfoStyle.dtd

go off, filesystem path. πŸ—‚οΈ

πŸ’œ AutoNumber πŸ’œ

To use system-generated number tokens in element formatting, first create an AutoNumber specification for each token stream. (Note that these tokens can only be used with the Prefix, Suffix, Header and Footer features.) iykyk β€” them's the rules, don't come for me.

A simple example is:

&<AutoNumber

        id=chapnum

        reset="Book Part"

        counter=chapter>

A more complex example is:

&<AutoNumber

        id=fignum

        type=UCroman

        initial="I"

        delta=l

        counter="FIG TABLE"

        reset=chap>

&<path>NUMITEM&</>

&<margin top=4pt bottom=4pt>

&<prefix>&<auto id=NumList>&</prefix>

where:

  • type β€” The kind of counter values: Arabic, UCalpha, LCalpha, UCroman, LCroman. The default value is Arabic. ✨
  • id β€” The unique name of this token. You can refer to this name, for example, in a Prefix. Required. 🫢
  • initial β€” The initial value for this token, which must be consistent with the Type. The default is 1.
  • delta β€” The value by which the system increments or decrements the token. The default is to increment by 1.
  • counter β€” The element(s) that cause this token to use the Delta to change values. Required. πŸ’…
  • reset β€” The element(s) that cause this token to reset to its initial value. Required. πŸ’…
heads up bestie: id, counter and reset are all flagged Required β€” skip them and your numbering is gonna have main character energy in the worst way. 😭

🌈 SEE ALSO 🌈


and that's the whole page, bestie β€” courtesy of the dtinfoStyle.dtd(file formats) corner of the manual, signing off with a lil sparkle. read the SEE ALSOs, they're literally right there. πŸ¦‹πŸ’–πŸŽ€

πŸ“¦ where this page comes from