[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Texi2html-cvs] Changes to texi2html/Tests/xemacs_res/xemacs_20.html
From: |
Patrice Dumas |
Subject: |
[Texi2html-cvs] Changes to texi2html/Tests/xemacs_res/xemacs_20.html |
Date: |
Tue, 23 Aug 2005 19:52:53 -0400 |
Index: texi2html/Tests/xemacs_res/xemacs_20.html
diff -u texi2html/Tests/xemacs_res/xemacs_20.html:1.25
texi2html/Tests/xemacs_res/xemacs_20.html:1.26
--- texi2html/Tests/xemacs_res/xemacs_20.html:1.25 Tue Aug 9 17:19:26 2005
+++ texi2html/Tests/xemacs_res/xemacs_20.html Tue Aug 23 23:51:17 2005
@@ -67,8 +67,8 @@
symbols, Japanese scripts (Hiragana, Katakana and Kanji), Korean scripts
(Hangul and Hanja) and Cyrillic script (for Byelorussian, Bulgarian,
Russian, Serbian and Ukrainian). These features have been merged from
-the modified version of Emacs known as MULE (for "MULti-lingual
-Enhancement to GNU Emacs").
+the modified version of Emacs known as MULE (for “MULti-lingual
+Enhancement to GNU Emacs”).
</p>
<table class="menu" border="0" cellspacing="0">
<tr><td align="left" valign="top"><a href="#SEC182">17.1 What is
Mule?</a></td><td> </td><td align="left" valign="top">
Basic concepts of Mule.
@@ -167,7 +167,7 @@
<a name="IDX698"></a>
<a name="IDX699"></a>
<p> The command <kbd>C-h h</kbd> (<code>view-hello-file</code>) displays the
file
-<tt>`etc/HELLO'</tt>, which shows how to say "hello" in many
languages.
+<tt>`etc/HELLO'</tt>, which shows how to say “hello” in many
languages.
This illustrates various scripts.
</p>
<p> Keyboards, even in the countries where these character sets are used,
@@ -312,7 +312,7 @@
<p> One way is to type the accent twice; that is a special feature for
entering the separate letter and accent. For example, <kbd>e ' '</kbd> gives
you the two characters <samp>`e''</samp>. Another way is to type another
letter
-after the <kbd>e</kbd>--something that won't combine with that--and
+after the <kbd>e</kbd>—something that won't combine with that—and
immediately delete it. For example, you could type <kbd>e e <kbd>DEL</kbd>
'</kbd> to get separate <samp>`e'</samp> and <samp>`''</samp>.
</p>
@@ -567,8 +567,8 @@
system, including the letter that stands for it in the mode line
(see section <a href="xemacs_4.html#SEC10">The Mode Line</a>).
</p>
-<p> Each of the coding systems that appear in this list--except for
-<code>binary</code>, which means no conversion of any kind--specifies how and
+<p> Each of the coding systems that appear in this list—except for
+<code>binary</code>, which means no conversion of any kind—specifies how
and
whether to convert printing characters, but leaves the choice of
end-of-line conversion to be decided based on the contents of each file.
For example, if the file appears to use carriage-return linefeed between
@@ -604,7 +604,7 @@
<code>iso-8859-1-mac</code>.
</p>
<p> In contrast, the coding system <code>binary</code> specifies no character
-code conversion at all--none for non-Latin-1 byte values and none for
+code conversion at all—none for non-Latin-1 byte values and none for
end of line. This is useful for reading or writing binary files, tar
files, and other files that must be examined verbatim.
</p>
@@ -648,7 +648,7 @@
<p> Most of the time, XEmacs can recognize which coding system to use for
-any given file-once you have specified your preferences.
+any given file–once you have specified your preferences.
</p>
<p> Some coding systems can be recognized or distinguished by which byte
sequences appear in the data. However, there are coding systems that
@@ -696,7 +696,7 @@
<p> You can specify the coding system for a particular file using the
<samp>`-*-…-*-'</samp> construct at the beginning of a file, or a local
variables list at the end (see section <a href="xemacs_30.html#SEC362">Local
Variables in Files</a>). You do this by
-defining a value for the "variable" named <code>coding</code>.
XEmacs does
+defining a value for the “variable” named <code>coding</code>.
XEmacs does
not really have a variable <code>coding</code>; instead of setting a variable,
it uses the specified coding system for the file. For example,
<samp>`-*-mode: C; coding: iso-8859-1;-*-'</samp> specifies use of the
@@ -765,7 +765,7 @@
<a name="IDX724"></a>
<a name="IDX725"></a>
<p> The command <kbd>C-x RET f</kbd>
(<code>set-buffer-file-coding-system</code>)
-specifies the file coding system for the current buffer--in other
+specifies the file coding system for the current buffer—in other
words, which coding system to use when saving or rereading the visited
file. You specify which coding system using the minibuffer. Since this
command applies to a file you have already visited, it affects only the
@@ -812,7 +812,7 @@
terminal are translated into that coding system.
</p>
<p> This feature is useful for certain character-only terminals built to
-support specific languages or character sets--for example, European
+support specific languages or character sets—for example, European
terminals that support one of the ISO Latin character sets.
</p>
<p> By default, output to the terminal is not translated at all.
@@ -822,7 +822,7 @@
<p> The command <kbd>C-x <kbd>RET</kbd> k</kbd>
(<code>set-keyboard-coding-system</code>)
specifies the coding system for keyboard input. Character-code
translation of keyboard input is useful for terminals with keys that
-send non-ASCII graphic characters--for example, some terminals designed
+send non-ASCII graphic characters—for example, some terminals designed
for ISO Latin-1 or subsets of it.
</p>
<p> By default, keyboard input is not translated at all.
@@ -853,7 +853,7 @@
to use for encoding file names. If you set the variable to a coding
system name (as a Lisp symbol or a string), XEmacs encodes file names
using that coding system for all file operations. This makes it
-possible to use non-Latin-1 characters in file names--or, at least,
+possible to use non-Latin-1 characters in file names—or, at least,
those non-Latin-1 characters which the specified coding system can
encode. By default, this variable is <code>nil</code>, which implies that you
cannot use non-Latin-1 characters in file names.