Difference between revisions of "Lokalize"

(update for kf5)
Line 6: Line 6:
 
|}
 
|}
 
<translate>
 
<translate>
 +
 
<!--T:2-->
 
<!--T:2-->
 
Lokalize is also a general computer-aided translation system (CAT) with which you can translate OpenDocument files (*.odt). [https://translate-toolkit.readthedocs.org Translate-Toolkit] is used internally to extract text for translation from .odt to .xliff files and to merge translation back into .odt file.
 
Lokalize is also a general computer-aided translation system (CAT) with which you can translate OpenDocument files (*.odt). [https://translate-toolkit.readthedocs.org Translate-Toolkit] is used internally to extract text for translation from .odt to .xliff files and to merge translation back into .odt file.
Line 17: Line 18:
  
  
==Lokalize under Windows== <!--T:6-->
+
==Lokalize under Windows and OS X== <!--T:6-->
  
 
<!--T:7-->
 
<!--T:7-->
Install KDE using '''kdewin-installer''':
+
There is a stripped-down Qt-only version of Lokalize which are self-contained, i.e. they do not need KDE installed to run:
  
 
<!--T:8-->
 
<!--T:8-->
{{Input|1=http://www.winkde.org/pub/kde/ports/win32/installer/kdewin-installer-gui-latest.exe}}
+
:* [http://nekaka.com/d/xCuuVv7jlA win32]
 
 
  
 
<!--T:9-->
 
<!--T:9-->
Leave defaults in all steps except package list.
+
It lacks project management, spellcheck, scripting, and to translate OpenDocument you will need to install and run Translate-Toolkit yourself. If you have interest in Lokalize on non-free platforms, please let me know through reporting issues on bugs.kde.org.
In package list select <menuchoice>kdesdk</menuchoice> (all dependencies will be installed automatically). Complete '''kdewin-installation''' process.
 
 
 
<!--T:11-->
 
Technical details: you install KDE 4.3 or later in standard way,
 
and then add custom-compiled '''Lokalize''' binaries and data.
 
 
 
  
 
==Compiling Lokalize from KDE trunk== <!--T:12-->
 
==Compiling Lokalize from KDE trunk== <!--T:12-->
Line 73: Line 67:
 
:* [http://docs.kde.org/development/en/kdesdk/lokalize/index.html Handbook]
 
:* [http://docs.kde.org/development/en/kdesdk/lokalize/index.html Handbook]
 
:* [http://api.kde.org/4.14-api/kdesdk-apidocs/lokalize/html/annotated.html KDE SC 5 API Reference]
 
:* [http://api.kde.org/4.14-api/kdesdk-apidocs/lokalize/html/annotated.html KDE SC 5 API Reference]
 +
:* [https://bugs.kde.org/enter_bug.cgi?product=lokalize&format=guided Report a bug]
  
 
<!--T:23-->
 
<!--T:23-->
 
[[Category:Development]]
 
[[Category:Development]]
 
</translate>
 
</translate>

Revision as of 00:07, 30 January 2015

Other languages:
Deutsch (Sie-Form)‎ • ‎English • ‎Türkçe • ‎dansk • ‎français • ‎galego • ‎italiano • ‎português do Brasil • ‎čeština • ‎русский • ‎українська • ‎中文(中国大陆)‎ • ‎中文(台灣)‎
Lokalize
Lokalize is the localization tool for KDE and other open source software

Lokalize is also a general computer-aided translation system (CAT) with which you can translate OpenDocument files (*.odt). Translate-Toolkit is used internally to extract text for translation from .odt to .xliff files and to merge translation back into .odt file.

Lokalize with French translation of Konqueror


Lokalize under Windows and OS X

There is a stripped-down Qt-only version of Lokalize which are self-contained, i.e. they do not need KDE installed to run:

It lacks project management, spellcheck, scripting, and to translate OpenDocument you will need to install and run Translate-Toolkit yourself. If you have interest in Lokalize on non-free platforms, please let me know through reporting issues on bugs.kde.org.

Compiling Lokalize from KDE trunk

Install libkf5i18n-dev, libkf5completion-dev, libkf5itemviews-dev, libkf5sonnet-dev, kross-dev headers packages and libhunspell-dev. Then:

git clone git://anongit.kde.org/lokalize

or

git clone [email protected]:lokalize

and

cd lokalize
 mkdir build
 cd build
 cmake -DCMAKE_BUILD_TYPE=RelWithDebInfo ..
 make -j2
 ./src/lokalize

Tips and tricks

Search in files

Translation Memory (TM) now keeps track of where each translation pair came from. So when you want to search for string in the files on disk, you just drag the directory with those files onto translation memory tab (F7) to update TM, wait a minute or two, then type your string into right field of Translation Memory tab, then press Enter.

Then you click on one of results and this opens appropriate file, on the appropriate entry. When you want to do another search during the same day, you skip the updating step and just type what you're searching for. You can filter TM search results by filename using the field left side of the F7 panel (Filemask).


Author

Nick Shaforostoff Facebook page

External links


Content is available under Creative Commons License SA 4.0 unless otherwise noted.