Remove dependency on echo

[Shushe] / README.markdown

diff --git a/README.markdown b/README.markdown
index bf353e0f0266f768cac8d2c48b8de8b0426e451c..d459604c1709aaf9632bf19b1600e85521461d1f 100644 (file)
--- a/README.markdown
+++ b/README.markdown
@@ -122,14 +122,6 @@ These are Posix utilities, but not included in the Linux Standard Base
 The G·N·U [Sharutils](https://www.gnu.org/software/sharutils/) package
   can be installed to access them.
 
 The G·N·U [Sharutils](https://www.gnu.org/software/sharutils/) package
   can be installed to access them.
 

-### `xargs`
-
-This is a Posix utility, but ⛩️📰 书社 currently depends on
-  unspecified behaviour.
-It requires support for the `-0` flag, which must disable the special
-  quote and whitespace handling of `xargs` in favour of null‐terminated
-  strings.
-

 ### `xmlcatalog` and `xmllint`
 
 These are not a Posix utilities.
 ### `xmlcatalog` and `xmllint`
 
 These are not a Posix utilities.


@@ -206,7 +198,6 @@ In every case, you may supply your own implementation by overriding the
 - `cksum`
 - `cp`
 - `date`
 - `cksum`
 - `cp`
 - `date`

-- `echo`

 - `file`
 - `find`
 - `git` (optional; set `GIT=` to disable)
 - `file`
 - `find`
 - `git` (optional; set `GIT=` to disable)


@@ -227,7 +218,7 @@ In every case, you may supply your own implementation by overriding the
 - `tr`
 - `uuencode`
 - `uudecode`
 - `tr`
 - `uuencode`
 - `uudecode`

-- `xargs` (requires support for `-0`)
+- `xargs`

 - `xmlcatalog` (provided by `libxml2`)
 - `xmllint` (provided by `libxml2`)
 - `xsltproc` (provided by `libxslt`)
 - `xmlcatalog` (provided by `libxml2`)
 - `xmllint` (provided by `libxml2`)
 - `xsltproc` (provided by `libxslt`)


@@ -693,6 +684,13 @@ They are :⁠—
     non X·M·L output types, ⁊·c).
   Other child elements will be ignored.
 
     non X·M·L output types, ⁊·c).
   Other child elements will be ignored.
 

+  If the `<书社:archive>` element is given an `@书社:expanded`
+    attribute, rather than producing a tarball ⛩️📰 书社 will output
+    the directory which expanding the tarball would produce.
+  This mechanism can be used to generate multiple files from a single
+    source, provided all of the files are contained with·in the same
+    directory.
+

 - **`<书社:base64-binary>`:**
   The text nodes in the transformation result will, after removing all
     Ascii whitespace, be treated as a Base·64 string, which is then
 - **`<书社:base64-binary>`:**
   The text nodes in the transformation result will, after removing all
     Ascii whitespace, be treated as a Base·64 string, which is then