diff options
Diffstat (limited to 'doc/html/i18n.html')
| -rw-r--r-- | doc/html/i18n.html | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/doc/html/i18n.html b/doc/html/i18n.html index 837fb8cc8..75b00184e 100644 --- a/doc/html/i18n.html +++ b/doc/html/i18n.html @@ -168,7 +168,7 @@ 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="ntqobject.html">TQObject</a> names +<p> Strings that are in "programmer space" (such as <a href="tqobject.html">TQObject</a> names and file format texts) need not use TQString; the traditional char* or the <a href="ntqcstring.html">TQCString</a> class will suffice. <p> You're unlikely to notice that you are using Unicode; @@ -178,7 +178,7 @@ const char* and char from traditional C. </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="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 +to achieve this is to use <a href="tqobject.html#tr">TQObject::tr</a>(). For example, assuming the <tt>LoginWidget</tt> is a subclass of TQWidget: <p> <pre> LoginWidget::LoginWidget() @@ -191,7 +191,7 @@ to achieve this is to use <a href="ntqobject.html#tr">TQObject::tr</a>(). For ex <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="ntqobject.html">TQObject</a> subclass, use either the tr() function of an +<a href="tqobject.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> @@ -251,8 +251,8 @@ defined, you'll be very likely to catch any strings you are 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="ntqobject.html#trUtf8">TQObject::trUtf8</a>() more convenient than -<a href="ntqobject.html#tr">TQObject::tr</a>(), as tr() depends on the +might find <a href="tqobject.html#trUtf8">TQObject::trUtf8</a>() more convenient than +<a href="tqobject.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="ntqkeysequence.html">TQKeySequence</a>() for Accelerator Values @@ -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="ntqobject.html#tr">TQObject::tr</a>(){tr()} function in the usual way; for example: +<a href="tqobject.html#tr">TQObject::tr</a>(){tr()} function in the usual way; for example: <p> <pre> void MyWidget::languageChange() { |