aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--doc/emacs/mule.texi51
1 files changed, 26 insertions, 25 deletions
diff --git a/doc/emacs/mule.texi b/doc/emacs/mule.texi
index fd25604c700..4989982eca0 100644
--- a/doc/emacs/mule.texi
+++ b/doc/emacs/mule.texi
@@ -1207,13 +1207,13 @@ using the internal Emacs representation.
1207@cindex file-name encoding, MS-Windows 1207@cindex file-name encoding, MS-Windows
1208@vindex w32-unicode-filenames 1208@vindex w32-unicode-filenames
1209 When Emacs runs on MS-Windows versions that are descendants of the 1209 When Emacs runs on MS-Windows versions that are descendants of the
1210NT family (Windows 2000, XP, Vista, Windows 7, and Windows 8), the 1210NT family (Windows 2000, XP, Vista, Windows 7, and all the later
1211value of @code{file-name-coding-system} is largely ignored, as Emacs 1211versions), the value of @code{file-name-coding-system} is largely
1212by default uses APIs that allow passing Unicode file names directly. 1212ignored, as Emacs by default uses APIs that allow passing Unicode file
1213By contrast, on Windows 9X, file names are encoded using 1213names directly. By contrast, on Windows 9X, file names are encoded
1214@code{file-name-coding-system}, which should be set to the codepage 1214using @code{file-name-coding-system}, which should be set to the
1215(@pxref{Coding Systems, codepage}) pertinent for the current system 1215codepage (@pxref{Coding Systems, codepage}) pertinent for the current
1216locale. The value of the variable @code{w32-unicode-filenames} 1216system locale. The value of the variable @code{w32-unicode-filenames}
1217controls whether Emacs uses the Unicode APIs when it calls OS 1217controls whether Emacs uses the Unicode APIs when it calls OS
1218functions that accept file names. This variable is set by the startup 1218functions that accept file names. This variable is set by the startup
1219code to @code{nil} on Windows 9X, and to @code{t} on newer versions of 1219code to @code{nil} on Windows 9X, and to @code{t} on newer versions of
@@ -1570,9 +1570,9 @@ used. Some examples are:
1570unpleasant results for characters for which they are used, and you may 1570unpleasant results for characters for which they are used, and you may
1571wish to instruct Emacs to completely ignore them while searching for a 1571wish to instruct Emacs to completely ignore them while searching for a
1572suitable font required to display a character. You can do that by 1572suitable font required to display a character. You can do that by
1573adding the offending fonts to the value of @code{face-ignored-fonts} 1573adding the offending fonts to the value of the variable
1574variable, which is a list. Here's an example to put in your 1574@code{face-ignored-fonts}, which is a list. Here's an example to put
1575@file{~/.emacs}: 1575in your @file{~/.emacs}:
1576 1576
1577@example 1577@example
1578(add-to-list 'face-ignored-fonts "Some Bad Font") 1578(add-to-list 'face-ignored-fonts "Some Bad Font")
@@ -1673,10 +1673,10 @@ should use the command @kbd{M-x set-keyboard-coding-system} or
1673customize the variable @code{keyboard-coding-system} to specify which 1673customize the variable @code{keyboard-coding-system} to specify which
1674coding system your keyboard uses (@pxref{Terminal Coding}). Enabling 1674coding system your keyboard uses (@pxref{Terminal Coding}). Enabling
1675this feature will probably require you to use @key{ESC} to type Meta 1675this feature will probably require you to use @key{ESC} to type Meta
1676characters; however, on a console terminal or in @code{xterm}, you can 1676characters; however, on a console terminal or a terminal emulator such
1677arrange for Meta to be converted to @key{ESC} and still be able to 1677as @code{xterm}, you can arrange for Meta to be converted to @key{ESC}
1678type 8-bit characters present directly on the keyboard or using 1678and still be able to type 8-bit characters present directly on the
1679@key{Compose} or @key{AltGr} keys. @xref{User Input}. 1679keyboard or using @key{Compose} or @key{AltGr} keys. @xref{User Input}.
1680 1680
1681@cindex @code{iso-transl} library 1681@cindex @code{iso-transl} library
1682@cindex compose character 1682@cindex compose character
@@ -1777,13 +1777,13 @@ for editing bidirectional text.
1777@dfn{logical} (or @dfn{reading}) order: the buffer or string position 1777@dfn{logical} (or @dfn{reading}) order: the buffer or string position
1778of the first character you read precedes that of the next character. 1778of the first character you read precedes that of the next character.
1779Reordering of bidirectional text into the @dfn{visual} order happens 1779Reordering of bidirectional text into the @dfn{visual} order happens
1780at display time. As result, character positions no longer increase 1780at display time. As a result, character positions no longer increase
1781monotonically with their positions on display. Emacs implements the 1781monotonically with their positions on display. Emacs implements the
1782Unicode Bidirectional Algorithm (UBA) described in the Unicode 1782Unicode Bidirectional Algorithm (UBA) described in the Unicode
1783Standard Annex #9, for reordering of bidirectional text for display. 1783Standard Annex #9, for reordering of bidirectional text for display.
1784It deviates from the UBA only in how continuation lines are displayed 1784It deviates from the UBA only in how continuation lines are displayed
1785when text direction is opposite to the base paragraph direction, 1785when text direction is opposite to the base paragraph direction,
1786e.g. when a long line of English text appears in a right-to-left 1786e.g., when a long line of English text appears in a right-to-left
1787paragraph. 1787paragraph.
1788 1788
1789@vindex bidi-display-reordering 1789@vindex bidi-display-reordering
@@ -1835,12 +1835,13 @@ thin blank characters; on text terminals they display as blanks.
1835 1835
1836 Because characters are reordered for display, Emacs commands that 1836 Because characters are reordered for display, Emacs commands that
1837operate in the logical order or on stretches of buffer positions may 1837operate in the logical order or on stretches of buffer positions may
1838produce unusual effects. For example, @kbd{C-f} and @kbd{C-b} 1838produce unusual effects. For example, the commands @kbd{C-f} and
1839commands move point in the logical order, so the cursor will sometimes 1839@kbd{C-b} move point in the logical order, so the cursor will
1840jump when point traverses reordered bidirectional text. Similarly, a 1840sometimes jump when point traverses reordered bidirectional text.
1841highlighted region covering a contiguous range of character positions 1841Similarly, a highlighted region covering a contiguous range of
1842may look discontinuous if the region spans reordered text. This is 1842character positions may look discontinuous if the region spans
1843normal and similar to the behavior of other programs that support 1843reordered text. This is normal and similar to the behavior of other
1844bidirectional text. If you set @code{visual-order-cursor-movement} to 1844programs that support bidirectional text. If you set
1845a non-@code{nil} value, cursor motion by the arrow keys follows the 1845@code{visual-order-cursor-movement} to a non-@code{nil} value, cursor
1846visual order on screen (@pxref{Moving Point, visual-order movement}). 1846motion by the arrow keys follows the visual order on screen
1847(@pxref{Moving Point, visual-order movement}).