The FAQ was merged in the i18n documentation file to avoid having many
files for a single topic.

Signed-off-by: Christophe CURIS <christophe.cu...@free.fr>
---
 FAQ.I18N                    | 69 ---------------------------------------------
 Makefile.am                 |  2 +-
 doc/build/Translations.texi | 68 ++++++++++++++++++++++++++++++++++++++++++++
 3 files changed, 69 insertions(+), 70 deletions(-)
 delete mode 100644 FAQ.I18N

diff --git a/FAQ.I18N b/FAQ.I18N
deleted file mode 100644
index 1192d6d..0000000
--- a/FAQ.I18N
+++ /dev/null
@@ -1,69 +0,0 @@
-
-If I18N support does not work for you, check these:
-
-       - the LANG environment variable is set to your locale, and 
-         the locale is supported by your OS's locale or X's locale
-         emulation. you can display all supported locales by 
-         executing "locale -a" command if it available. and you
-         can check if your locale is supported by X's locale emulation.
-         See "/usr/X11R6/lib/X11/locale/locale.alias"
-
-       - Check if you're using appropriate fonts for the locale you
-         chose. If you're using a font set that has a different 
-         encoding than the one used by Xlib or libc, bad things can
-         happen. Try specifically putting the encoding in the LANG 
-         variable, like ru_RU.KOI8-R. Again, see
-         "/usr/X11R6/lib/X11/locale/locale.alias"
-
-       - if your OS doesn't support any locale or if your OS doesn't 
-         support a locale for your language, you can use X Window System's
-         locale emulation feature instead of OS's locale. To use this
-         feature, add this option to the configure, "--with-x-locale".
-         if your OS is commercial one, such as Solaris, IRIX, AIX, ...
-         you perhaps don't have to use X's locale emulation.
-         But if your OS is Linux or NetBSD or..., it is possible that
-         your locale is not supported so far. then use "--with-x-locale".
-
-         Note: to use X's locale emulation, your Xlib has to be
-               compiled so that the locale emulation is enabled.
-               Linux RedHat5.0's default Xlib is not compiled 
-               like that. (RH4.x are ok). Recompiled Xlib for
-               RH5.0 where you can use locale emulation is available
-               here:
-               ftp://ftp.linux.or.jp/pub/RPM/glibc
-
-       - the fonts you're using support your locale. if your font
-         setting on $HOME/GNUstep/Defaults/WindowMaker is like..
-
-         WindowTitleFont = "Trebuchet MS:bold:pixelsize=12";
-         MenuTitleFont   = "Trebuchet MS:bold:pixelsize=12";
-         ......................................................
-
-         then you can't display Asian language (ja, ko, ch) characters using
-          Trebuchet MS. A font that is guaranteed to work for any language is
-          sans (or sans-serif). sans is not a font itself, but an alias which
-          points to multiple fonts and will load the first in that list that
-          has the ability to show glyphs in your language. If you don't know
-          a font that is suited for you language you can always set all your
-          fonts to something like:
-
-               "sans:pixelsize=12"
-
-          However, please note that if your font is something like:
-
-               "Trebuchet MS,sans serif:pixelsize=12"
-
-         this will not be able to display Asian languages if any of the
-          previous fonts before sans are installed. This is because unlike
-          the proper font pickup that sans guarantees for your language,
-          this construct only allows a font fallback mechanism, which tries
-          all the fonts in the list in order, until it finds one that is
-          available, even if it doesn't support your language.
-
-         Also you need to change font settings in style files in
-         the "$HOME/Library/WindowMaker/Style" directory.
-
-       - the LC_CTYPE environment variable is unset or it has the correct
-          value. If you don't know what is the correct value, unset it.
-
-
diff --git a/Makefile.am b/Makefile.am
index 351d0db..56be4db 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -29,7 +29,7 @@ ACLOCAL_AMFLAGS = -I m4
 SUBDIRS = wrlib WINGs src util po WindowMaker wmlib WPrefs.app doc
 DIST_SUBDIRS = $(SUBDIRS) test
 
