Fix X·M·L 1.1 handling to be portable

[Shushe] / README.markdown

diff --git a/README.markdown b/README.markdown
index 643a4d8da36c3e470ddc197cc5f008b9e1b76404..5457ce763994785c2029d58162d4b68e25ebf1a7 100644 (file)
--- a/README.markdown
+++ b/README.markdown
@@ -75,7 +75,7 @@ Compilation involves the following steps :⁠—
 
 6. ⛩️📰 书社 compiles each output file to `build/result`.
 
-7. ⛩️📰 书社 symlinks most output files from `build/result` to
+7. ⛩️📰 书社 copies most output files from `build/result` to
      `build/public`, but it does some additional processing instead on
      those which indicate a non‐X·M·L desired final output form.
 
@@ -121,6 +121,7 @@ In every case, you may supply your own implementation by overriding the
 - `file`
 - `find`
 - `git` (optional; set `GIT=` to disable)
+- `grep`
 - `ln`
 - `mkdir` (requires support for `-p`)
 - `mv`
@@ -130,7 +131,7 @@ In every case, you may supply your own implementation by overriding the
 - `rm`
 - `sed`
 - `sleep`
-- `stat`
+- `stat` (BSD *or* GNU)
 - `test`
 - `touch`
 - `tr` (requires support for `-d`)
@@ -459,6 +460,10 @@ Transforms are used to convert X·M·L files into their final output,
   It is not possible to selectively only declare one prefix for a
     name·space to the exclusion of others.
 
+  `<书社:raw-output>` elements may be used inside of
+    `<书社:serialize-xml>` elements to inject raw output into the
+    serialized X·M·L.
+
 The following are recommendations on effective creation of
   transforms :⁠—