X-Git-Url: https://git.ladys.computer/Shushe/blobdiff_plain/4a0e5671fe44e12a563c4b8403b87db66566f005..d94cfdc987aba3983f4945d59b02cbb062573432:/README.markdown?ds=inline diff --git a/README.markdown b/README.markdown index 13cb1d6..cae7ac1 100644 --- a/README.markdown +++ b/README.markdown @@ -124,9 +124,21 @@ The following additional variables can be used to control the behaviour - **`BUILDDIR`:** The location of the (temporary) build directory (default: `build`). + `make clean` will delete this, and it is recommended that it not be + used for programs aside from ⛩️📰 书社. - **`DESTDIR`:** The location of directory to output files to (default: `public`). + `make install` will overwrite files in this directory which + correspond to those in `SRCDIR`. + It *will not* touch other files, including those generated from files + in `SRCDIR` which have since been deleted. + + Files are first compiled to `$(BUILDDIR)/public` before they are + copied to `DESTDIR`, so this folder is relatively quick and + inexpensive to re·create. + It’s reasonable to simply delete it before every `make install` to + ensure stale content is removed. - **`THISDIR`:** The location of the ⛩️📰 书社 `GNUmakefile`. @@ -140,12 +152,20 @@ The following additional variables can be used to control the behaviour - **`FINDOPTS`:** Options to pass to `find` when searching for source files (default: - `-LE`). + `-PE`). - **`FINDRULES`:** Rules to use with `find` when searching for source files (default: `-flags -nohidden -and -not -name '.*'`). +- **`FINDINCLUDEOPTS`:** + Options to pass to `find` when searching for includes (default: + `$(FINDOPTS)`). + +- **`FINDINCLUDERULES`:** + Rules to use with `find` when searching for includes (default: + `$(FINDRULES)`). + - **`PARSERS`:** A white·space‐separated list of parsers to use (default: `$(THISDIR)/parsers/*.xslt`). @@ -186,18 +206,11 @@ Text formats with associated X·S·L·T parsers are wrapped in a H·T·M·L Source files whose media type does not have an associated X·S·L·T parser are considered “assets” and will not be transformed. -For compatibility with this program, source filenames should conform to - the following rules :⁠— - -- They should not start with a hyphen‐minus. - This is to prevent confusion between filenames and options on the - commandline. - -- They should not contain spaces, colons, percent signs, backticks, - question marks, hashes, or backslashes. - -In general, filenames should be such that they do not require - percent‐encoding in the path component of an i·r·i. +For compatibility with this program, source filenames should not + contain Ascii whitespace or any of the following Ascii characters: + ``!"#$%&()-:<>?\^`{|}``. +These characters are either invalid in u·r·i’s or conflict with aspects + of the Make or commandline syntax. ## Parsers @@ -207,14 +220,20 @@ Parsers are used to convert plaintext files into X·M·L trees, as well ⛩️📰 书社 comes with some parsers; namely :⁠— - **`parsers/plain.xslt`:** - Wraps `text/plain` contents in a `` element. + Wraps `text/plain` contents in a `` element. + +- **`parsers/record-jar.xslt`:** + Converts `text/record-jar` contents into a + `` of `` elements (one for + each record). - **`parsers/tsv.xslt`:** - Converts `text/tab-separated-values` contents into an `` - element. + Converts `text/tab-separated-values` contents into an + `` element. -New ⛩️📰 书社 parsers should have a `` element with no - `@name` or `@mode` and whose `@match` attribute… +New ⛩️📰 书社 parsers which target plaintext formats should have an + `` element with no `@name` or `@mode` and whose + `@match` attribute… - Starts with an appropriately‐namespaced qualified name for a `` element. @@ -250,9 +269,16 @@ Alternatively, you can set the `@书社:supported-media-types` attribute on the root element of the parser to override media type support detection. -It is **strongly recommended** that all templates in parsers other than - those described above be namespaced (by `@name` or `@mode`), to avoid - conflicts between templates in multiple parsers. +Parsers can also target specific dialects of X·M·L, in which case they + operate on the same basic principles as transforms (described below). +The major distinction between X·M·L parsers and transforms is where in + the process the transformation happens: +Parsers are applied *prior* to embedding (and can be used to generate + embeds); transforms are applied *after*. + +It is **strongly recommended** that auxillary templates in parsers be + namespaced (by `@name` or `@mode`) whenever possible, to avoid + conflicts between parsers. ## Embedding @@ -283,6 +309,14 @@ Transforms are used to convert X·M·L files into their final output, after all necessary parsing and embedding has taken place. ⛩️📰 书社 comes with some transforms; namely :⁠— +- **`transforms/attributes.xslt`:** + Applies transforms to the children of any `<书社:apply-attributes>` + elements, and then applies the attributes of the + `<书社:apply-attributes>` to each result child, replacing the + element with the result. + This is useful in combination with image embeds to apply alt‐text to + the resulting ``. + - **`transforms/asset.xslt`:** Converts `` elements which correspond to recognized media types into the appropriate H·T·M·L elements, and deletes @@ -291,7 +325,7 @@ Transforms are used to convert X·M·L files into their final output, - **`transforms/metadata.xslt`:** Provides basic `` metadata. - This metadata is generated from `` elements with one o. + This metadata is generated from `` elements with one of the following `@itemprop` attributes :⁠— - **`urn:fdc:ladys.computer:20231231:Shu1She4:title`:**