From: Heiko Schlittermann (HS12-RIPE) Date: Mon, 17 Aug 2015 15:37:08 +0000 (+0200) Subject: Docs: Clarify white space in $h_ expansion X-Git-Tag: exim-4_87_RC1~118 X-Git-Url: https://vcs.fsf.org/?a=commitdiff_plain;h=8ae9f4a33857f2169441aab0d5a12f09548a2367;p=exim.git Docs: Clarify white space in $h_ expansion --- diff --git a/doc/doc-docbook/spec.xfpt b/doc/doc-docbook/spec.xfpt index d2b6043d6..af9da690d 100644 --- a/doc/doc-docbook/spec.xfpt +++ b/doc/doc-docbook/spec.xfpt @@ -9264,10 +9264,11 @@ by earlier ACLs are visible. Upper case and lower case letters are synonymous in header names. If the following character is white space, the terminating colon may be omitted, but this is not recommended, because you may then forget it when it is needed. When -white space terminates the header name, it is included in the expanded string. -If the message does not contain the given header, the expansion item is -replaced by an empty string. (See the &%def%& condition in section -&<>& for a means of testing for the existence of a header.) +white space terminates the header name, this white space is included in the +expanded string. If the message does not contain the given header, the +expansion item is replaced by an empty string. (See the &%def%& condition in +section &<>& for a means of testing for the existence of a +header.) If there is more than one header with the same name, they are all concatenated to form the substitution string, up to a maximum length of 64K. Unless