-EXTRA_DIST = TODO BUGS BUGFORM FAQ FAQ.I18N INSTALL \
+EXTRA_DIST = TODO BUGS BUGFORM FAQ INSTALL \
        INSTALL-WMAKER README.i18n README.definable-cursor \
        The-perfect-Window-Maker-patch.txt \
        README COPYING.WTFPL autogen.sh \
diff --git a/doc/build/Translations.texi b/doc/build/Translations.texi
index 64168f5..60f705f 100644
--- a/doc/build/Translations.texi
+++ b/doc/build/Translations.texi
@@ -81,6 +81,7 @@ This manual is for Window Maker, version @value{version}.
 @menu
 * Enabling Languages support::  How to compile Window Maker with i18n support
 * Choosing the Language::       When installed, how to run wmaker with your 
language
+* Troubleshooting::             Some points to check if you have problems
 @end menu
 
 
@@ -228,5 +229,72 @@ or through pages like
 
@uref{http://www.shellhacks.com/en/HowTo-Change-Locale-Language-and-Character-Set-in-Linux,Shell
 Hacks' note on Changing Locale}.
 
 
+@c 
----------------------------------------------------------------------------- 
Troubleshooting ---
+@node Troubleshooting
+@chapter Troubleshooting
+
+If I18N support does not work for you, check these:
+
+@itemize @minus
+@item
+the @env{LANG} environment variable is set to your locale, and
+the locale is supported by your OS's locale or X's locale
+emulation. you can display all supported locales by
+executing "@command{locale -a}" command if it is available; you
+can check if your locale is supported by X's locale emulation,
+see @file{/usr/share/X11/locale/locale.alias}
+
+@item
+check if you are using an appropriate fonts for the locale you
+chose. If you're using a font set that has a different
+encoding than the one used by @sc{Xlib} or @sc{libc}, bad things can
+happen. Try specifically putting the encoding in the @env{LANG}
+variable, like @code{ru_RU.KOI8-R}. Again, see
+@file{/usr/share/X11/locale/locale.alias}
+
+@item
+the fonts you're using support your locale. if your font
+setting on @file{$HOME/GNUstep/Defaults/WindowMaker} is like...
+
+@example
+   WindowTitleFont = "Trebuchet MS:bold:pixelsize=12";
+   MenuTitleFont   = "Trebuchet MS:bold:pixelsize=12";
+@end example
+
+then you can't display Asian languages (@code{ja}, @code{ko}, @code{ch}, ...) 
characters using
+@code{Trebuchet MS}. A font that is guaranteed to work for any language is
+@code{sans} (or @code{sans-serif}). @code{sans} is not a font itself, but an 
alias which
+points to multiple fonts and will load the first in that list that
+has the ability to show glyphs in your language. If you don't know
+a font that is suited for your language you can always set all your
+fonts to something like:
+
+@example
+   "sans:pixelsize=12"
+@end example
+
+However, please note that if your font is something like:
+
+@example
+   "Trebuchet MS,sans serif:pixelsize=12"
+@end example
+
+this will not be able to display Asian languages if any of the
+previous fonts before sans are installed. This is because unlike
+the proper font pickup that @code{sans} guarantees for your language,
+this construct only allows a font fallback mechanism, which tries
+all the fonts in the list in order, until it finds one that is
+available, even if it doesn't support your language.
+
+Also you need to change font settings in style files in
+the @file{$HOME/Library/WindowMaker/Style} directory.
+
+@item
+the @env{LC_CTYPE} environment variable is unset or it has the correct
+value. If you don't know what is the correct value, unset it.
+
+@end itemize
+
+
 @c 
-------------------------------------------------------------------------------------
 The End ---
 @bye
-- 
2.1.4


-- 
To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.

Reply via email to