This makes our docs compatible with texinfo-6.7. There was one file,
sxemacs-faq.texi, that I ended up converting to UTF-8. Please be
aware and take care when editing that one from now on.
I did the conversion outside of SXEmacs with iconv and sed, so as to
eliminate any risk of corruption. Here is how...
,----
| iconv -f ISO-8859-1 -t UTF-8//TRANSLIT -o utf-sxemacs-faq.texi
| sxemacs-faq.texi &&
|
| sed -i -e 's/iso-2022-8/utf-8/' -e '3i@documentencoding UTF-8' \
| utf-sxemacs-faq.texi &&
| mv -v {utf-,}sxemacs-faq.texi
`----
I did attempt to find any occurances of chars it couldn't convert, but
I'm sure you'll agree that searching for the odd out of place `?' in
a large FAQ... well, "needle in a hay-stack" comes to mind.
* info/sxemacs-faq.texi: Convert file t UTF-8.
Set @documentencoding UTF-8
(Q1.3.8): Fix a @ref
* info/sppm.texi (Sending a patch from a git repo): Remove
@indent from within `@code' sections. It's frowned upon in
texinfo 6.7.
* info/lispref/ldap.texi (LDAP Variables): Fix file
corruption.
Reported-by: Andrés Ramírez <rrandresf@gmail.com>
Signed-off-by: Steve Youngs <steve@sxemacs.org>
library SXEmacs was compiled with, they may include @code{simple},
@code{krbv41} and @code{krbv42}.
@item base
library SXEmacs was compiled with, they may include @code{simple},
@code{krbv41} and @code{krbv42}.
@item base
-The base for the search. This may look like @samp{cÿ, o¬me}, see
+The base for the search. This may look like @samp{o=ACME, c=US}, see
RFC 1779 for syntax details.
@item scope
One of the symbols @code{base}, @code{onelevel} or @code{subtree}
RFC 1779 for syntax details.
@item scope
One of the symbols @code{base}, @code{onelevel} or @code{subtree}
@enumerate
@item
@code{git format-patch --add-header="X-Git-Repo: REPO-URL" \@*
@enumerate
@item
@code{git format-patch --add-header="X-Git-Repo: REPO-URL" \@*
-@indent
---add-header="X-Git-Branch: for-steve" \@*
-@indent
---subject-prefix="P-Req" --minimal --numbered -o DIR origin/master}
+ --add-header="X-Git-Branch: for-steve" \@*
+ --subject-prefix="P-Req" --minimal --numbered -o DIR origin/master}
@item
@code{git send-email \@*
@item
@code{git send-email \@*
-@indent
---to="SXEmacs Patches <sxemacs-patches@@sxemacs.org>" \@*
-@indent
---from="$(git config user.name) <$(git config user.email)>" DIR}
+ --to="SXEmacs Patches <sxemacs-patches@@sxemacs.org>" \@*
+ --from="$(git config user.name) <$(git config user.email)>" DIR}
@end enumerate
If you not have have a publicly accessible repository, the SXEmacs
@end enumerate
If you not have have a publicly accessible repository, the SXEmacs
-\input texinfo.tex @c -*- mode: texinfo; coding: iso-2022-8 -*-
+\input texinfo.tex @c -*- mode: texinfo; coding: utf-8 -*-
@setfilename sxemacs-faq.info
@settitle Frequently asked questions about SXEmacs
@setchapternewpage off
@setfilename sxemacs-faq.info
@settitle Frequently asked questions about SXEmacs
@setchapternewpage off
@author Chuck Thompson <cthomp@@xemacs.org>
@author Steve Baur <steve@@xemacs.org>
@author Andreas Kaempf <andreas@@sccon.com>
@author Chuck Thompson <cthomp@@xemacs.org>
@author Steve Baur <steve@@xemacs.org>
@author Andreas Kaempf <andreas@@sccon.com>
-@author Christian Nybø <chr@@mediascience.no>
+@author Christian Nybø <chr@@mediascience.no>
@author Sandra Wambold <wambold@@xemacs.org>
@page
@end titlepage
@author Sandra Wambold <wambold@@xemacs.org>
@page
@end titlepage
@email{steve@@xemacs.org, Steven L. Baur}. It was converted back to
texinfo by @email{hniksic@@xemacs.org, Hrvoje Niksic}. The FAQ was then
maintained by @email{andreas@@sccon.com, Andreas Kaempf}, who passed it
@email{steve@@xemacs.org, Steven L. Baur}. It was converted back to
texinfo by @email{hniksic@@xemacs.org, Hrvoje Niksic}. The FAQ was then
maintained by @email{andreas@@sccon.com, Andreas Kaempf}, who passed it
If you notice any errors or items which should be added or amended to
this FAQ please send email to @email{sxemacs-devel@@sxemacs.org}.
If you notice any errors or items which should be added or amended to
this FAQ please send email to @email{sxemacs-devel@@sxemacs.org}.
so on), and SKK, for Japanese. (SKK also supports an interface to an
external "dictionary server" process.) Quail supports both typical
"dead-key" methods (eg, in the "latin-1-prefix" method, @kbd{" a}
so on), and SKK, for Japanese. (SKK also supports an interface to an
external "dictionary server" process.) Quail supports both typical
"dead-key" methods (eg, in the "latin-1-prefix" method, @kbd{" a}
-produces ä, LATIN SMALL LETTER A WITH DIAERESIS), and the complex
+produces ä, LATIN SMALL LETTER A WITH DIAERESIS), and the complex
dictionary-based phonetic methods used for Asian ideographic languages
like Chinese.
dictionary-based phonetic methods used for Asian ideographic languages
like Chinese.
Wnn and SJ3 use the @code{egg} user interface. The interface for Canna
is specialized to Canna.
Wnn and SJ3 use the @code{egg} user interface. The interface for Canna
is specialized to Canna.
-Wnn supports Japanese, Chinese and Korean. It is made by OMRON and Kyôto
+Wnn supports Japanese, Chinese and Korean. It is made by OMRON and Kyôto
University. It is a powerful and complex system. Wnn4 is free and Wnn6
is not. Wnn uses grammatical hints and probability of word association,
so in principle Wnn can be cleverer than other methods.
University. It is a powerful and complex system. Wnn4 is free and Wnn6
is not. Wnn uses grammatical hints and probability of word association,
so in principle Wnn can be cleverer than other methods.
@unnumberedsec Q1.3.8: Does SXEmacs support Unicode?
Partially, as an external encoding for files, processes, and terminals.
@unnumberedsec Q1.3.8: Does SXEmacs support Unicode?
Partially, as an external encoding for files, processes, and terminals.
-It does not yet support Unicode fonts @ref{Q1.3.9, Does SXEmacs support
-Unicode Fonts?}
+It does not yet support Unicode fonts, see @ref{Q1.3.9}.
To get Unicode support, you need a Mule-enabled SXEmacs. Install
Mule-UCS from packages in the usual way. Put
To get Unicode support, you need a Mule-enabled SXEmacs. Install
Mule-UCS from packages in the usual way. Put
@unnumberedsec Q3.5.7: How can you type in special characters in SXEmacs?
@c Changed
One way is to use the package @code{x-compose}. Then you can use
@unnumberedsec Q3.5.7: How can you type in special characters in SXEmacs?
@c Changed
One way is to use the package @code{x-compose}. Then you can use
-sequences like @kbd{Compose " a} to get ä, etc.
+sequences like @kbd{Compose " a} to get ä, etc.
Another way is to use the @code{iso-insert} package. Then you can use
Another way is to use the @code{iso-insert} package. Then you can use
-sequences like @kbd{C-x 8 " a} to get ä, etc.
+sequences like @kbd{C-x 8 " a} to get ä, etc.
@email{glynn@@sensei.co.uk, Glynn Clements} writes:
@email{glynn@@sensei.co.uk, Glynn Clements} writes:
Once you have Multi_key defined, you can use e.g.
@example
Once you have Multi_key defined, you can use e.g.
@example
- Multi a ' => á
- Multi e " => ë
- Multi c , => ç
+ Multi a ' => á
+ Multi e " => ë
+ Multi c , => ç
@kbd{C-h n} will no longer find NEWS files from packages -- Youngs.
@item
@kbd{C-h n} will no longer find NEWS files from packages -- Youngs.
@item
-List of package mirrors updated -- Aichner, Skyttä.
+List of package mirrors updated -- Aichner, Skyttä.
@item
Bootstrappable PUI -- Youngs.
@item
Bootstrappable PUI -- Youngs.
projects / sxemacs / commitdiff