aboutsummaryrefslogtreecommitdiff
path: root/runtime/doc/mbyte.txt
diff options
context:
space:
mode:
Diffstat (limited to 'runtime/doc/mbyte.txt')
-rw-r--r--runtime/doc/mbyte.txt33
1 files changed, 1 insertions, 32 deletions
diff --git a/runtime/doc/mbyte.txt b/runtime/doc/mbyte.txt
index 02c00bc03b..c87ed317d4 100644
--- a/runtime/doc/mbyte.txt
+++ b/runtime/doc/mbyte.txt
@@ -97,14 +97,6 @@ is the difficult part. It depends on the system you are using, the locale and
a few other things. See the chapters on fonts: |mbyte-fonts-X11| for
X-Windows and |mbyte-fonts-MSwin| for MS-Windows.
-For GTK+ 2, you can skip most of this section. The option 'guifontset' does
-no longer exist. You only need to set 'guifont' and everything should "just
-work". If your system comes with Xft2 and fontconfig and the current font
-does not contain a certain glyph, a different font will be used automatically
-if available. The 'guifontwide' option is still supported but usually you do
-not need to set it. It is only necessary if the automatic font selection does
-not suit your needs.
-
For X11 you can set the 'guifontset' option to a list of fonts that together
cover the characters that are used. Example for Korean: >
@@ -484,11 +476,6 @@ For Vim you may need to set 'encoding' to "utf-8".
Unfortunately, using fonts in X11 is complicated. The name of a single-byte
font is a long string. For multi-byte fonts we need several of these...
-Note: Most of this is no longer relevant for GTK+ 2. Selecting a font via
-its XLFD is not supported; see 'guifont' for an example of how to
-set the font. Do yourself a favor and ignore the |XLFD| and |xfontset|
-sections below.
-
First of all, Vim only accepts fixed-width fonts for displaying text. You
cannot use proportionally spaced fonts. This excludes many of the available
(and nicer looking) fonts. However, for menus and tooltips any font can be
@@ -791,20 +778,6 @@ For example, when you are using kinput2 as |IM-server| and sh, >
export XMODIFIERS="@im=kinput2"
<
-FULLY CONTROLLED XIM
-
-You can fully control XIM, like with IME of MS-Windows (see |multibyte-ime|).
-This is currently only available for the GTK GUI.
-
-Before using fully controlled XIM, one setting is required. Set the
-'imactivatekey' option to the key that is used for the activation of the input
-method. For example, when you are using kinput2 + canna as IM Server, the
-activation key is probably Shift+Space: >
-
- :set imactivatekey=S-space
-
-See 'imactivatekey' for the format.
-
==============================================================================
8. Input on MS-Windows *mbyte-IME*
@@ -1142,14 +1115,12 @@ internally.
Vim has comprehensive UTF-8 support. It works well in:
- xterm with utf-8 support enabled
-- Motif and GTK GUI
- MS-Windows GUI
- several other platforms
Double-width characters are supported. This works best with 'guifontwide' or
'guifontset'. When using only 'guifont' the wide characters are drawn in the
-normal width and a space to fill the gap. Note that the 'guifontset' option
-is no longer relevant in the GTK+ 2 GUI.
+normal width and a space to fill the gap.
*bom-bytes*
When reading a file a BOM (Byte Order Mark) can be used to recognize the
@@ -1219,8 +1190,6 @@ doesn't always work. See the system specific remarks below, and 'langmenu'.
USING UTF-8 IN X-Windows *utf-8-in-xwindows*
-Note: This section does not apply to the GTK+ 2 GUI.
-
You need to specify a font to be used. For double-wide characters another
font is required, which is exactly twice as wide. There are three ways to do
this: