removed useless spaces

git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@51911 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775

docs/doxygen/overviews/fontencoding.h

@@ -7,114 +7,114 @@
 /////////////////////////////////////////////////////////////////////////////
 
 /*!
- 
+
  @page fontencoding_overview Font encoding overview
- 
+
  wxWidgets has support for multiple font encodings.
  By encoding we mean here the mapping between the character codes and the
  letters. Probably the most well-known encoding is (7 bit) ASCII one which is
  used almost universally now to represent the letters of the English alphabet
  and some other common characters. However, it is not enough to represent the
  letters of foreign alphabets and here other encodings come into play. Please
- note that we will only discuss 8-bit fonts here and not 
+ note that we will only discuss 8-bit fonts here and not
  #Unicode.
- Font encoding support is ensured by several classes: 
- #wxFont itself, but also 
- #wxFontEnumerator and 
+ Font encoding support is ensured by several classes:
+ #wxFont itself, but also
+ #wxFontEnumerator and
  #wxFontMapper. wxFont encoding support is reflected by
  a (new) constructor parameter @e encoding which takes one of the following
  values (elements of enumeration type @c wxFontEncoding):
- 
- 
- 
- 
- 
- 
+
+
+
+
+
+
  wxFONTENCODING_SYSTEM
- 
- 
- 
- 
+
+
+
+
  The default encoding of the underlying
  operating system (notice that this might be a "foreign" encoding for foreign
  versions of Windows 9x/NT).
- 
- 
- 
- 
- 
+
+
+
+
+
  wxFONTENCODING_DEFAULT
- 
- 
- 
- 
+
+
+
+
  The applications default encoding as
  returned by wxFont::GetDefaultEncoding. On
  program startup, the applications default encoding is the same as
  wxFONTENCODING_SYSTEM, but may be changed to make all the fonts created later
  to use it (by default).
- 
- 
- 
- 
- 
+
+
+
+
+
  wxFONTENCODING_ISO8859_1..15
- 
- 
- 
- 
+
+
+
+
  ISO8859 family encodings which are
  usually used by all non-Microsoft operating systems
- 
- 
- 
- 
- 
+
+
+
+
+
  wxFONTENCODING_KOI8
- 
- 
- 
- 
+
+
+
+
  Standard Cyrillic encoding for the Internet
  (but see also wxFONTENCODING_ISO8859_5 and wxFONTENCODING_CP1251)
- 
- 
- 
- 
- 
+
+
+
+
+
  wxFONTENCODING_CP1250
- 
- 
- 
- 
+
+
+
+
  Microsoft analogue of ISO8859-2
- 
- 
- 
- 
- 
+
+
+
+
+
  wxFONTENCODING_CP1251
- 
- 
- 
- 
+
+
+
+
  Microsoft analogue of ISO8859-5
- 
- 
- 
- 
- 
+
+
+
+
+
  wxFONTENCODING_CP1252
- 
- 
- 
- 
+
+
+
+
  Microsoft analogue of ISO8859-1
- 
- 
- 
- 
- 
+
+
+
+
+
  As you may see, Microsoft's encoding partly mirror the standard ISO8859 ones,
  but there are (minor) differences even between ISO8859-1 (Latin1, ISO encoding
  for Western Europe) and CP1251 (WinLatin1, standard code page for English
@@ -129,13 +129,13 @@
  written in Cyrillic) are different on different platforms and because the
  fonts in the given encoding might just not be installed (this is especially a
  problem with Unix, or, in general, non-Win32 systems).
- To clarify, the #wxFontEnumerator 
+ To clarify, the #wxFontEnumerator
  class may be used to enumerate both all available encodings and to find the
  facename(s) in which the given encoding exists. If you can find the font in
  the correct encoding with wxFontEnumerator then your troubles are over, but,
  unfortunately, sometimes this is not enough. For example, there is no standard
  way (that I know of, please tell me if you do!) to find a font on a Windows system
- for KOI8 encoding (only for WinCyrillic one which is quite different), so 
+ for KOI8 encoding (only for WinCyrillic one which is quite different), so
  #wxFontEnumerator will never return one, even if
  the user has installed a KOI8 font on his system.
  To solve this problem, a #wxFontMapper class is provided.
@@ -147,7 +147,7 @@
  All these topics are illustrated by the @ref samplefont_overview;
  please refer to it and the documentation of the classes mentioned here for
  further explanations.
- 
+
  */
- 
- 
+
+