about summary refs log tree commit diff
path: root/Etc/FAQ.yo
diff options
context:
space:
mode:
authorPeter Stephenson <pws@users.sourceforge.net>2008-10-29 09:57:52 +0000
committerPeter Stephenson <pws@users.sourceforge.net>2008-10-29 09:57:52 +0000
commit000fe2060b74bb396651baad6a1a8c0f31537b08 (patch)
tree567fe6a571b2222c03053f4c990a3997b6bd2f7e /Etc/FAQ.yo
parent031dd01cf20ef231c7f26b262ae01e81e3d6eb34 (diff)
downloadzsh-000fe2060b74bb396651baad6a1a8c0f31537b08.tar.gz
zsh-000fe2060b74bb396651baad6a1a8c0f31537b08.tar.xz
zsh-000fe2060b74bb396651baad6a1a8c0f31537b08.zip
update to 4.3.8 zsh-4.3.8
Diffstat (limited to 'Etc/FAQ.yo')
-rw-r--r--Etc/FAQ.yo4
1 files changed, 2 insertions, 2 deletions
diff --git a/Etc/FAQ.yo b/Etc/FAQ.yo
index faa4741fe..05ee8b277 100644
--- a/Etc/FAQ.yo
+++ b/Etc/FAQ.yo
@@ -298,7 +298,7 @@ sect(On what machines will it run?)
 sect(What's the latest version?)
 
   Zsh 4.2.7 is the latest production version.  The latest development
-  version is 4.3.7; this contains support for multibyte character strings
+  version is 4.3.8; this contains support for multibyte character strings
   (such as UTF-8 locales).  All the main features for multibyte
   support are now in place, although there is some debugging work
   still to be done.
@@ -2032,7 +2032,7 @@ sect(How does zsh handle multibyte input and output?)
   set the tt(MULTIBYTE) option.
 
   The other option that affects multibyte support is tt(COMBINING_CHARS),
-  new in version 4.3.7.  When this is set, any zero-length punctuation
+  new in version 4.3.8.  When this is set, any zero-length punctuation
   characters that follow an alphanumeric character (the base character) are
   assumed to be modifications (accents etc.) to the base character and to
   be displayed within the same screen area as the base character.  As not