diff options
Diffstat (limited to 'doc/html/i18n.html')
| -rw-r--r-- | doc/html/i18n.html | 30 |
1 files changed, 15 insertions, 15 deletions
diff --git a/doc/html/i18n.html b/doc/html/i18n.html index 6c09191b..e606ce29 100644 --- a/doc/html/i18n.html +++ b/doc/html/i18n.html @@ -133,7 +133,7 @@ the fl and fi ligatures used in typesetting US and European books. <p> </ul> <p> TQt tries to take care of all the special features listed above. You usually don't have to worry about these features so long as you use -TQt's input widgets (e.g. <a href="ntqlineedit.html">TQLineEdit</a>, <a href="ntqtextedit.html">TQTextEdit</a>, and derived classes) +TQt's input widgets (e.g. <a href="ntqlineedit.html">TQLineEdit</a>, <a href="tqtextedit.html">TQTextEdit</a>, and derived classes) and TQt's display widgets (e.g. <a href="ntqlabel.html">TQLabel</a>). <p> Support for these writing systems is transparent to the programmer and completely encapsulated in TQt's text engine. This means that you @@ -151,7 +151,7 @@ string. In some languages (e.g. Arabic or languages from the Indian subcontinent), the width and shape of a glyph changes depending on the surrounding characters. Writing input controls usually requires a certain knowledge of the scripts it is going to be used in. Usually -the easiest way is to subclass <a href="ntqlineedit.html">TQLineEdit</a> or <a href="ntqtextedit.html">TQTextEdit</a>. +the easiest way is to subclass <a href="ntqlineedit.html">TQLineEdit</a> or <a href="tqtextedit.html">TQTextEdit</a>. <p> </ul> <p> The following sections give some information on the status of the internationalization (i18n) support in TQt. @@ -389,7 +389,7 @@ useful.) <p> <h3> Support for Encodings </h3> -<a name="1-6"></a><p> The <a href="ntqtextcodec.html">TQTextCodec</a> class and the facilities in <a href="ntqtextstream.html">TQTextStream</a> make it easy to +<a name="1-6"></a><p> The <a href="tqtextcodec.html">TQTextCodec</a> class and the facilities in <a href="tqtextstream.html">TQTextStream</a> make it easy to support many input and output encodings for your users' data. When an application starts, the locale of the machine will determine the 8-bit encoding used when dealing with 8-bit data: such as for font @@ -402,8 +402,8 @@ would be: <p> <pre> <a href="tqstring.html">TQString</a> string = ...; // some Unicode text - <a href="ntqtextcodec.html">TQTextCodec</a>* codec = TQTextCodec::<a href="ntqtextcodec.html#codecForName">codecForName</a>( "ISO 8859-5" ); - <a href="ntqcstring.html">TQCString</a> encoded_string = codec-><a href="ntqtextcodec.html#fromUnicode">fromUnicode</a>( string ); + <a href="tqtextcodec.html">TQTextCodec</a>* codec = TQTextCodec::<a href="tqtextcodec.html#codecForName">codecForName</a>( "ISO 8859-5" ); + <a href="ntqcstring.html">TQCString</a> encoded_string = codec-><a href="tqtextcodec.html#fromUnicode">fromUnicode</a>( string ); ...; // use encoded_string in 8-bit operations </pre> @@ -421,8 +421,8 @@ conversion: <p> <pre> <a href="ntqcstring.html">TQCString</a> encoded_string = ...; // Some ISO 8859-5 encoded text. - <a href="ntqtextcodec.html">TQTextCodec</a>* codec = TQTextCodec::<a href="ntqtextcodec.html#codecForName">codecForName</a>("ISO 8859-5"); - <a href="tqstring.html">TQString</a> string = codec-><a href="ntqtextcodec.html#toUnicode">toUnicode</a>(encoded_string); + <a href="tqtextcodec.html">TQTextCodec</a>* codec = TQTextCodec::<a href="tqtextcodec.html#codecForName">codecForName</a>("ISO 8859-5"); + <a href="tqstring.html">TQString</a> string = codec-><a href="tqtextcodec.html#toUnicode">toUnicode</a>(encoded_string); ...; // Use string in all of TQt's TQString operations. </pre> @@ -434,18 +434,18 @@ need to process existing documents. In general, Unicode (UTF-16 or UTF-8) is best for information transferred between arbitrary people, while within a language or national group, a local standard is often more appropriate. The most important encoding to support is the one -returned by <a href="ntqtextcodec.html#codecForLocale">TQTextCodec::codecForLocale</a>(), as this is the one the user +returned by <a href="tqtextcodec.html#codecForLocale">TQTextCodec::codecForLocale</a>(), as this is the one the user is most likely to need for communicating with other people and applications (this is the codec used by local8Bit()). <p> TQt supports most of the more frequently used encodings natively. For a -complete list of supported encodings see the <a href="ntqtextcodec.html">TQTextCodec</a> +complete list of supported encodings see the <a href="tqtextcodec.html">TQTextCodec</a> documentation. <p> In some cases and for less frequently used encodings it may be -necessary to write your own <a href="ntqtextcodec.html">TQTextCodec</a> subclass. Depending on the +necessary to write your own <a href="tqtextcodec.html">TQTextCodec</a> subclass. Depending on the urgency, it may be useful to contact Trolltech technical support or ask on the <tt>qt-interest</tt> mailing list to see if someone else is already working on supporting the encoding. A useful interim measure -can be to use the <a href="ntqtextcodec.html#loadCharmapFile">TQTextCodec::loadCharmapFile</a>() function to build a +can be to use the <a href="tqtextcodec.html#loadCharmapFile">TQTextCodec::loadCharmapFile</a>() function to build a data-driven codec, although this approach has a memory and speed penalty, especially with dynamically loaded libraries. For details of writing your own TQTextCodec, see the main TQTextCodec class @@ -517,7 +517,7 @@ this is the Unix convention (see <a href="ntqfile.html#setEncodingFunction">TQFile::setEncodingFunction</a>() to explore alternative encodings). <li> File I/O defaults to the local 8-bit encoding, -with Unicode options in <a href="ntqtextstream.html">TQTextStream</a>. +with Unicode options in <a href="tqtextstream.html">TQTextStream</a>. </ul> <p> <h3> Windows </h3> @@ -553,9 +553,9 @@ results, use complete locales from your system vendor. <tr bgcolor=#f0f0f0><td><b><a href="qhebrewcodec.html">TQHebrewCodec</a></b><td>Conversion to and from visually ordered Hebrew <tr bgcolor=#f0f0f0><td><b><a href="ntqjiscodec.html">TQJisCodec</a></b><td>Conversion to and from JIS character sets <tr bgcolor=#f0f0f0><td><b><a href="ntqsjiscodec.html">TQSjisCodec</a></b><td>Conversion to and from Shift-JIS -<tr bgcolor=#f0f0f0><td><b><a href="ntqtextcodec.html">TQTextCodec</a></b><td>Conversion between text encodings -<tr bgcolor=#f0f0f0><td><b><a href="qtextdecoder.html">TQTextDecoder</a></b><td>State-based decoder -<tr bgcolor=#f0f0f0><td><b><a href="qtextencoder.html">TQTextEncoder</a></b><td>State-based encoder +<tr bgcolor=#f0f0f0><td><b><a href="tqtextcodec.html">TQTextCodec</a></b><td>Conversion between text encodings +<tr bgcolor=#f0f0f0><td><b><a href="tqtextdecoder.html">TQTextDecoder</a></b><td>State-based decoder +<tr bgcolor=#f0f0f0><td><b><a href="tqtextencoder.html">TQTextEncoder</a></b><td>State-based encoder <tr bgcolor=#f0f0f0><td><b><a href="ntqtranslator.html">TQTranslator</a></b><td>Internationalization support for text output <tr bgcolor=#f0f0f0><td><b><a href="qtranslatormessage.html">TQTranslatorMessage</a></b><td>Translator message and its properties <tr bgcolor=#f0f0f0><td><b><a href="ntqtsciicodec.html">TQTsciiCodec</a></b><td>Conversion to and from the Tamil TSCII encoding |