diff options
Diffstat (limited to 'doc/html/i18n.html')
| -rw-r--r-- | doc/html/i18n.html | 154 |
1 files changed, 77 insertions, 77 deletions
diff --git a/doc/html/i18n.html b/doc/html/i18n.html index c2203cf84..a49407e1c 100644 --- a/doc/html/i18n.html +++ b/doc/html/i18n.html @@ -133,25 +133,25 @@ 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="qlineedit.html">TQLineEdit</a>, <a href="qtextedit.html">TQTextEdit</a>, and derived classes) -and TQt's display widgets (e.g. <a href="qlabel.html">TQLabel</a>). +TQt's input widgets (e.g. <a href="ntqlineedit.html">TQLineEdit</a>, <a href="ntqtextedit.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 don't need to have any knowledge about the writing system used in a particular language, except for the following small points: <ul> -<p> <li> <a href="qpainter.html#drawText">TQPainter::drawText</a>( int x, int y, const <a href="qstring.html">TQString</a> &str ) will always +<p> <li> <a href="ntqpainter.html#drawText">TQPainter::drawText</a>( int x, int y, const <a href="ntqstring.html">TQString</a> &str ) will always draw the string with it's left edge at the position specified with the x, y parameters. This will usually give you left aligned strings. Arabic and Hebrew application strings are usually right aligned, so for these languages use the version of drawText() that -takes a <a href="qrect.html">TQRect</a> since this will align in accordance with the language. -<p> <li> When you write your own text input controls, use <a href="qfontmetrics.html#charWidth">TQFontMetrics::charWidth</a>() to determine the width of a character in a +takes a <a href="ntqrect.html">TQRect</a> since this will align in accordance with the language. +<p> <li> When you write your own text input controls, use <a href="ntqfontmetrics.html#charWidth">TQFontMetrics::charWidth</a>() to determine the width of a character in a 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="qlineedit.html">TQLineEdit</a> or <a href="qtextedit.html">TQTextEdit</a>. +the easiest way is to subclass <a href="ntqlineedit.html">TQLineEdit</a> or <a href="ntqtextedit.html">TQTextEdit</a>. <p> </ul> <p> The following sections give some information on the status of the internationalization (i18n) support in TQt. @@ -161,29 +161,29 @@ of the internationalization (i18n) support in TQt. <a name="1"></a><p> Writing multi-platform international software with TQt is a gentle, incremental process. Your software can become internationalized in the following stages: -<p> <h3> Use <a href="qstring.html">TQString</a> for all User-visible Text +<p> <h3> Use <a href="ntqstring.html">TQString</a> for all User-visible Text </h3> <a name="1-1"></a><p> Since TQString uses the Unicode encoding internally, every language in the world can be processed transparently using familiar text processing operations. Also, since all TQt functions that present text to the user take a TQString as a parameter, there is no char* to TQString conversion overhead. -<p> Strings that are in "programmer space" (such as <a href="qobject.html">TQObject</a> names +<p> Strings that are in "programmer space" (such as <a href="ntqobject.html">TQObject</a> names and file format texts) need not use TQString; the traditional -char* or the <a href="qcstring.html">TQCString</a> class will suffice. +char* or the <a href="ntqcstring.html">TQCString</a> class will suffice. <p> You're unlikely to notice that you are using Unicode; TQString, and <a href="qchar.html">TQChar</a> are just like easier versions of the crude const char* and char from traditional C. <p> <h3> Use tr() for all Literal Text </h3> <a name="1-2"></a><p> Wherever your program uses <tt>"quoted text"</tt> for text that will -be presented to the user, ensure that it is processed by the <a href="qapplication.html#translate">TQApplication::translate</a>() function. Essentially all that is necessary -to achieve this is to use <a href="qobject.html#tr">TQObject::tr</a>(). For example, assuming the +be presented to the user, ensure that it is processed by the <a href="ntqapplication.html#translate">TQApplication::translate</a>() function. Essentially all that is necessary +to achieve this is to use <a href="ntqobject.html#tr">TQObject::tr</a>(). For example, assuming the <tt>LoginWidget</tt> is a subclass of TQWidget: <p> <pre> LoginWidget::LoginWidget() { - <a href="qlabel.html">TQLabel</a> *label = new <a href="qlabel.html">TQLabel</a>( tr("Password:"), this ); + <a href="ntqlabel.html">TQLabel</a> *label = new <a href="ntqlabel.html">TQLabel</a>( tr("Password:"), this ); ... } </pre> @@ -191,20 +191,20 @@ to achieve this is to use <a href="qobject.html#tr">TQObject::tr</a>(). For exam <p> This accounts for 99% of the user-visible strings you're likely to write. <p> If the quoted text is not in a member function of a -<a href="qobject.html">TQObject</a> subclass, use either the tr() function of an -appropriate class, or the <a href="qapplication.html#translate">TQApplication::translate</a>() function +<a href="ntqobject.html">TQObject</a> subclass, use either the tr() function of an +appropriate class, or the <a href="ntqapplication.html#translate">TQApplication::translate</a>() function directly: <p> <pre> void some_global_function( LoginWidget *logwid ) { - <a href="qlabel.html">TQLabel</a> *label = new <a href="qlabel.html">TQLabel</a>( + <a href="ntqlabel.html">TQLabel</a> *label = new <a href="ntqlabel.html">TQLabel</a>( LoginWidget::tr("Password:"), logwid ); } void same_global_function( LoginWidget *logwid ) { - <a href="qlabel.html">TQLabel</a> *label = new <a href="qlabel.html">TQLabel</a>( - qApp-><a href="qapplication.html#translate">translate</a>("LoginWidget", "Password:"), + <a href="ntqlabel.html">TQLabel</a> *label = new <a href="ntqlabel.html">TQLabel</a>( + qApp-><a href="ntqapplication.html#translate">translate</a>("LoginWidget", "Password:"), logwid ); } </pre> @@ -238,42 +238,42 @@ The macros expand to just the text (without the context). return tr( greeting_strings[greet_type] ); } - <a href="qstring.html">TQString</a> global_greeting( int greet_type ) + <a href="ntqstring.html">TQString</a> global_greeting( int greet_type ) { - return qApp-><a href="qapplication.html#translate">translate</a>( "FriendlyConversation", + return qApp-><a href="ntqapplication.html#translate">translate</a>( "FriendlyConversation", greeting_strings[greet_type] ); } </pre> -<p> If you disable the const char* to <a href="qstring.html">TQString</a> automatic conversion +<p> If you disable the const char* to <a href="ntqstring.html">TQString</a> automatic conversion by compiling your software with the macro QT_NO_CAST_ASCII defined, you'll be very likely to catch any strings you are -missing. See <a href="qstring.html#fromLatin1">TQString::fromLatin1</a>() for more information. +missing. See <a href="ntqstring.html#fromLatin1">TQString::fromLatin1</a>() for more information. Disabling the conversion can make programming a bit cumbersome. <p> If your source language uses characters outside Latin-1, you -might find <a href="qobject.html#trUtf8">TQObject::trUtf8</a>() more convenient than -<a href="qobject.html#tr">TQObject::tr</a>(), as tr() depends on the -<a href="qapplication.html#defaultCodec">TQApplication::defaultCodec</a>(), which makes it more fragile than +might find <a href="ntqobject.html#trUtf8">TQObject::trUtf8</a>() more convenient than +<a href="ntqobject.html#tr">TQObject::tr</a>(), as tr() depends on the +<a href="ntqapplication.html#defaultCodec">TQApplication::defaultCodec</a>(), which makes it more fragile than TQObject::trUtf8(). -<p> <h3> Use <a href="qkeysequence.html">TQKeySequence</a>() for Accelerator Values +<p> <h3> Use <a href="ntqkeysequence.html">TQKeySequence</a>() for Accelerator Values </h3> <a name="1-3"></a><p> Accelerator values such as Ctrl+Q or Alt+F need to be translated too. If you hardcode <tt>CTRL+Key_Q</tt> for "Quit" in your application, translators won't be able to override it. The correct idiom is <p> <pre> - <a href="qpopupmenu.html">TQPopupMenu</a> *file = new <a href="qpopupmenu.html">TQPopupMenu</a>( this ); - file-><a href="qmenudata.html#insertItem">insertItem</a>( tr("&Quit"), this, SLOT(quit()), + <a href="ntqpopupmenu.html">TQPopupMenu</a> *file = new <a href="ntqpopupmenu.html">TQPopupMenu</a>( this ); + file-><a href="ntqmenudata.html#insertItem">insertItem</a>( tr("&Quit"), this, SLOT(quit()), TQKeySequence(tr("Ctrl+Q", "File|Quit")) ); </pre> -<p> <h3> Use <a href="qstring.html#arg">TQString::arg</a>() for Dynamic Text +<p> <h3> Use <a href="ntqstring.html#arg">TQString::arg</a>() for Dynamic Text </h3> <a name="1-4"></a><p> The TQString::arg() functions offer a simple means for substituting arguments: <pre> void FileCopier::showProgress( int done, int total, - const <a href="qstring.html">TQString</a>& current_file ) + const <a href="ntqstring.html">TQString</a>& current_file ) { label.setText( tr("%1 of %2 files copied.\nCopying: %3") .arg(done) @@ -286,11 +286,11 @@ arguments: can easily be achieved by changing the order of the % arguments. For example: <pre> - <a href="qstring.html">TQString</a> s1 = "%1 of %2 files copied. Copying: %3"; - <a href="qstring.html">TQString</a> s2 = "Kopierer nu %3. Av totalt %2 filer er %1 kopiert."; + <a href="ntqstring.html">TQString</a> s1 = "%1 of %2 files copied. Copying: %3"; + <a href="ntqstring.html">TQString</a> s2 = "Kopierer nu %3. Av totalt %2 filer er %1 kopiert."; - <a href="qapplication.html#qDebug">qDebug</a>( s1.<a href="qstring.html#arg">arg</a>(5).arg(10).arg("somefile.txt").ascii() ); - <a href="qapplication.html#qDebug">qDebug</a>( s2.<a href="qstring.html#arg">arg</a>(5).arg(10).arg("somefile.txt").ascii() ); + <a href="ntqapplication.html#qDebug">qDebug</a>( s1.<a href="ntqstring.html#arg">arg</a>(5).arg(10).arg("somefile.txt").ascii() ); + <a href="ntqapplication.html#qDebug">qDebug</a>( s2.<a href="ntqstring.html#arg">arg</a>(5).arg(10).arg("somefile.txt").ascii() ); </pre> <p> produces the correct output in English and Norwegian: @@ -345,8 +345,8 @@ project file as a command-line argument. Norwegian and Swedish. If you use <a href="qmake-manual.html">qmake</a>, you usually don't need an extra project file for <em>lupdate</em>; your <tt>qmake</tt> project file will work fine once you add the <tt>TRANSLATIONS</tt> entry. -<p> In your application, you must <a href="qtranslator.html#load">TQTranslator::load</a>() the translation -files appropriate for the user's language, and install them using <a href="qapplication.html#installTranslator">TQApplication::installTranslator</a>(). +<p> In your application, you must <a href="ntqtranslator.html#load">TQTranslator::load</a>() the translation +files appropriate for the user's language, and install them using <a href="ntqapplication.html#installTranslator">TQApplication::installTranslator</a>(). <p> If you have been using the old TQt tools (<tt>findtr</tt>, <tt>msg2qm</tt> and <tt>mergetr</tt>), you can use <em>qm2ts</em> to convert your old <tt>.qm</tt> files. <p> <em>linguist</em>, <em>lupdate</em> and <em>lrelease</em> are installed in the <tt>bin</tt> subdirectory of the base directory TQt is installed into. Click Help|Manual @@ -354,9 +354,9 @@ in <em>TQt Linguist</em> to access the user's manual; it contains a tutorial to get you started. <p> While these utilities offer a convenient way to create <tt>.qm</tt> files, any system that writes <tt>.qm</tt> files is sufficient. You could make an -application that adds translations to a <a href="qtranslator.html">TQTranslator</a> with -<a href="qtranslator.html#insert">TQTranslator::insert</a>() and then writes a <tt>.qm</tt> file with -<a href="qtranslator.html#save">TQTranslator::save</a>(). This way the translations can come from any +application that adds translations to a <a href="ntqtranslator.html">TQTranslator</a> with +<a href="ntqtranslator.html#insert">TQTranslator::insert</a>() and then writes a <tt>.qm</tt> file with +<a href="ntqtranslator.html#save">TQTranslator::save</a>(). This way the translations can come from any source you choose. <p> <a name="qt-itself"></a> TQt itself contains over 400 strings that will also need to be @@ -369,27 +369,27 @@ useful.) <pre> int main( int argc, char **argv ) { - <a href="qapplication.html">TQApplication</a> app( argc, argv ); + <a href="ntqapplication.html">TQApplication</a> app( argc, argv ); // translation file for TQt - <a href="qtranslator.html">TQTranslator</a> qt( 0 ); - qt.<a href="qtranslator.html#load">load</a>( TQString( "qt_" ) + TQTextCodec::locale(), "." ); - app.<a href="qapplication.html#installTranslator">installTranslator</a>( &qt ); + <a href="ntqtranslator.html">TQTranslator</a> qt( 0 ); + qt.<a href="ntqtranslator.html#load">load</a>( TQString( "qt_" ) + TQTextCodec::locale(), "." ); + app.<a href="ntqapplication.html#installTranslator">installTranslator</a>( &qt ); // translation file for application strings - <a href="qtranslator.html">TQTranslator</a> myapp( 0 ); - myapp.<a href="qtranslator.html#load">load</a>( TQString( "myapp_" ) + TQTextCodec::locale(), "." ); - app.<a href="qapplication.html#installTranslator">installTranslator</a>( &myapp ); + <a href="ntqtranslator.html">TQTranslator</a> myapp( 0 ); + myapp.<a href="ntqtranslator.html#load">load</a>( TQString( "myapp_" ) + TQTextCodec::locale(), "." ); + app.<a href="ntqapplication.html#installTranslator">installTranslator</a>( &myapp ); ... - return app.<a href="qapplication.html#exec">exec</a>(); + return app.<a href="ntqapplication.html#exec">exec</a>(); } </pre> <p> <h3> Support for Encodings </h3> -<a name="1-6"></a><p> The <a href="qtextcodec.html">TQTextCodec</a> class and the facilities in <a href="qtextstream.html">TQTextStream</a> make it easy to +<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 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 @@ -400,29 +400,29 @@ Cyrillic KOI8-R locale (the de-facto standard locale in Russia) might need to output Cyrillic in the ISO 8859-5 encoding. Code for this would be: <p> <pre> - <a href="qstring.html">TQString</a> string = ...; // some Unicode text + <a href="ntqstring.html">TQString</a> string = ...; // some Unicode text - <a href="qtextcodec.html">TQTextCodec</a>* codec = TQTextCodec::<a href="qtextcodec.html#codecForName">codecForName</a>( "ISO 8859-5" ); - <a href="qcstring.html">TQCString</a> encoded_string = codec-><a href="qtextcodec.html#fromUnicode">fromUnicode</a>( string ); + <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 ); ...; // use encoded_string in 8-bit operations </pre> <p> For converting Unicode to local 8-bit encodings, a shortcut is -available: the <a href="qstring.html#local8Bit">local8Bit</a>() method -of <a href="qstring.html">TQString</a> returns such 8-bit data. Another useful shortcut is the -<a href="qstring.html#utf8">utf8</a>() method, which returns text in the +available: the <a href="ntqstring.html#local8Bit">local8Bit</a>() method +of <a href="ntqstring.html">TQString</a> returns such 8-bit data. Another useful shortcut is the +<a href="ntqstring.html#utf8">utf8</a>() method, which returns text in the 8-bit UTF-8 encoding: this perfectly preserves Unicode information while looking like plain US-ASCII if the text is wholly US-ASCII. -<p> For converting the other way, there are the <a href="qstring.html#fromUtf8">TQString::fromUtf8</a>() and -<a href="qstring.html#fromLocal8Bit">TQString::fromLocal8Bit</a>() convenience functions, or the general code, +<p> For converting the other way, there are the <a href="ntqstring.html#fromUtf8">TQString::fromUtf8</a>() and +<a href="ntqstring.html#fromLocal8Bit">TQString::fromLocal8Bit</a>() convenience functions, or the general code, demonstrated by this conversion from ISO 8859-5 Cyrillic to Unicode conversion: <p> <pre> - <a href="qcstring.html">TQCString</a> encoded_string = ...; // Some ISO 8859-5 encoded text. + <a href="ntqcstring.html">TQCString</a> encoded_string = ...; // Some ISO 8859-5 encoded text. - <a href="qtextcodec.html">TQTextCodec</a>* codec = TQTextCodec::<a href="qtextcodec.html#codecForName">codecForName</a>("ISO 8859-5"); - <a href="qstring.html">TQString</a> string = codec-><a href="qtextcodec.html#toUnicode">toUnicode</a>(encoded_string); + <a href="ntqtextcodec.html">TQTextCodec</a>* codec = TQTextCodec::<a href="ntqtextcodec.html#codecForName">codecForName</a>("ISO 8859-5"); + <a href="ntqstring.html">TQString</a> string = codec-><a href="ntqtextcodec.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="qtextcodec.html#codecForLocale">TQTextCodec::codecForLocale</a>(), as this is the one the user +returned by <a href="ntqtextcodec.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="qtextcodec.html">TQTextCodec</a> +complete list of supported encodings see the <a href="ntqtextcodec.html">TQTextCodec</a> documentation. <p> In some cases and for less frequently used encodings it may be -necessary to write your own <a href="qtextcodec.html">TQTextCodec</a> subclass. Depending on the +necessary to write your own <a href="ntqtextcodec.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="qtextcodec.html#loadCharmapFile">TQTextCodec::loadCharmapFile</a>() function to build a +can be to use the <a href="ntqtextcodec.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 @@ -482,7 +482,7 @@ to the user's language settings while they are still running. To make widgets aware of changes to the system language, implement a public slot called <tt>languageChange()</tt> in each widget that needs to be notified. In this slot, you should update the text displayed by widgets using the -<a href="qobject.html#tr">TQObject::tr</a>(){tr()} function in the usual way; for example: +<a href="ntqobject.html#tr">TQObject::tr</a>(){tr()} function in the usual way; for example: <p> <pre> void MyWidget::languageChange() { @@ -492,8 +492,8 @@ void MyWidget::languageChange() } </pre> -<p> The default event handler for <a href="qwidget.html">TQWidget</a> subclasses responds to the -<a href="qevent.html#Type-enum">LanguageChange</a> event, and will call this slot +<p> The default event handler for <a href="ntqwidget.html">TQWidget</a> subclasses responds to the +<a href="ntqevent.html#Type-enum">LanguageChange</a> event, and will call this slot when necessary; other application components can also connect signals to this slot to force widgets to update themselves. <p> <h2> System Support @@ -514,10 +514,10 @@ are under development in some Unix variants. All TQt file functions allow Unicode, but convert filenames to the local 8-bit encoding, as this is the Unix convention -(see <a href="qfile.html#setEncodingFunction">TQFile::setEncodingFunction</a>() +(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="qtextstream.html">TQTextStream</a>. +with Unicode options in <a href="ntqtextstream.html">TQTextStream</a>. </ul> <p> <h3> Windows </h3> @@ -544,21 +544,21 @@ results, use complete locales from your system vendor. <a name="5"></a><p> These classes are relevant to internationalizing TQt applications. <p><table width="100%"> -<tr bgcolor=#f0f0f0><td><b><a href="qbig5codec.html">TQBig5Codec</a></b><td>Conversion to and from the Big5 encoding -<tr bgcolor=#f0f0f0><td><b><a href="qeucjpcodec.html">TQEucJpCodec</a></b><td>Conversion to and from EUC-JP character sets -<tr bgcolor=#f0f0f0><td><b><a href="qeuckrcodec.html">TQEucKrCodec</a></b><td>Conversion to and from EUC-KR character sets -<tr bgcolor=#f0f0f0><td><b><a href="qgb18030codec.html">TQGb18030Codec</a></b><td>Conversion to and from the Chinese GB18030/GBK/GB2312 encoding +<tr bgcolor=#f0f0f0><td><b><a href="ntqbig5codec.html">TQBig5Codec</a></b><td>Conversion to and from the Big5 encoding +<tr bgcolor=#f0f0f0><td><b><a href="ntqeucjpcodec.html">TQEucJpCodec</a></b><td>Conversion to and from EUC-JP character sets +<tr bgcolor=#f0f0f0><td><b><a href="ntqeuckrcodec.html">TQEucKrCodec</a></b><td>Conversion to and from EUC-KR character sets +<tr bgcolor=#f0f0f0><td><b><a href="ntqgb18030codec.html">TQGb18030Codec</a></b><td>Conversion to and from the Chinese GB18030/GBK/GB2312 encoding <tr bgcolor=#f0f0f0><td><b><a href="qgb2312codec.html">TQGb2312Codec</a></b><td>Conversion to and from the Chinese GB2312 encoding -<tr bgcolor=#f0f0f0><td><b><a href="qgbkcodec.html">TQGbkCodec</a></b><td>Conversion to and from the Chinese GBK encoding +<tr bgcolor=#f0f0f0><td><b><a href="ntqgbkcodec.html">TQGbkCodec</a></b><td>Conversion to and from the Chinese GBK encoding <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="qjiscodec.html">TQJisCodec</a></b><td>Conversion to and from JIS character sets -<tr bgcolor=#f0f0f0><td><b><a href="qsjiscodec.html">TQSjisCodec</a></b><td>Conversion to and from Shift-JIS -<tr bgcolor=#f0f0f0><td><b><a href="qtextcodec.html">TQTextCodec</a></b><td>Conversion between text encodings +<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="qtranslator.html">TQTranslator</a></b><td>Internationalization support for text output +<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="qtsciicodec.html">TQTsciiCodec</a></b><td>Conversion to and from the Tamil TSCII encoding +<tr bgcolor=#f0f0f0><td><b><a href="ntqtsciicodec.html">TQTsciiCodec</a></b><td>Conversion to and from the Tamil TSCII encoding </table> <!-- eof --> <p><address><hr><div align=center> |