cortav  Check-in [7b6c406de4]

Modified cortav.ct from [3240d0f3f3] to [718eb3ed50].

   102    102   ** [`~~~ \[language\] title ~~~]
   103    103   ** [`~~~ title \[language\] #id ~~~]
   104    104   *[*reference] (tab): a line beginning with a tab is treated as a "reference." references hold out-of-line metadata for preceding text like links and footnotes. a reference consists of an identifier followed by a colon and an arbitrary number of spaces or tabs, followed by text. whether this text is interpreted as raw-text or styled-text depends on the context in which the reference is used. in encodings without tab characters, two preceding blanks can be used instead.
   105    105   * [*quotation] ([`<]): a line of the form [`<[$name]> [$quote]] denotes an utterance by [$name].
   106    106   * [*blockquote] ([`>]): alternate blockquote syntax. can be nested by repeating the [`>] character.
   107    107   * [*subtitle/caption] ([`\--]): attaches a subtitle to the previous header, or caption to the previous object
   108    108   * [*embed] ([`&]): embeds a referenced object. can be used to show images or repeat previously defined objects like lists or tables, optionally with a caption.
   109         -** [`&$[$macro] [$arg1]|[$arg2]|[$argn]…] invokes a block-level macro with the supplied arguments
   110         -*** [`&$mymacro arg 1|arg 2|arg 3]
          109  +** [`$[$macro] [$arg1]|[$arg2]|[$argn]…] invokes a block-level macro with the supplied arguments
          110  +*** [`$mymacro arg 1|arg 2|arg 3]
   111    111   ** [`&[$image]] embeds an image or other block-level object. [!image] can be a reference with a url or file path, or it can be an embed section (e.g. for SVG files)
   112    112   ***[`&myimg All that remained of the unfortunate blood magic pageant contestants and audience (police photo)]
   113    113   ** [`&-[$ident] [$styled-text]] embeds a closed disclosure element containing the text of the named object (a nonprinting section or cortav resource should usually be used to store the content; it can also name an image or video, of course). in interactive outputs, this will display as a block which can be clicked on to view the full contents of the referenced object [$ident]; if [$styled-text] is present, it overrides the title of the section you are embedding (if any). in static outputs, the disclosure object will display as an enclosed box with [$styled-text] as the title text
   114    114   *** [`&-ex-a Prosecution Exhibit A (GRAPHIC CONTENT)]
   115    115   ** [`&+[$section] [$styled-text]] is like the above, but the disclosure element is open by default
   116    116   * [*horizontal rule] ([`\---]): inserts a horizontal rule or other context break; does not end the section. must be followed by newline. underlines can also be used in place of dashes ([`___], [`-_-], [`__-__-__] etc), as can horizontal unicode box drawing characters ([`─ ━ ┈] etc).
   117    117   * [*page break] ([`\^^]): for formats that support pagination, like EPUB or HTML (when printed), indicates that the rest of the current page should be blank. for formats that do not, extra margins will be inserted. does not create a new section
................................................................................
   455    455   	cursive-quote: %font dup
   456    456   		%font set body=cursive
   457    457   		> [#1]
   458    458   		%font pop
   459    459   
   460    460   %% now, whenever we want a block with a cursive body, we can simply invoke
   461    461   
   462         -&$cursive-quote A sea of blood yet lies between us and the Destination. It won't impede me. And I'm so very proud to say that, apparently, it won't impede the Smiling Man either, if the Svalbard contract was any indication! [pause for laughter]
          462  +$cursive-quote A sea of blood yet lies between us and the Destination. It won't impede me. And I'm so very proud to say that, apparently, it won't impede the Smiling Man either, if the Svalbard contract was any indication! [pause for laughter]
   463    463   
   464    464   %% without affecting the overall font context. in fact, since 'cursive-quote' creates
   465    465   %% its context using 'dup', it would import all font specifications besides 'body'
   466    466   %% from the environment it is invoked in
   467    467   ~~~
   468    468   
   469    469   you may have noticed the rather odd bit at the end of our font definition, with the [`dit] URI. the reasons for this are tragic. groff, while delightful, has a thoroughly antiquated understanding of fonts, and doesn't support normal font formats like truetype. groff ships with a limited number of fonts in its own format, identified by obscurantist letter code ([`HBI] is "Helvetica Bold Italic", for instance) and lacking normal metadata. for this reason, you'll have to tell cortav how you want your fonts translated.

Modified desk/cortav.xml from [bf85cd3996] to [dc63948a6a].

     1      1   <?xml version='1.0' encoding='UTF-8'?>
     2      2   <!--
     3      3    [ʞ] cortav.xml
     4      4     ~ lexi hale <lexi@hale.su>
     5      5     © AGPLv3
     6      6     ? Kate/kwrite-compatible syntax definition for the cortav markup format
     7      7     > ln cortav.xml $HOME/.local/share/org.kde.syntax-highlighting/syntax/
            8  +  ! NOTE: the Kate syntax engine cannot capture all the syntactic properties
            9  +          of Cortav. we do the best we can, but note the following important
           10  +          discrepancies:
           11  +
           12  +            1) the inline resource syntax allows a wide range of complex
           13  +               brackets pairs such as <!--:[ ]:--!>; the Kate syntax only
           14  +               accounts for the pair { }
     8     15   -->
     9     16   <language name='Cortav' version='1' kateversion='2.4' section='Markup' extensions='*.ct'>
    10     17   	<highlighting>
    11     18   		<list name='extension-directives'>
    12     19   			<item>uses</item>
    13     20   			<item>needs</item>
    14     21   			<item>inhibits</item>