path: root/INSTALL
authorPeter Stephenson <[email protected]>2005-12-15 10:38:55 (GMT)
committer Peter Stephenson <[email protected]>2005-12-15 10:38:55 (GMT)
commitb5a83cc7549e48a82dd57859f40a8f282f1534d0 (patch) (side-by-side diff)
tree1eba31736a892a857e5addc6d8ece520d218e4a8 /INSTALL
parent174ad4a80fa13a843a319c516e703ae74858ad39 (diff)
users/9788: add (oN) glob qualifier for no sorting
22076: more documentation for multibyte handling
Diffstat (limited to 'INSTALL') (more/less context) (ignore whitespace changes)
1 files changed, 12 insertions, 1 deletions
diff --git a/INSTALL b/INSTALL
index 855164f..a7635e1 100644
@@ -272,7 +272,16 @@ The support can be explicitly enabled or disable with --enable-multibyte or
--disable-multibyte. Reports of systems where multibyte support was not
enabled by default but --enable-multibyte resulted in a usable shell would
be appreciated. The developers are not aware of any need to use
---disable-multibyte and this should be reported as a bug.
+--disable-multibyte and this should be reported as a bug. Currently
+multibyte mode is believed to work automatically on:
+ - All(?) current GNU/Linux distributions
+ - All(?) current BSD variants
+ - OS X 10.4.3
+and to work when configured with --enable-multibyte on:
+ - Solaris 8 and later
The main shell is not yet aware of multibyte characters, so for example the
length of a scalar parameter will return the number of bytes, not
@@ -281,6 +290,8 @@ characters. This means that pattern tests such as ? and [[:alpha:]] do not
work correctly with characters in multibyte character sets beyond the ASCII
+See chapter 5 in the FAQ for some notes on multibyte input.
Memory Routines