| Home | All Classes | Main Classes | Annotated | Grouped Classes | Functions | |
The TQTranslator class provides internationalization support for text output. More...
#include <qtranslator.h>
Inherits TQObject.
The TQTranslator class provides internationalization support for text output.
An object of this class contains a set of TQTranslatorMessage objects, each of which specifies a translation from a source language to a target language. TQTranslator provides functions to look up translations, add new ones, remove them, load and save them, etc.
The most common use of TQTranslator is to: load a translator file created with TQt Linguist, install it using TQApplication::installTranslator(), and use it via TQObject::tr(). For example:
int main( int argc, char ** argv )
{
TQApplication app( argc, argv );
TQTranslator translator( 0 );
translator.load( "french.qm", "." );
app.installTranslator( &translator );
MyWidget m;
app.setMainWidget( &m );
m.show();
return app.exec();
}
Note that the translator must be created before the
application's main window.
Most applications will never need to do anything else with this class. The other functions provided by this class are useful for applications that work on translator files.
We call a translation a "messsage". For this reason, translation files are sometimes referred to as "message files".
It is possible to lookup a translation using findMessage() (as tr() and TQApplication::translate() do) and contains(), to insert a new translation messsage using insert(), and to remove one using remove().
Translation tools often need more information than the bare source text and translation, for example, context information to help the translator. But end-user programs that are using translations usually only need lookup. To cater for these different needs, TQTranslator can use stripped translator files that use the minimum of memory and which support little more functionality than findMessage().
Thus, load() may not load enough information to make anything more than findMessage() work. save() has an argument indicating whether to save just this minimum of information or to save everything.
"Everything" means that for each translation item the following information is kept:
The minimum for each item is just the information necessary for findMessage() to return the right text. This may include the source, context and comment, but usually it is just a hash value and the translated text.
For example, the "Cancel" in a dialog might have "Anuluj" when the program runs in Polish (in this case the source text would be "Cancel"). The context would (normally) be the dialog's class name; there would normally be no comment, and the translated text would be "Anuluj".
But it's not always so simple. The Spanish version of a printer dialog with settings for two-sided printing and binding would probably require both "Activado" and "Activada" as translations for "Enabled". In this case the source text would be "Enabled" in both cases, and the context would be the dialog's class name, but the two items would have disambiguating comments such as "two-sided printing" for one and "binding" for the other. The comment enables the translator to choose the appropriate gender for the Spanish version, and enables TQt to distinguish between translations.
Note that when TQTranslator loads a stripped file, most functions do not work. The functions that do work with stripped files are explicitly documented as such.
See also TQTranslatorMessage, TQApplication::installTranslator(), TQApplication::removeTranslator(), TQObject::tr(), TQApplication::translate(), Environment Classes, and Internationalization with TQt.
This enum type defines how TQTranslator writes translation files. There are two modes:
Note that when TQTranslator loads a stripped file, most functions do not work. The functions that do work with stripped files are explicitly documented as such.
This function works with stripped translator files.
This function works with stripped translator files.
(This is is a one-liner that calls findMessage().)
Please use findMessage() instead.
Returns the translation for the key (context, sourceText, comment) or TQString::null if there is none in this translator.
This function does not work with stripped translator files. It may appear to, but that is not dependable.
See also remove().
This function is obsolete. It is provided to keep old source working. We strongly advise against using it in new code.
If the full file name does not exist, other file names are tried in the following order:
For example, an application running in the fr_CA locale (French-speaking Canada) might call load("foo.fr_ca", "/opt/foolib"). load() would then try to open the first existing readable file from this list:
See also save().
Example: i18n/main.cpp.
Loads the .qm file data data of length len into the translator. Returns TRUE if the data is loaded successfully; otherwise returns FALSE.
The data is not copied. The caller must be able to guarantee that data will not be deleted or modified.
If you want to iterate over the list, you should iterate over a copy, e.g.
TQValueList<TQTranslatorMessage> list = myTranslator.messages();
TQValueList<TQTranslatorMessage>::Iterator it = list.begin();
while ( it != list.end() ) {
process_message( *it );
++it;
}
This function works with stripped translator files.
See also insert().
This function is obsolete. It is provided to keep old source working. We strongly advise against using it in new code.
Removes the translation associated to the key (context, sourceText, "") from this translator.
See also load().
You should never need to call this directly; save() and other functions call it as necessary. mode is for internal use.
See also save() and unsqueeze().
You should never need to call this function; it is called by insert() and friends as necessary.
See also squeeze().
This file is part of the TQt toolkit. Copyright © 1995-2007 Trolltech. All Rights Reserved.
| Copyright © 2007 Trolltech | Trademarks | TQt 3.3.8
|