docs/latex/wx/tnoneng.tex

   1 \section{Writing non-English applications}\label{nonenglishoverview}
   2
   3 This article describes how to write applications that communicate with
   4 user in language other than English. Unfortunately many languages use
   5 different charsets under Unix and Windows (and other platforms, to make
   6 situation even more complicated). These charsets usually differ in so
   7 many characters it is impossible to use same texts under all platforms.
   8 wxWindows provide mechanism that helps you avoid distributing many
   9 identical, only differently encoded, packages with your application
  10 (e.g. help files and menu items in iso8859-13 and windows-1257). Thanks
  11 to this mechanism you can distribute only let's say iso8859-13 data
  12 and it will be handled transparently under all systems.
  13
  14 Please read \helpref{Internationalization}\label{internationalization} which
  15 describes locales concept.
  16
  17 Whereever in the following text {\it iso8859-2} and {\it windows-1250} are
  18 used, any encodings are meant and any encodings may be substituted there.
  19
  20
  21 \wxheading{Locales}
  22
  23 TODO
  24
  25 \wxheading{Converting data}
  26
  27 before storing / after loading
  28
  29 TODO
  30
  31 \wxheading{Font mapping}
  32
  33 TODO
  34
  35 \wxheading{Help files}
  36
  37 If you're using \helpref{wxHtmlHelpController}{wxhtmlhelpcontroller} there is
  38 no problem at all. You must only make sure that all HTML files contain
  39 META tag, e.g.
  40
  41 \begin{verbatim}
  42 <meta http-equiv="Content-Type" content="iso8859-2">
  43 \end{verbatim}
  44
  45 and that hhp project file contains one additional line in {\tt OPTIONS}
  46 section:
  47
  48 \begin{verbatim}
  49 Charset=iso8859-2
  50 \end{verbatim}
  51
  52 This additional entry tells HTML help controller what encoding is used
  53 in contents and index tables.