Overview
Comment: | fix incorrect plural |
---|---|
Downloads: | Tarball | ZIP archive | SQL archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA3-256: |
3f5d6b4b81998118f08d29288d4d95d2 |
User & Date: | lexi on 2024-03-15 18:02:25 |
Other Links: | manifest | tags |
Context
2024-05-07
| ||
19:25 | unbreak build (oops sorry about that) check-in: b4009ca1bd user: lexi tags: trunk | |
2024-03-15
| ||
18:02 | fix incorrect plural check-in: 3f5d6b4b81 user: lexi tags: trunk | |
17:20 | relicense future versions under AGPLv3; the EUPL is not a sane FOSS license for American jurisdictions check-in: f552ca3518 user: lexi tags: trunk | |
Changes
Modified cortav.ct from [6249e7c67c] to [4b83863e2a].
576 576 * {d expand} causes the next object (usually a code block) to be fully expanded when it would otherwise not be 577 577 * {d font} controls the font stack, for outputs that support changing fonts. see [>fonts fonts] for more information. 578 578 * {d lang} changes the current language, which is used by extensions to e.g. control typographical conventions, and may be encoded into the output by certain renderers (e.g. HTML). note that quotes and blockquotes can be set to a separate language with a simpler syntax. the language should be notated using IETF language tags 579 579 ** {dd lang is|x-ranuir-Cent-CR8} sets the current language to Ranuir as spoken in the Central Worlds, written in Corran and encoded using C6B+U8L (which can also be interpreted as UTF-8, albeit with some lost semantics). this might be used at the top of a document to set its primary language. 580 580 ** {dd lang push|gsw-u-sd-chzh} temporarily switches to Zürich German, e.g. to quote a German passage in an otherwise Ranuir document 581 581 ** {dd lang sec|en-US} switches to American English for the duration of a section. does not affect the language stack. 582 582 ** {d lang pop} drops the current language off the language stack, returning to whatever was pushed or set before it. this would be used, for instance, at the end of a passage 583 -* {d pragma} supplies semantic data about author intent, the kind of information the document contains and hints about how it should be displayed to the user. think of them like offhand remarks to the renderer -- there's no guarantee that it'll pay any attention, but if it does, your document will look better. pragmas have no scope; they affect the entire document. the pragma function exists primarily as a means to allow parameters that would normally need to be specified on e.g. the command line to be encoded in the document instead in a way that multiple implementations can understand. a few standard pragmas are defined. 583 +* {d pragma} supplies semantic data about author intent, the kind of information the document contains and hints about how it should be displayed to the user. think of them like offhand remarks to the renderer -- there's no guarantee that it'll pay any attention, but if it does, your document will look better. pragmata have no scope; they affect the entire document. the pragma function exists primarily as a means to allow parameters that would normally need to be specified on e.g. the command line to be encoded in the document instead in a way that multiple implementations can understand. a few standard pragmata are defined. 584 584 ** {d pragma layout} gives a hint on how the document should be layed out. the first hint that is understood will be applied; all others will be discarded. standard hints include: 585 585 *** [`essay] 586 586 *** [`narrative] 587 587 *** [`screenplay]: uses asides to denote actions, quotes for dialogue 588 588 *** [`stageplay]: uses asides to denote actions, quotes for dialogue 589 589 *** [`manual] 590 590 *** [`glossary] ................................................................................ 595 595 ***: [*heading]: the section can occur on the same page as text and headings from other sections 596 596 ** {d pragma accent} specifies an accent hue (in degrees around the color wheel) for renderers which support colorized output 597 597 ** {d pragma accent-spread} is a factor that controls the "spread" of hues used in the document. if 0, only the accent color will be used; if larger, other hues will be used in addition to the primary accent color. 598 598 ** {d pragma dark-on-light on\|off} controls whether the color scheme used should be light-on-dark or dark-on-light 599 599 ** {d pragma page-width} indicates how wide the pages should be 600 600 ** {d pragma title-page} specifies a section to use as a title page, for renderer backends that support pagination 601 601 602 -! note on pragmata: particularly when working with collections of documents, you should not keep shared formatting metadata duplicated across the documents themselves! the best thing to do is to have a makefile for compiling the documents using whatever tools you want to support, and encoding the rendering options in this file (for the reference implementation this currently means as command line arguments, but eventually it will support intent files as well) so they can all be changed in one place; pragmas should instead be used for per-document [*overrides] of default settings. 602 +! note on pragmata: particularly when working with collections of documents, you should not keep shared formatting metadata duplicated across the documents themselves! the best thing to do is to have a makefile for compiling the documents using whatever tools you want to support, and encoding the rendering options in this file (for the reference implementation this currently means as command line arguments, but eventually it will support intent files as well) so they can all be changed in one place; pragmata should instead be used for per-document [*overrides] of default settings. 603 603 ! a workaround for the lack of intent files in the reference implementation is to have a single pseudo-stylesheet that contains only {d pragma} statements, and then import this file from each individual source file using the {d include} directive. this is suboptimal and recommended only when you need to ensure compatibility between different implementations. 604 604 ! when creating HTML files, an even better alternative may be to turn off style generation entirely and link in an external, hand-written CSS stylesheet. this is generally the way you should compile sources for existing websites if you aren't going to write your own extension. 605 605 606 606 ##ex examples 607 607 608 608 ~~~ blockquotes #bq [cortav] ~~~ 609 609 the following excerpts of text were recovered from a partially erased hard drive found in the Hawthorne manor in the weeks after the Incident. context is unknown.