Changeset 291 for trunk/README.OS2


Ignore:
Timestamp:
Nov 5, 2009, 11:32:53 PM (16 years ago)
Author:
Dmitry A. Kuminov
Message:

README.OS2: More words about how to properly set the LANG variable.

File:
1 edited

Legend:

Unmodified
Added
Removed

  • trunk/README.OS2

    r287 r291  
    117117     Qt.
    118118
    119   3. Make sure you have the LANG environment variable properly set.
    120      The format is ll_CC[.codepage] where ll is the language code,
    121      CC is the country code and codepage is the optional code page
    122      to use. If LANG is missing or invalid, string conversion operations
    123      may work incorrectly resulting in distorted text input or output. Note
    124      that for most languages you will have to specify the code page number
    125      explicitly or non-Latin1 symbols will not be printed correctly. Look at
    126      the CODEPAGE setting in your CONFIG.SYS to get the number of your system
    127      code page.
     119  3. Make sure you have the LANG environment variable properly set. The format
     120     is 'set LANG=ll_CC[.encoding]' where <ll> is the language code, <CC> is the
     121     country code and <encoding> is the optional encoding to use. If LANG is
     122     missing or invalid, string conversion operations may work incorrectly
     123     resulting in distorted text input or output. Note that for most languages
     124     you will have to specify the encoding number explicitly because Qt and OS/2
     125     usually disagree about the default encoding for the given language.
     126
     127     To specify the correct encoding for Qt you need to know your system code
     128     page number. You can find this number in the COUNTRY statement of your
     129     CONFIG.SYS. Note however that the code page number from CONFIG.SYS and the
     130     encoding name you specify in LANG are different things. Qt doesn't
     131     understand IBM code page numbers directly. In most cases, you can get the
     132     encoding name by prepending 'cp' to the code page number (for example,
     133     'cp850' for code page 850) but sometimes this will not work because not all
     134     encodings have 'cp'-like aliases. In this case, you should google around to
     135     find the correct encoding name for your code page number. Here is a couple
     136     of examples of the proper LANG specification:
     137
     138       set LANG=de_DE.cp850             - for the German OS/2 locale
     139       set LANG=ru_RU.cp866             - for the Russian OS/2 locale
     140
     141     Later, the correct encoding for the system code page will be detected
     142     automatically and specifying it in LANG will not be necessary.
    128143
    129144  4. Some functionality of the already available Qt classes may be limited or
Note: See TracChangeset for help on using the changeset viewer.