bool{} is false for empty strings

fixes bug 1193
reported by Jasen Betts.

diff --git a/doc/doc-docbook/spec.xfpt b/doc/doc-docbook/spec.xfpt
index 951cd52864fa300e69da40682135f0bb4f1d8117..12d8137818421cec23ca895c10aee2566b4d14d4 100644 (file)
--- a/doc/doc-docbook/spec.xfpt
+++ b/doc/doc-docbook/spec.xfpt
@@ -9871,7 +9871,10 @@ zero.
 This condition turns a string holding a true or false representation into
 a boolean state.  It parses &"true"&, &"false"&, &"yes"& and &"no"&
 (case-insensitively); also positive integer numbers map to true if non-zero,
 This condition turns a string holding a true or false representation into
 a boolean state.  It parses &"true"&, &"false"&, &"yes"& and &"no"&
 (case-insensitively); also positive integer numbers map to true if non-zero,

-false if zero.  Leading and trailing whitespace is ignored.
+false if zero.
+An empty string is treated as false.
+Leading and trailing whitespace is ignored;
+thus a string consisting only of whitespace is false.

 All other string values will result in expansion failure.
 
 When combined with ACL variables, this expansion condition will let you
 All other string values will result in expansion failure.
 
 When combined with ACL variables, this expansion condition will let you