2 SPDX-FileCopyrightText: 2024 Lady <https://www.ladys.computer/about/#lady>
3 SPDX-License-Identifier: CC0-1.0
7 <b>A make·file for X·M·L.</b>
9 <dfn>⛩📰 书社</dfn> aims to make it easy to generate websites with
10 X·S·L·T and G·N·U Make.
11 It is consequently only a good choice for people who like X·S·L·T and
12 G·N·U Make and wish it were easier to make websites with them.
14 It makes things easier by :—
16 - Automatically identifying source files and characterizing them by
17 type (X·M·L, text, or asset).
19 - Parsing supported text types into X·M·L trees.
21 - Enabling easy inclusion of source files within each other.
23 It aims to do this with zero dependencies beyond the programs already
24 installed on your computer†.
26 † Assuming an operating system with a fairly featureful, and
27 Posix‐compliant, development setup (e·g, Macintosh ≥ version 10.8).
28 In fact, on Linux you will probably need to install a few programs:
29 `libxml2-utils`, `xsltproc`, `sharutils`, and `pax`.
33 <i lang="cmn-Hans">书社</i> is a Chinese word meaning “publishing
36 The first character, <i lang="cmn-Hans">书</i>, is the simplified form
39 The second character, <i lang="cmn-Hans">社</i>, contemporarily means
40 “association”, but historically referred to the god of the soil and
41 related altars or festivities.
42 In Japanese, it is an alternate spelling for <i lang="ja">やしろ</i>,
43 the word for “Shinto shrine”.
45 The name <i lang="cmn-Hans">书社</i> was chosen to play on this pun, as
46 it is intended as a publishing program for webshrines.
48 In Ascii environments, ⛩📰 书社 should be written `Shushe`, following
49 the pinyin transliteration.
53 In most cases, ⛩📰 书社 aims to require only functionality which is
54 present in all Posix‐compliant (`POSIX.1-2001`) operating systems.
55 There are a few exceptions.
56 Details on particular programs are given below; if a program is not
57 listed, it is assumed that any Posix‐compliant implementation will
62 This is a Posix utility, but ⛩📰 书社 depends on functionality
63 introduced after `POSIX.1-2001` (the `-u` option, introduced in
65 Macintosh systems somewhat interestingly implement this option
66 correctly in legacy mode (`COMMAND_MODE=legacy`) but incorrectly by
67 default (despite claiming `POSIX.1-2008` conformance for this
69 [Note this erroneous comment claiming nanosecond & timezone are
70 extensions rather than standardized.][rdar-92753335]
71 Despite this, the default Macintosh implementation will still work with
72 ⛩📰 书社, with the caveat that the timestamp will only include a
73 fractional component when a Posix⹀compliant (e·g, Macintosh legacy or
74 G·N·U) implementation is used.
78 This is a Posix utility, but it was considered optional in
79 `POSIX.1-2001` (altho it was made mandatory in `POSIX.1-2008`) and
80 ⛩📰 书社 currently depends on unspecified behaviour.
81 It requires support for the following additional options :—
83 - **`-C`**, when supplied with `-m`, must be useable to compile a
84 `.mgc` magicfile for use with future invocations of `file`.
86 - **`--files-from`** must be useable to provide a file that `file`
87 should read file·names from, and `-` must be useable in this
88 context to specify the standard input.
90 - **`--mime-type`** must cause `file` to print the internet media type
91 of the file with no charset parameter.
93 - **`--separator`** must be useable to set the separator that `file`
94 uses to separate file names from types.
96 These options are implemented by the
97 [Fine Free File Command](https://darwinsys.com/file/), which is used
98 by most operating systems.
102 This is not a Posix utility.
103 Usage of `git` is optional, but recommended (and activated by default).
104 To disable it, set `GIT=`.
108 This is a Posix utility, but it is considered an optional Software
109 Development utility and ⛩📰 书社 currently depends on unspecified
111 ⛩📰 书社 requires specifically the G·N·U version of `make`, and
112 depends on functionality present in version 3.81 or later.
113 It is not expected to work in previous versions, or with other
114 implementations of Make.
118 This is a Posix utility, but it is not included in the Linux Standard
119 Base or installed by default in many distributions.
120 ⛩📰 书社 only requires support for the `ustar` format.
122 ### `uudecode` and `uuencode`
124 These are Posix utilities, but they were considered optional in
125 `POSIX.1-2001` (altho they are made mandatory in `POSIX.1-2008`) and
126 they are not included in the Linux Standard Base or installed by
127 default in many distributions.
128 The G·N·U [Sharutils](https://www.gnu.org/software/sharutils/) package
129 provides one implementation.
131 ### `xmlcatalog` and `xmllint`
133 These are not a Posix utilities.
134 They are a part of `libxml2`, but may need to be installed separately
135 on some platforms (e·g by the name `libxml2-utils`).
139 This is not a Posix utility.
140 It is a part of `libxslt`, but may need to be installed separately on
145 Place source files in `sources/` and run `make install` to compile
146 the result to `public/`.
147 Compilation involves the following steps :—
149 1. ⛩📰 书社 compiles all of the magic files in `magic/` into a single
150 file, `build/magic.mgc`.
152 2. ⛩📰 书社 processes all of the parsers in `parsers/` and determines
153 the list of supported plaintext types.
155 3. ⛩📰 书社 identifies all of the source files and includes and uses
156 `build/magic.mgc` to classify them by media type.
158 4. ⛩📰 书社 parses all plaintext and X·M·L source files and includes
159 and then builds a dependency tree between them.
161 5. ⛩📰 书社 uses the dependency tree to establish prerequisites for
164 6. ⛩📰 书社 compiles each output file to `build/result`.
166 7. ⛩📰 书社 copies most output files from `build/result` to
167 `build/public`, but it does some additional processing instead on
168 those which indicate a non‐X·M·L desired final output form.
170 8. ⛩📰 书社 copies the final resulting files to `public`.
172 You can use `make list` to list each identified source file or include
173 alongside its computed type and dependencies.
174 As this is a Make‐based program, steps will only be run if the
175 corresponding buildfile or output file is older than its
180 The ⛩📰 书社 name·space is `urn:fdc:ladys.computer:20231231:Shu1She4`.
182 This document uses a few name·space prefixes, with the following
185 | Prefix | Expansion |
186 | ---------: | :-------------------------------------------- |
187 | `catalog:` | `urn:oasis:names:tc:entity:xmlns:xml:catalog` |
188 | `exsl:` | `http://exslt.org/common` |
189 | `exslstr:` | `http://exslt.org/strings` |
190 | `html:` | `http://www.w3.org/1999/xhtml` |
191 | `svg:` | `http://www.w3.org/2000/svg` |
192 | `xlink:` | `http://www.w3.org/1999/xlink` |
193 | `xslt:` | `http://www.w3.org/1999/XSL/Transform` |
194 | `书社:` | `urn:fdc:ladys.computer:20231231:Shu1She4` |
196 ## Setup and Configuration
198 ⛩📰 书社 depends on the following programs to run.
199 In every case, you may supply your own implementation by overriding the
200 corresponding (allcaps) variable (e·g, set `MKDIR` to supply your own
201 `mkdir` implementation).
212 - `git` (optional; set `GIT=` to disable)
218 - `pax` (only when generating archives)
229 - `xmlcatalog` (provided by `libxml2`)
230 - `xmllint` (provided by `libxml2`)
231 - `xsltproc` (provided by `libxslt`)
233 The following additional variables can be used to control the behaviour
237 The location of the source files (default: `sources`).
238 Multiple source directories can be provided, so long as the same
239 file subpath doesn’t exist in more than one of them.
242 The location of source includes (default: `sources/includes`).
243 This can be inside of `SRCDIR`, but needn’t be.
244 Multiple include directories can be provided, so long as the same
245 file subpath doesn’t exist in more than one of them.
248 If set to the location of a directory, ⛩📰 书社 will run a two‐stage build.
249 In the first stage, only files in `SRCDIR` which match `FINDDATARULES` (see below) will be built, with files in `DATADIR` serving as includes.
250 In the second stage, the remaining files in `SRCDIR` will be built, with the files built during the first stage, in addition to any files in `INCLUDEDIR`, serving as includes.
251 Files built during the first stage are copied into `DESTDIR` alongside those from the second stage when installing.
253 This functionality is intended for sites where the bulk of the site can be built from a few data files which are expensive to create.
256 The location of the (temporary) build directory (default: `build`).
257 `make clean` will delete this, and it is recommended that it not be
258 used for programs aside from ⛩📰 书社.
261 The location of directory to output files to (default: `public`).
262 `make install` will overwrite files in this directory which
263 correspond to those in `SRCDIR`.
264 It *will not* touch other files, including those generated from files
265 in `SRCDIR` which have since been deleted.
267 Files are first compiled to `$(BUILDDIR)/public` before they are
268 copied to `DESTDIR`, so this folder is relatively quick and
269 inexpensive to re·create.
270 It’s reasonable to simply delete it before every `make install` to
271 ensure stale content is removed.
274 The location of the ⛩📰 书社 `GNUmakefile`.
275 This should be set automatically when calling Make and shouldn’t ever
276 need to be set manually.
277 This variable is used to find the ⛩📰 书社 `lib/` folder, which is
278 expected to be in the same location.
281 A white·space‐separated list of magic files to use (default:
282 `$(THISDIR)/magic/*`).
285 The value of this variable is appended to `MAGIC` by default, to
286 enable additional magic files without overriding the existing ones.
289 Rules to use with `find` when searching for source files.
290 The default ignores files that start with a period or hyphen‐minus,
291 those which end with a cloparen, and those which contain a hash,
292 buck, percent, asterisk, colon, semi, eroteme, bracket, backslash,
294 It is important that these rules not produce any output, as anything
295 printed to `stdout` will be considered a result of the find.
297 - **`EXTRAFINDRULES`:**
298 The value of this variable is appended to `FINDRULES` by default, to
299 enable additional rules without overriding the existing ones.
301 - **`FINDINCLUDERULES`:**
302 Rules to use with `find` when searching for includes (default:
305 - **`EXTRAFINDINCLUDERULES`:**
306 The value of this variable is appended to `FINDINCLUDERULES` by
307 default, to enable additional rules without overriding the existing
311 A list of file extensions which signify “data” files during a two‐stage build using `DATADIR`.
313 - **`FINDDATARULES`:**
314 Rules to use with `find` when searching for data files.
315 By default, these rules are derived from `DATAEXT`.
317 - **`EXTRAFINDDATARULES`:**
318 The value of this variable is appended to `FINDDATARULES` by
319 default, to enable additional rules without overriding the existing
323 A white·space‐separated list of parsers to use (default:
324 `$(THISDIR)/parsers/*.xslt`).
326 - **`EXTRAPARSERS`:**
327 The value of this variable is appended to `PARSERS` by default, to
328 enable additional parsers without overriding the existing ones.
331 A white·space‐separated list of parser dependencies (default:
332 `$(THISDIR)/lib/split.xslt`).
334 - **`EXTRAPARSERLIBS`:**
335 The value of this variable is appended to `PARSERLIBS` by default, to
336 enable additional parser dependencies without overriding the
340 A white·space‐separated list of transforms to use (default:
341 `$(THISDIR)/transforms/*.xslt`).
343 - **`EXTRATRANSFORMS`:**
344 The value of this variable is appended to `TRANSFORMS` by default, to
345 enable additional transforms without overriding the existing ones.
347 - **`TRANSFORMLIBS`:**
348 A white·space‐separated list of transform dependencies (default:
349 `$(THISDIR)/lib/serialize.xslt`).
351 - **`EXTRATRANSFORMLIBS`:**
352 The value of this variable is appended to `TRANSFORMLIBS` by default,
353 to enable additional transform dependencies without overriding the
357 A white·space‐separated list of media types or media type suffixes to
358 consider X·M·L (default: `application/xml text/xml +xml`).
361 A program to run on (unspecial) X·M·L files after they are
362 transformed (default: `xmllint --nonet --nsclean`).
363 This variable can be used for postprocessing.
366 The current version of ⛩📰 书社 (default: derived from the current
367 git tag/branch/commit).
370 The current version of the source files (default: derived from the
371 current git tag/branch/commit).
374 If this variable has a value, informative messages will not be
375 printed (default: empty).
376 Informative messages print to stderr, not stdout, so disabling them
377 usually shouldn’t be necessary.
378 This does not (cannot) disable messages from Make itself, for which
379 the `-s`, `--silent` ∕ `--quiet` Make option is more likely to be
383 If this variable has a value, every recipe instruction will be
384 printed when it runs (default: empty).
385 This is helpful for debugging, but typically too noisy for general
390 Source files may be placed in `SRCDIR` in any manner; the file
391 structure used there will match the output.
392 The type of source files is *not* determined by file extension, but
393 rather by magic number; this means that files **must** begin with
394 something recognizable.
395 Supported magic numbers include :—
397 - `<?xml` for `application/xml` files
398 - `#!js` for `text/javascript` files
399 - `@charset "` for `text/css` files
400 - `#!tsv` for `text/tab-separated-values` files
401 - `%%` for `text/record-jar` files (unregistered; see
402 [[draft-phillips-record-jar-01][]])
404 Text formats with associated X·S·L·T parsers are wrapped in a H·T·M·L
405 `<script>` element whose `@type` gives its media type, and then
406 passed to the parser to process.
407 Source files whose media type does not have an associated X·S·L·T
408 parser are considered “assets” and will not be transformed.
410 **☡ For compatibility with this program, source file·names must not
411 contain Ascii white·space, colons (`:`), semis (`;`), pipes (`|`),
412 bucks (`$`), percents (`%`), hashes (`#`), asterisks (`*`), brackets
413 (`[` or `]`), erotemes (`?`), backslashes (`\`), or control
414 characters, must not begin with a hyphen‐minus (`-`), and must not end
415 with a cloparen (`)`).**
416 The former characters have the potential to conflict with make syntax,
417 a leading hyphen‐minus is confusable for a commandline argument, and a
418 trailing cloparen [activates a bug in G·N·U Make
419 3.81](https://stackoverflow.com/questions/17148468/capturing-filenames-including-parentheses-with-gnu-makes-wildcard-function#comment24825307_17148894).
423 Parsers are used to convert plaintext files into X·M·L trees, as well
424 as convert plaintext formats which are already included inline in
425 existing source X·M·L documents.
426 ⛩📰 书社 comes with some parsers; namely :—
428 - **`parsers/plain.xslt`:**
429 Wraps `text/plain` contents in a `<html:pre>` element.
431 - **`parsers/record-jar.xslt`:**
432 Converts `text/record-jar` contents into a `<html:div>` of
433 `<html:dl>` elements (one for each record).
435 - **`parsers/tsv.xslt`:**
436 Converts `text/tab-separated-values` contents into an `<html:table>`
439 New ⛩📰 书社 parsers which target plaintext formats should have an
440 `<xslt:template>` element with no `@name` or `@mode` and whose
443 - Starts with an appropriately‐name·spaced qualified name for a
444 `<html:script>` element.
446 - Follows this with the string `[@type=`.
448 - Follows this with a quoted string giving a media type supported by
450 Media type parameters are *not* supported.
452 - Follows this with the string `]`.
454 For example, the trivial `text/plain` parser is defined as follows :—
457 <?xml version="1.0"?>
459 xmlns="http://www.w3.org/1999/XSL/Transform"
460 xmlns:html="http://www.w3.org/1999/xhtml"
461 xmlns:书社="urn:fdc:ladys.computer:20231231:Shu1She4"
464 <书社:id>example:text/plain</书社:id>
465 <template match="html:script[@type='text/plain']">
466 <html:pre><value-of select="."/></html:pre>
471 ⛩📰 书社 will scan the provided parsers for this pattern to determine
472 the set of allowed plaintext file types.
473 Multiple such `<xslt:template>` elements may be provided in a single
474 parser, for example if the parser supports multiple media types.
475 Alternatively, you can set the `@书社:supported-media-types` attribute
476 on the root element of the parser to override media type support
479 Even when `@书社:supported-media-types` is set, it is a requirement
480 that each parser transform any `<html:script>` elements with a
481 `@type` which matches their registered types into something else.
482 Otherwise the parser will be stuck in an endless loop.
483 The result tree of applying the transform to the `<html:script>`
484 element will be reparsed (in case any new `<html:script>` elements
485 were added in its subtree), and a `@书社:parsed-by` attribute will be
486 added to each toplevel element in the result.
487 The value of this attribute will be the value of the `<书社:id>`
488 toplevel element in the parser.
490 It is possible for parsers to support zero plaintext types.
491 This is useful when targeting specific dialects of X·M·L; parsers in
492 this sense operate on the same basic principles as transforms
494 The major distinction between X·M·L parsers and transforms is where in
495 the process the transformation happens:
496 Parsers are applied *prior* to embedding (and can be used to generate
497 embeds); transforms are applied *after*.
499 It is **strongly recommended** that auxillary templates in parsers be
500 name·spaced (by `@name` or `@mode`) whenever possible, to avoid
501 conflicts between parsers.
503 ### Attributes added during parsing
505 ⛩📰 书社 will add a few attributes to elements which result from
506 parsing plaintext `<html:script>` elements.
509 - A `@书社:parsed-by` attribute, giving a space‐separated list of
510 parsers which parsed the node.
511 (Generally, this will be a list of one, but it is possible for the
512 result of a parse to be another plaintext node, which may be parsed
513 by a different parser.)
515 - A `@书社:media-type` attribute, giving the identified media type of
518 ## Output Redirection
520 By default, ⛩📰 书社 installs files to the same location in `DESTDIR`
521 as they were placed in their `SRCDIR`.
522 This behaviour can be customized by setting the `@书社:destination`
523 attribute on the root element, whose value can give a different path.
524 This attribute is read after parsing, but before transformation (where
525 it is silently dropped).
529 Documents can be embedded in other documents using a `<书社:link>`
530 element with `@xlink:show="embed"`.
531 The `@xlink:href`s of these elements should have the format
532 `about:shushe?source=<path>`, where `<path>` provides the path to the
533 file within `SRCDIR`.
534 Includes, which do not generate outputs of their own but may still be
535 freely embedded, instead use the format
536 `about:shushe?include=<path>`, where `<path>` provides the path
539 Embeds are replaced with the parsed contents of a file, unless the file
540 is an asset, in which case an `<html:object>` element is produced
541 instead (with the contents of the asset file provided as a base64
543 Embed replacements will be given a `@书社:identifier` attribute whose
544 value will match the `@xlink:href` of the embed.
546 Embedding takes place after parsing but before transformation, so
547 parsers are able to generate their own embeds.
548 ⛩📰 书社 is able to detect the transitive embed dependencies of files
549 and update them accordingly; it will signal an error if the
550 dependencies are recursive.
552 ### Attributes added during expansion
554 ⛩📰 书社 will add a few attributes to toplevel result elements, both
555 in the main document and any embedded documents, during the expansion
556 phase prior to the main transformation.
559 - A `@书社:cksum` attribute giving the `cksum` checksum of the
560 corresponding source file.
562 - A `@书社:mtime` attribute giving the last modified time of the
563 corresponding source file.
565 - A `@书社:identifier` attribute giving the ⛩📰 书社 identifier
566 (i·e, starting with `about:shushe?`) of the corresponding source
569 - For elements in the `html` namespace, an `itemscope` attribute and an
570 `itemtype` attribute with a value of
571 `urn:fdc:ladys.computer:20231231:Shu1She4:document` (for the main
572 document) or `urn:fdc:ladys.computer:20231231:Shu1She4:embed` (for
574 These attributes are used to scope any nested `<html:meta>` elements
575 with `@itemprop` attributes to their containing documents.
579 Transforms are used to convert X·M·L files into their final output,
580 after all necessary parsing and embedding has taken place.
581 ⛩📰 书社 comes with some transforms; namely :—
583 - **`transforms/asset.xslt`:**
584 Converts `<html:object>` elements which correspond to recognized
585 media types into the appropriate H·T·M·L elements, and deletes
586 `<html:style>` elements from the body of the document and moves
588 This conversion happens during the application phase, after the main
591 - **`transforms/metadata.xslt`:**
592 Provides basic `<html:head>` metadata.
593 This metadata is generated from `<html:meta>` elements with one of
594 the following `@itemprop` attributes :—
596 - **`urn:fdc:ladys.computer:20231231:Shu1She4:title`:**
597 Provides the title of the page.
599 ⛩📰 书社 automatically encapsulates H·T·M·L embeds so that their
600 metadata does not propogate up to the embedding document.
601 To undo this behaviour, remove the `@itemscope` and `@itemtype`
602 attributes from the embed during the transformation phase.
604 - **`transforms/serialization.xslt`:**
605 Replaces `<书社:serialize-xml>` elements with the (escaped)
606 serialized X·M·L of their contents.
607 This replacement happens during the application phase, after most
608 other transformations have taken place.
610 If a `@with-namespaces` attribute is provided, any name·space nodes
611 on the toplevel serialized elements whose U·R·I’s correspond to the
612 definitions of the provided prefixes, as defined for the
613 `<书社:serialize-xml>` element, will be declared using name·space
614 attributes on the serialized elements.
615 Otherwise, only name·space nodes which _differ_ from the definitions
616 on the `<书社:serialize-xml>` element will be declared.
617 The string `#default` may be used to represent the default
619 Multiple prefixes may be provided, separated by white·space.
621 When it comes to name·spaces used internally by ⛩📰 书社, the
622 prefix used by ⛩📰 书社 may be declared _in addition to_ the
623 prefix(es) used in the source document(s).
624 It is not possible to selectively only declare one prefix for a
625 name·space to the exclusion of others.
627 `<书社:raw-output>` elements may be used inside of
628 `<书社:serialize-xml>` elements to inject raw output into the
631 The following are recommendations on effective creation of
634 - Make template matchers as specific as possible.
635 It is likely an error if two transforms have templates which match
636 the same element (unless the templates have different priority).
638 - Name·space templates (with `@name` or `@mode`) whenever possible.
640 - Set `@exclude-result-prefixes` on the root `xslt:transform` element
641 to reduce the number of declared name·spaces in the final result.
645 The following params are made available globally in parsers and
652 The ⛩📰 书社 identifier of the source file (a u·r·i beginning with
656 The value of the `SRCREV` variable (if present).
659 The value of the `THISREV` variable (if present).
663 Provided at least one toplevel result element belongs to the H·T·M·L
664 namespace, ⛩📰 书社 will wrap the final output of the transforms in
665 appropriate `<html:html>` and `<html:body>` elements, so it is not
666 necessary for transforms to do this explicitly.
667 If a toplevel result element _is_ a `<html:html>` and `<html:body>`
668 element, it will be merged with the one that ⛩📰 书社 creates.
669 Consequently, wrapping the result in a `<html:body>` element can be
670 used to enable wrapping for non‐H·T·M·L content, when desired.
672 As a part of this process, after performing the initial transform
673 ⛩📰 书社 will match in the following modes to fill in areas of the
677 The result of matching in this mode is prepended into the
678 `<html:body>` of the output (before the transformation result).
681 The result of matching in this mode is appended into the
682 `<html:body>` of the output (after the transformation result).
685 The result of matching in this mode is inserted into the
686 `<html:head>` of the output.
688 The document being matched will contain the full transform result
689 prior to wrapping as well as an `<书社:id>` element for each
691 The latter elements can be matched to enable transforms to provide
692 content _without_ matching any elements in the result; for example,
693 the following transform adds a link to a stylesheet to the
694 `<html:head>` of every page :—
697 <?xml version="1.0"?>
699 xmlns="http://www.w3.org/1999/XSL/Transform"
700 xmlns:html="http://www.w3.org/1999/xhtml"
701 xmlns:xslt="http://www.w3.org/1999/XSL/Transform"
702 xmlns:书社="urn:fdc:ladys.computer:20231231:Shu1She4"
703 exclude-result-prefixes="书社"
706 <书社:id>example:add-stylesheet-links.xslt</书社:id>
707 <template match="书社:id[string(.)='example:add-stylesheet-links.xslt']" mode="书社:metadata">
708 <html:link rel="stylesheet" type="text/css" href="/style.css"/>
713 Output wrapping can be entirely disabled by adding a
714 `@书社:disable-output-wrapping` attribute to the top‐level element in
716 It will not be performed on outputs whose root elements are
717 `<书社:archive>`, `<书社:base64-binary>`, or `<书社:raw-text>`
718 (described below), or on result trees which do not contain a toplevel
719 element in the H·T·M·L namespace.
721 ## Applying Attributes
723 The `<书社:apply-attributes>` element will apply any attributes on the
724 element to the element(s) it wraps.
725 It is especially useful in combination with embeds.
727 The `<书社:apply-attributes-to-root>` element will apply any attributes
728 on the element to the root node of the final transformation result.
729 It is especially useful in combination with output wrapping.
731 In both cases, attributes from various sources are combined with
732 white·space between them.
733 Attribute application takes place after all ordinary transforms have
736 Both elements ignore attributes in the `xml:` name·space, except for
737 `@xml:lang`, which ignores all but the first definition (including
738 any already present on the root element).
739 On H·T·M·L and S·V·G elements, `@lang` has the same behaviour as
742 ## Other Kinds of Output
744 There are a few special elements in the `书社:` name·space which, if
745 they appear as the toplevel element in a transformation result, cause
746 ⛩📰 书社 to produce something other than an X·M·L file.
749 - **`<书社:archive>`:**
750 Each child element with a `@书社:archived-as` attribute will be
751 archived as a separate file in a resulting tarball (this attribute
752 gives the file name).
753 These elements will be processed the same as the root elements of any
754 other file (e·g, they will be wrapped; they can themselves specify
755 non X·M·L output types, ⁊·c).
756 Other child elements will be ignored.
758 If the `<书社:archive>` element is given an `@书社:expanded`
759 attribute, rather than producing a tarball ⛩📰 书社 will output
760 the directory which expanding the tarball would produce.
761 This mechanism can be used to generate multiple files from a single
762 source, provided all of the files are contained with·in the same
765 - **`<书社:base64-binary>`:**
766 The text nodes in the transformation result will, after removing all
767 Ascii whitespace, be treated as a Base·64 string, which is then
770 - **`<书社:raw-text>`:**
771 A plaintext (U·T·F‐8) file will be produced from the text nodes in
772 the transformation result.
776 This repository conforms to [REUSE][].
778 Most source files are licensed under the terms of the <cite>Mozilla
779 Public License, version 2.0</cite>.
781 [REUSE]: <https://reuse.software/spec/>
782 [draft-phillips-record-jar-01]: <https://datatracker.ietf.org/doc/html/draft-phillips-record-jar-01>
783 [rdar-92753335]: <https://github.com/apple-oss-distributions/patch_cmds/blob/5084833f90df1b0e0924ea56f94c0199b3b8bbc6/diff/diffreg.c#L1800-L1808>