Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

lrelease(1) [redhat man page]

lrelease(1)						      General Commands Manual						       lrelease(1)

NAME
lrelease - generate Qt message files from Qt Linguist translation files SYNOPSIS
lrelease [ options ] project-file lrelease [ options ] ts-files DESCRIPTION
This page documents the Qt Linguist Release tool for the Qt GUI toolkit. Lrelease reads a qmake/tmake project file (.pro file) and con- verts the translation files (.ts files) specified in it into Qt message files (.qm files) used by the application to translate. The .qm file format is a compact binary format that provides extremely fast lookups for translations and that is used by Qt. OPTIONS
-help Display the usage and exit. -verbose Explain what is being done. -version Display the version of lrelease and exit. USAGE
Here is an example .pro file that can be given to lrelease: HEADERS = funnydialog.h wackywidget.h SOURCES = funnydialog.cpp main.cpp wackywidget.cpp FORMS = fancybox.ui TRANSLATIONS = gnomovision_dk.ts gnomovision_fi.ts gnomovision_no.ts gnomovision_se.ts When running lrelease on this project file, the Qt message files gnomovision_dk.qm, gnomovision_fi.qm, gnomovision_no.qm and gnomovi- sion_se.qm will be generated from gnomovision_dk.ts, gnomovision_fi.ts, gnomovision_no.ts and gnomovision_se.ts, respectively. Lrelease can also be invoked with a list of .ts files to convert: lrelease gnomovision_*.ts SEE ALSO
lupdate(1) and http://doc.trolltech.com/i18n.html Trolltech AS 18 October 2001 lrelease(1)

Check Out this Related Man Page

uic(1)							      General Commands Manual							    uic(1)

NAME
uic - Qt user interface compiler SYNOPSIS
uic [options] file DESCRIPTION
This page documents the User Interface Compiler for the Qt GUI toolkit. The uic reads a user interface definition (.ui) file in XML as gen- erated by Qt Designer and creates corresponding C++ header or source files. It also generates an image file that embeds raw image data in C++ source code. Generate declaration: uic [options] <file> Generate implementation: uic [options] -impl <headerfile> <file> <headerfile>: name of the declaration file Generate image collection: uic [options] -embed <project> <image1> <image2> <image3> ... <project>: project name <image[1..n]>: image files For convenience, uic can also generate declaration or implementation stubs for subclasses. Generate subclass declaration: uic [options] -subdecl <subclassname> <baseclassheaderfile> <file> <subclassname>: name of the subclass to generate <baseclassheaderfile>: declaration file of the baseclass Generate subclass implementation: uic [options] -subimpl <subclassname> <subclassheaderfile> <file> <subclassname>: name of the subclass to generate <subclassheaderfile>: declaration file of the subclass GENERAL OPTIONS
-o file Write output to file rather than to stdout. -nofwd Omit forward declarations of custom classes in the generated header file. This is necessary if typedef classes are used. -tr func Use func() instead of tr() for internationalization. -version Display the version of uic and exit. USAGE
uic is almost always invoked by make(1), rather than by hand. Here are useful makefile rules if you only use GNU make: %.h: %.ui uic $< -o $@ %.cpp: %.ui uic -impl $*.h $< -o $@ If you want to write portably, you can use individual rules of the following form: NAME.h: NAME.ui uic $< -o $@ NAME.cpp: NAME.ui uic -impl $*.h $< -o $@ You must also remember to add NAME.cpp to your SOURCES (substitute your favorite name) variable and NAME.o to your OBJECTS variable. (While we prefer to name our C++ source files .cpp, the uic doesn't care, so you can use .C, .cc, .CC, .cxx or even .c++ if you prefer.) SEE ALSO
http://www.trolltech.com/ AUTHOR
Trolltech ASA <info@trolltech.com> Trolltech AS 2 Aug 2001 uic(1)
Man Page