]> Lady’s Gitweb - Shushe/blob - README.markdown
Support pagination
[Shushe] / README.markdown
1 <!--
2 SPDX-FileCopyrightText: 2024 Lady <https://www.ladys.computer/about/#lady>
3 SPDX-License-Identifier: CC0-1.0
4 -->
5 # ⛩️📰 书社
6
7 <b>A make·file for X·M·L.</b>
8
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.
13
14 It makes things easier by :⁠—
15
16 - Automatically identifying source files and characterizing them by
17 type (X·M·L, text, or asset).
18
19 - Parsing supported text types into X·M·L trees.
20
21 - Enabling easy inclusion of source files within each other.
22
23 It aims to do this with zero dependencies beyond the programs already
24 installed on your computer†.
25
26 † The only non‐Posix programs‡ required (other than G·N·U Make itself,
27 and optionally Git) are those provided by `libxml2` and `libxslt`.
28 On most operating systems, these libraries come pre·installed, but on
29 Linux machines the commandline utilities are often packaged
30 separately (as **`libxml2-utils`** and **`xsltproc`**), which may
31 still need to be installed.
32 Additionally, not all Linux distributions bundle all necessary Posix
33 programs; on Debian (for example) you may need to separately install
34 **`sharutils`** for `uudecode` and `uuencode` and **`pax`** for
35 archiving.
36
37 ‡ This make·file also currently depends on non‐Posix `stat` but
38 attempts to handle both the G·N·U and B·S·D variants.
39 It expects `xargs` to accept a `-0` option, which, while widely
40 supported, is not a part of the Posix standard.
41
42 **Note:**
43 ⛩️📰 书社 requires functionality present in G·N·U Make 3.81 or later,
44 and will not work in previous versions, or with other implementations
45 of Make.
46
47 ## Nomenclature
48
49 <i lang="cmn-Hans">书社</i> is a Chinese word meaning “publishing
50 house”.
51
52 The first character, <i lang="cmn-Hans">书</i>, is the simplified form
53 of “document”.
54
55 The second character, <i lang="cmn-Hans">社</i>, contemporarily means
56 “association”, but historically referred to the god of the soil and
57 related altars or festivities.
58 In Japanese, it is an alternate spelling for <i lang="ja">やしろ</i>,
59 the word for “Shinto shrine”.
60
61 The name <i lang="cmn-Hans">书社</i> was chosen to play on this pun, as
62 it is intended as a publishing program for webshrines.
63
64 In Ascii environments, ⛩️📰 书社 should be written `Shushe`, following
65 the pinyin transliteration.
66
67 ## Basic Usage
68
69 Place source files in `sources/` and run `make install` to compile
70 the result to `public/`.
71 Compilation involves the following steps :⁠—
72
73 1. ⛩️📰 书社 compiles all of the magic files in `magic/` into a single
74 file, `build/magic.mgc`.
75
76 2. ⛩️📰 书社 processes all of the parsers in `parsers/` and determines
77 the list of supported plaintext types.
78
79 3. ⛩️📰 书社 identifies all of the source files and includes and uses
80 `build/magic.mgc` to classify them by media type.
81
82 4. ⛩️📰 书社 parses all plaintext and X·M·L source files and includes
83 and then builds a dependency tree between them.
84
85 5. ⛩️📰 书社 uses the dependency tree to establish prerequisites for
86 each output file.
87
88 6. ⛩️📰 书社 compiles each output file to `build/result`.
89
90 7. ⛩️📰 书社 copies most output files from `build/result` to
91 `build/public`, but it does some additional processing instead on
92 those which indicate a non‐X·M·L desired final output form.
93
94 8. ⛩️📰 书社 copies the final resulting files to `public`.
95
96 You can use `make list` to list each identified source file or include
97 alongside its computed type and dependencies.
98 As this is a Make‐based program, steps will only be run if the
99 corresponding buildfile or output file is older than its
100 prerequisites.
101
102 ## Name·spaces
103
104 The ⛩️📰 书社 name·space is `urn:fdc:ladys.computer:20231231:Shu1She4`.
105
106 This document uses a few name·space prefixes, with the following
107 meanings :⁠—
108
109 | Prefix | Expansion |
110 | ---------: | :-------------------------------------------- |
111 | `catalog:` | `urn:oasis:names:tc:entity:xmlns:xml:catalog` |
112 | `exsl:` | `http://exslt.org/common` |
113 | `exslstr:` | `http://exslt.org/strings` |
114 | `html:` | `http://www.w3.org/1999/xhtml` |
115 | `svg:` | `http://www.w3.org/2000/svg` |
116 | `xlink:` | `http://www.w3.org/1999/xlink` |
117 | `xslt:` | `http://www.w3.org/1999/XSL/Transform` |
118 | `书社:` | `urn:fdc:ladys.computer:20231231:Shu1She4` |
119
120 ## Setup and Configuration
121
122 ⛩️📰 书社 depends on the following programs to run.
123 In every case, you may supply your own implementation by overriding the
124 corresponding (allcaps) variable (e·g, set `MKDIR` to supply your own
125 `mkdir` implementation).
126
127 - `awk`
128 - `cat`
129 - `cksum`
130 - `cp`
131 - `date`
132 - `echo`
133 - `file`
134 - `find`
135 - `git` (optional; set `GIT=` to disable)
136 - `grep`
137 - `ln`
138 - `ls`
139 - `mkdir`
140 - `mv`
141 - `od`
142 - `pax` (only when generating archives)
143 - `printf`
144 - `rm`
145 - `sed`
146 - `sleep`
147 - `stat` (BSD *or* GNU)
148 - `test`
149 - `touch`
150 - `tr`
151 - `uuencode`
152 - `uudecode`
153 - `xargs` (requires support for `-0`)
154 - `xmlcatalog` (provided by `libxml2`)
155 - `xmllint` (provided by `libxml2`)
156 - `xsltproc` (provided by `libxslt`)
157
158 The following additional variables can be used to control the behaviour
159 of ⛩️📰 书社 :⁠—
160
161 - **`SRCDIR`:**
162 The location of the source files (default: `sources`).
163 Multiple source directories can be provided, so long as the same
164 file subpath doesn’t exist in more than one of them.
165
166 - **`INCLUDEDIR`:**
167 The location of source includes (default: `sources/includes`).
168 This can be inside of `SRCDIR`, but needn’t be.
169 Multiple include directories can be provided, so long as the same
170 file subpath doesn’t exist in more than one of them.
171
172 - **`BUILDDIR`:**
173 The location of the (temporary) build directory (default: `build`).
174 `make clean` will delete this, and it is recommended that it not be
175 used for programs aside from ⛩️📰 书社.
176
177 - **`DESTDIR`:**
178 The location of directory to output files to (default: `public`).
179 `make install` will overwrite files in this directory which
180 correspond to those in `SRCDIR`.
181 It *will not* touch other files, including those generated from files
182 in `SRCDIR` which have since been deleted.
183
184 Files are first compiled to `$(BUILDDIR)/public` before they are
185 copied to `DESTDIR`, so this folder is relatively quick and
186 inexpensive to re·create.
187 It’s reasonable to simply delete it before every `make install` to
188 ensure stale content is removed.
189
190 - **`THISDIR`:**
191 The location of the ⛩️📰 书社 `GNUmakefile`.
192 This should be set automatically when calling Make and shouldn’t ever
193 need to be set manually.
194 This variable is used to find the ⛩️📰 书社 `lib/` folder, which is
195 expected to be in the same location.
196
197 - **`MAGIC`:**
198 A white·space‐separated list of magic files to use (default:
199 `$(THISDIR)/magic/*`).
200
201 - **`EXTRAMAGIC`:**
202 The value of this variable is appended to `MAGIC` by default, to
203 enable additional magic files without overriding the existing ones.
204
205 - **`FINDRULES`:**
206 Rules to use with `find` when searching for source files.
207 The default ignores files that start with a period or hyphen‐minus,
208 those which end with a cloparen, and those which contain a hash,
209 buck, percent, asterisk, colon, semi, eroteme, bracket, backslash,
210 or pipe.
211
212 - **`EXTRAFINDRULES`:**
213 The value of this variable is appended to `FINDRULES` by default, to
214 enable additional rules without overriding the existing ones.
215
216 - **`FINDINCLUDERULES`:**
217 Rules to use with `find` when searching for includes (default:
218 `$(FINDRULES)`).
219
220 - **`EXTRAFINDINCLUDERULES`:**
221 The value of this variable is appended to `FINDINCLUDERULES` by
222 default, to enable additional rules without overriding the existing
223 ones.
224
225 - **`PARSERS`:**
226 A white·space‐separated list of parsers to use (default:
227 `$(THISDIR)/parsers/*.xslt`).
228
229 - **`EXTRAPARSERS`:**
230 The value of this variable is appended to `PARSERS` by default, to
231 enable additional parsers without overriding the existing ones.
232
233 - **`TRANSFORMS`:**
234 A white·space‐separated list of transforms to use (default:
235 `$(THISDIR)/transforms/*.xslt`).
236
237 - **`EXTRATRANSFORMS`:**
238 The value of this variable is appended to `TRANSFORMS` by default, to
239 enable additional transforms without overriding the existing ones.
240
241 - **`XMLTYPES`:**
242 A white·space‐separated list of media types to consider X·M·L
243 (default: `application/xml text/xml`).
244
245 - **`THISREV`:**
246 The current version of ⛩️📰 书社 (default: derived from the current
247 git tag/branch/commit).
248
249 - **`SRCREV`:**
250 The current version of the source files (default: derived from the
251 current git tag/branch/commit).
252
253 - **`VERBOSE`:**
254 If this variable has a value, every recipe instruction will be
255 printed when it runs (default: empty).
256 This is helpful for debugging, but typically too noisy for general
257 usage.
258
259 ## Source Files
260
261 Source files may be placed in `SRCDIR` in any manner; the file
262 structure used there will match the output.
263 The type of source files is *not* determined by file extension, but
264 rather by magic number; this means that files **must** begin with
265 something recognizable.
266 Supported magic numbers include :⁠—
267
268 - `<?xml` for `application/xml` files
269 - `#!js` for `text/javascript` files
270 - `@charset "` for `text/css` files
271 - `#!tsv` for `text/tab-separated-values` files
272 - `%%` for `text/record-jar` files (unregistered; see
273 [[draft-phillips-record-jar-01][]])
274
275 Text formats with associated X·S·L·T parsers are wrapped in a H·T·M·L
276 `<script>` element whose `@type` gives its media type, and then
277 passed to the parser to process.
278 Source files whose media type does not have an associated X·S·L·T
279 parser are considered “assets” and will not be transformed.
280
281 **☡ For compatibility with this program, source file·names must not
282 contain Ascii white·space, colons (`:`), semis (`;`), pipes (`|`),
283 bucks (`$`), percents (`%`), hashes (`#`), asterisks (`*`), brackets
284 (`[` or `]`), erotemes (`?`), backslashes (`\`), or control
285 characters, must not begin with a hyphen‐minus (`-`), must not end
286 with a cloparen (`)`), and must not contain quoted braces (`"{` or
287 `}"`).**
288 The former characters have the potential to conflict with make syntax,
289 a leading hyphen‐minus is confusable for a command‐line argument, a
290 trailing cloparen [activates a bug in G·N·U Make
291 3.81](https://stackoverflow.com/questions/17148468/capturing-filenames-including-parentheses-with-gnu-makes-wildcard-function#comment24825307_17148894),
292 and quoted braces are used internally by the program.
293
294 ## Parsers
295
296 Parsers are used to convert plaintext files into X·M·L trees, as well
297 as convert plaintext formats which are already included inline in
298 existing source X·M·L documents.
299 ⛩️📰 书社 comes with some parsers; namely :⁠—
300
301 - **`parsers/plain.xslt`:**
302 Wraps `text/plain` contents in a `<html:pre>` element.
303
304 - **`parsers/record-jar.xslt`:**
305 Converts `text/record-jar` contents into a `<html:div>` of
306 `<html:dl>` elements (one for each record).
307
308 - **`parsers/tsv.xslt`:**
309 Converts `text/tab-separated-values` contents into an `<html:table>`
310 element.
311
312 New ⛩️📰 书社 parsers which target plaintext formats should have an
313 `<xslt:template>` element with no `@name` or `@mode` and whose
314 `@match` attribute…
315
316 - Starts with an appropriately‐name·spaced qualified name for a
317 `<html:script>` element.
318
319 - Follows this with the string `[@type=`.
320
321 - Follows this with a quoted string giving a media type supported by
322 the parser.
323 Media type parameters are *not* supported.
324
325 - Follows this with the string `]`.
326
327 For example, the trivial `text/plain` parser is defined as follows :⁠—
328
329 ```xml
330 <?xml version="1.0"?>
331 <transform
332 xmlns="http://www.w3.org/1999/XSL/Transform"
333 xmlns:html="http://www.w3.org/1999/xhtml"
334 xmlns:书社="urn:fdc:ladys.computer:20231231:Shu1She4"
335 version="1.0"
336 >
337 <书社:id>example:text/plain</书社:id>
338 <template match="html:script[@type='text/plain']">
339 <html:pre><value-of select="."/></html:pre>
340 </template>
341 </transform>
342 ```
343
344 ⛩️📰 书社 will scan the provided parsers for this pattern to determine
345 the set of allowed plaintext file types.
346 Multiple such `<xslt:template>` elements may be provided in a single
347 parser, for example if the parser supports multiple media types.
348 Alternatively, you can set the `@书社:supported-media-types` attribute
349 on the root element of the parser to override media type support
350 detection.
351
352 Even when `@书社:supported-media-types` is set, it is a requirement
353 that each parser transform any `<html:script>` elements with a
354 `@type` which matches their registered types into something else.
355 Otherwise the parser will be stuck in an endless loop.
356 The result tree of applying the transform to the `<html:script>`
357 element will be reparsed (in case any new `<html:script>` elements
358 were added in its subtree), and a `@书社:parsed-by` attribute will be
359 added to each toplevel element in the result.
360 The value of this attribute will be the value of the `<书社:id>`
361 toplevel element in the parser.
362
363 It is possible for parsers to support zero plaintext types.
364 This is useful when targeting specific dialects of X·M·L; parsers in
365 this sense operate on the same basic principles as transforms
366 (described below).
367 The major distinction between X·M·L parsers and transforms is where in
368 the process the transformation happens:
369 Parsers are applied *prior* to embedding (and can be used to generate
370 embeds); transforms are applied *after*.
371
372 It is **strongly recommended** that auxillary templates in parsers be
373 name·spaced (by `@name` or `@mode`) whenever possible, to avoid
374 conflicts between parsers.
375
376 ### Attributes added during parsing
377
378 ⛩️📰 书社 will add a few attributes to the output of the parsing step,
379 namely :⁠—
380
381 - A `@书社:cksum` attribute on toplevel result elements, giving the
382 `cksum` checksum of the corresponding source file.
383
384 - For the elements which result from parsing plaintext `<html:script>`
385 elements :⁠—
386
387 - A `@书社:parsed-by` attribute, giving a space‐separated list of
388 parsers which parsed the node.
389 (Generally, this will be a list of one, but it is possible for the
390 result of a parse to be another plaintext node, which may be
391 parsed by a different parser.)
392
393 - A `@书社:media-type` attribute, giving the identified media type of
394 the plaintext node.
395
396 ## Embedding
397
398 Documents can be embedded in other documents using a `<书社:link>`
399 element with `@xlink:show="embed"`.
400 The `@xlink:href`s of these elements should have the format
401 `about:shushe?source=<path>`, where `<path>` provides the path to the
402 file within `SRCDIR`.
403 Includes, which do not generate outputs of their own but may still be
404 freely embedded, instead use the format
405 `about:shushe?include=<path>`, where `<path>` provides the path
406 within `INCLUDEDIR`.
407
408 Embeds are replaced with the parsed contents of a file, unless the file
409 is an asset, in which case an `<html:object>` element is produced
410 instead (with the contents of the asset file provided as a base64
411 `data:` u·r·i).
412 Embed replacements will be given a `@书社:identifier` attribute whose
413 value will match the `@xlink:href` of the embed.
414
415 Embedding takes place after parsing but before transformation, so
416 parsers are able to generate their own embeds.
417 ⛩️📰 书社 is able to detect the transitive embed dependencies of files
418 and update them accordingly; it will signal an error if the
419 dependencies are recursive.
420
421 ## Output Redirection
422
423 By default, ⛩️📰 书社 installs files to the same location in `DESTDIR`
424 as they were placed in their `SRCDIR`.
425 This behaviour can be customized by setting the `@书社:destination`
426 attribute on the root element, whose value can give a different path.
427 This attribute is read after parsing, but before transformation (where
428 it is silently dropped).
429
430 ## Transforms
431
432 Transforms are used to convert X·M·L files into their final output,
433 after all necessary parsing and embedding has taken place.
434 ⛩️📰 书社 comes with some transforms; namely :⁠—
435
436 - **`transforms/asset.xslt`:**
437 Converts `<html:object>` elements which correspond to recognized
438 media types into the appropriate H·T·M·L elements, and deletes
439 `<html:style>` elements from the body of the document and moves
440 them to the head.
441
442 - **`transforms/metadata.xslt`:**
443 Provides basic `<html:head>` metadata.
444 This metadata is generated from `<html:meta>` elements with one of
445 the following `@itemprop` attributes :⁠—
446
447 - **`urn:fdc:ladys.computer:20231231:Shu1She4:title`:**
448 Provides the title of the page.
449
450 ⛩️📰 书社 automatically encapsulates H·T·M·L embeds so that their
451 metadata does not propogate up to the embedding document.
452 To undo this behaviour, remove the `@itemscope` and `@itemtype`
453 attributes from the embed during the transformation phase.
454
455 - **`transforms/serialization.xslt`:**
456 Replaces `<书社:serialize-xml>` elements with the (escaped)
457 serialized X·M·L of their contents.
458 This replacement happens during the application phase, after most
459 other transformations have taken place.
460
461 If a `@with-namespaces` attribute is provided, any name·space nodes
462 on the toplevel serialized elements whose U·R·I’s correspond to the
463 definitions of the provided prefixes, as defined for the
464 `<书社:serialize-xml>` element, will be declared using name·space
465 attributes on the serialized elements.
466 Otherwise, only name·space nodes which _differ_ from the definitions
467 on the `<书社:serialize-xml>` element will be declared.
468 The string `#default` may be used to represent the default
469 name·space.
470 Multiple prefixes may be provided, separated by white·space.
471
472 When it comes to name·spaces used internally by ⛩️📰 书社, the
473 prefix used by ⛩️📰 书社 may be declared _in addition to_ the
474 prefix(es) used in the source document(s).
475 It is not possible to selectively only declare one prefix for a
476 name·space to the exclusion of others.
477
478 `<书社:raw-output>` elements may be used inside of
479 `<书社:serialize-xml>` elements to inject raw output into the
480 serialized X·M·L.
481
482 The following are recommendations on effective creation of
483 transforms :⁠—
484
485 - Make template matchers as specific as possible.
486 It is likely an error if two transforms have templates which match
487 the same element (unless the templates have different priority).
488
489 - Name·space templates (with `@name` or `@mode`) whenever possible.
490
491 - Set `@exclude-result-prefixes` on the root `xslt:transform` element
492 to reduce the number of declared name·spaces in the final result.
493
494 ## Global Params
495
496 The following params are made available globally in parsers and
497 transforms :⁠—
498
499 - **`BUILDTIME`:**
500 The current time.
501
502 - **`CKSUM`:**
503 The checksum of the source file (⅌ `cksum`).
504
505 - **`IDENTIFIER`:**
506 The ⛩️📰 书社 identifier of the source file (a u·r·i beginning with
507 `about:shushe`).
508
509 - **`SRCREV`:**
510 The value of the `SRCREV` variable (if present).
511
512 - **`SRCTIME`:**
513 The time at which the source file was last modified.
514
515 - **`THISREV`:**
516 The value of the `THISREV` variable (if present).
517
518 The following params are only available in transforms :⁠—
519
520 - **`CATALOG`:**
521 The path of the catalog file (within `BUILDDIR`).
522
523 - **`PATH`:**
524 The path of the output file (within `DESTDIR`).
525
526 ## Output Wrapping
527
528 ⛩️📰 书社 will wrap the final output of the transforms in appropriate
529 `<html:html>` and `<html:body>` elements, so it is not necessary for
530 transforms to do this explicitly.
531 After performing the initial transform, ⛩️📰 书社 will match the root
532 node of the result in the following modes to fill in areas of the
533 wrapper :⁠—
534
535 - **`书社:header`:**
536 The result of matching in this mode is prepended into the
537 `<html:body>` of the output (before the transformation result).
538
539 - **`书社:footer`:**
540 The result of matching in this mode is appended into the
541 `<html:body>` of the output (after the transformation result).
542
543 - **`书社:metadata`:**
544 The result of matching in this mode is inserted into the
545 `<html:head>` of the output.
546
547 In addition to being called with the transform result, each of these
548 modes will additionally be called with a `<xslt:include>` element
549 corresponding to each transform.
550 If a transform has a `<书社:id>` top‐level element whose value is an
551 i·r·i, its `<xslt:include>` element will have a corresponding
552 `@书社:id` attribute.
553 This mechanism can be used to allow transforms to insert content
554 without matching any elements in the result; for example, the
555 following transform adds a link to a stylesheet to the `<html:head>`
556 of every page :⁠—
557
558 ```xml
559 <?xml version="1.0"?>
560 <transform
561 xmlns="http://www.w3.org/1999/XSL/Transform"
562 xmlns:html="http://www.w3.org/1999/xhtml"
563 xmlns:xslt="http://www.w3.org/1999/XSL/Transform"
564 xmlns:书社="urn:fdc:ladys.computer:20231231:Shu1She4"
565 exclude-result-prefixes="书社"
566 version="1.0"
567 >
568 <书社:id>example:add-stylesheet-links.xslt</书社:id>
569 <template match="xslt:include[@书社:id='example:add-stylesheet-links.xslt']" mode="书社:metadata">
570 <html:link rel="stylesheet" type="text/css" href="/style.css"/>
571 </template>
572 </transform>
573 ```
574
575 Output wrapping can be entirely disabled by adding a
576 `@书社:disable-output-wrapping` attribute to the top‐level element in
577 the result tree.
578 It will not be performed on outputs whose root elements are
579 `<书社:archive>`, `<书社:base64-binary>`, or `<书社:raw-text>`
580 (described below).
581
582 ## Applying Attributes
583
584 The `<书社:apply-attributes>` element will apply any attributes on the
585 element to the element(s) it wraps.
586 It is especially useful in combination with embeds.
587
588 The `<书社:apply-attributes-to-root>` element will apply any attributes
589 on the element to the root node of the final transformation result.
590 It is especially useful in combination with output wrapping.
591
592 In both cases, attributes from various sources are combined with
593 white·space between them.
594 Attribute application takes place after all ordinary transforms have
595 completed.
596
597 Both elements ignore attributes in the `xml:` name·space, except for
598 `@xml:lang`, which ignores all but the first definition (including
599 any already present on the root element).
600 On H·T·M·L and S·V·G elements, `@lang` has the same behaviour as
601 `@xml:lang`.
602
603 ## Other Kinds of Output
604
605 There are a few special elements in the `书社:` name·space which, if
606 they appear as the toplevel element in a transformation result, cause
607 ⛩️📰 书社 to produce something other than an X·M·L file.
608 They are :⁠—
609
610 - **`<书社:archive>`:**
611 Each child element with a `@书社:archived-as` attribute will be
612 archived as a separate file in a resulting tarball (this attribute
613 gives the file name).
614 These elements will be processed the same as the root elements of any
615 other file (e·g, they will be wrapped; they can themselves specify
616 non X·M·L output types, ⁊·c).
617 Other child elements will be ignored.
618
619 - **`<书社:base64-binary>`:**
620 The text nodes in the transformation result will, after removing all
621 Ascii whitespace, be treated as a Base·64 string, which is then
622 decoded.
623
624 - **`<书社:raw-text>`:**
625 A plaintext (U·T·F‐8) file will be produced from the text nodes in
626 the transformation result.
627
628 ## Pagination
629
630 It is possible to have a single source file produce multiple output
631 files via `<书社:page>` elements, whose `@name` gives the name of the
632 page.
633 If a parsed document has a `@书社:destination` which contains `%s`,
634 the `%s` will be replaced with the `@name` for each `<书社:page>` (and
635 removed for the main output).
636 Otherwise, the `@name` is inserted before the first period of the
637 filename (or at the end of the filename for those with no period).
638 If `<书社:page>`s do not have a `@name`, they are numbered
639 sequentially.
640 The destination of pages must be in the same directory as their parent.
641
642 Pagination essentially forms a limited convenience for the more
643 sophisticated technique of creating an archive with ⛩️📰 书社 and
644 then unarchiving it.
645 Pages are, from Make’s point of view, untracked side·effects of
646 installing the main output, meaning they cannot be targeted directly
647 and will not appear in `make list` or `make listout`.
648 They are intended solely for the like of indices and feeds, for which
649 convenience and necessity outweigh their flaws.
650
651 ## License
652
653 This repository conforms to [REUSE][].
654
655 Most source files are licensed under the terms of the <cite>Mozilla
656 Public License, version 2.0</cite>.
657
658 [REUSE]: <https://reuse.software/spec/>
659 [draft-phillips-record-jar-01]: <https://datatracker.ietf.org/doc/html/draft-phillips-record-jar-01>
This page took 0.077965 seconds and 5 git commands to generate.