Lokalize: Difference between revisions

    From KDE UserBase Wiki
    No edit summary
    (Marked this version for translation)
     
    (35 intermediate revisions by 14 users not shown)
    Line 1: Line 1:
    {{Template:I18n/Language Navigation Bar|Lokalize}}
    <languages />
    {|
     
    |[[Image:Lokalize.png|128px|left|Lokalize]]||    ||'''Lokalize is the localization tool for KDE 4'''
    {|class="tablecenter vertical-centered"
    |[[Image:Lokalize.png|128px|left|Lokalize]]||    ||<translate><!--T:1-->
    '''Lokalize is the localization tool for KDE and other open source software'''</translate>
    |}
    |}
    <translate>


    Lokalize is a replacement for KBabel which is now discontinued.
    <!--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.


    <!--T:3-->
    __TOC__
    __TOC__


    <!--T:4-->
    [[Image:Lokalize-scr-1.png|thumb|500px|center|Lokalize with French translation of Konqueror]]
    [[Image:Lokalize-scr-1.png|thumb|500px|center|Lokalize with French translation of Konqueror]]


    Some more info on Lokalize can be found on the Lokalize summer of code page: http://techbase.kde.org/Projects/Summer_of_Code/2007/Projects/KAider




    ==Lokalize under Windows==
    ==Compiling Lokalize from KDE trunk== <!--T:12-->
    Install KDE using kdewin-installer:
    http://www.winkde.org/pub/kde/ports/win32/installer/kdewin-installer-gui-latest.exe
    Leave defaults in all steps except package list.
    In package list select kdesdk (all dependencies will be installed automatically). Complete kdewin-installation process.


    ::''Here was a link to lokalize052009.exe, that replace a vanilla Lokalize with the latest Lokalize version from trunk. This link is now broken :-(''
    <!--T:13-->
    Install '''libkf5i18n-dev''',  '''libkf5completion-dev''', '''libkf5itemviews-dev''', '''libkf5sonnet-dev''', '''kross-dev''' headers packages and '''libhunspell-dev'''. Then:


    Technical details: you install KDE 4.2 in standard way,
    <!--T:14-->
    and then add custom-compiled Lokalize binaries and data
    {{Input|1= git clone <nowiki>git://anongit.kde.org/lokalize</nowiki>}}or
    (to-be 4.3).


     
    <!--T:15-->
    ==Compiling Lokalize from KDE trunk==
    {{Input|1=git clone <nowiki>git@git.kde.org:lokalize</nowiki>}}
    Install kdelibs headers package (for example in Debian it's kdelibs5-dev). Then:
    and
    svn checkout --depth=files svn://anonsvn.kde.org/home/kde/trunk/KDE/kdesdk/
    {{Input|1=cd lokalize
    cd kdesdk && svn up cmake doc lokalize
      mkdir build
      mkdir build
      cd build
      cd build
    mkdir $HOME/kde43
      cmake -DCMAKE_BUILD_TYPE=RelWithDebInfo ..
      cmake .. -DCMAKE_INSTALL_PREFIX=$HOME/kde43 -CMAKE_BUILD_TYPE=RelWithDebInfo
      make -j2
      make -j2
      make install
      ./src/lokalize
    }}
     
    <!--T:24-->
    ==Downloading Lokalize binaries for Windows==
    The latest release build of Lokalize for Windows is available as a build artifact in the Windows Qt5.15 project, under [sidebar] > Deploy > Package registry, at https://invent.kde.org/teams/ci-artifacts/windows-qt5.15/-/packages ; search for "Lokalize" and choose a "release" build.
     
    <!--T:25-->
    The latest nightly build of Lokalize for Windows is also available at the same place; search for "Lokalize" and choose a "master" build.


    Then run lokalize via $HOME/kde43/bin/lokalize
    ==Tips and tricks== <!--T:17-->


    === Search in files === <!--T:18-->


    ==Tips and tricks==
    <!--T:19-->
    === Search in files ===
    Translation Memory (TM) now keeps track of where each translation pair came from. So when you want to <menuchoice>search</menuchoice> for string in the files on disk, you just drag the directory with those files onto <menuchoice>translation memory</menuchoice>  tab (<keycap>F7</keycap>) to update TM, wait a minute or two, then type your string into right field of <menuchoice>Translation Memory tab</menuchoice>, then press <keycap>Enter</keycap>.
    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 appropriate entry. When you want to do another search during the same day, you skip 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).
    <!--T:20-->
    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 <keycap>F7</keycap> panel (<menuchoice>Filemask</menuchoice>).




    <!--T:21-->
    == Author ==
    == Author ==
    Nick Shaforostoff <shaforostoff AT kde.ru>
    Nick Shaforostoff [http://www.facebook.com/shaforostoff Facebook page]
       
       
    == External links ==
    == External links ==
    <!--T:22-->
    * [http://docs.kde.org/development/en/kdesdk/lokalize/index.html Handbook]
    * [http://docs.kde.org/development/en/kdesdk/lokalize/index.html Handbook]
    * [http://lokalize.program.net.ua/lokalize-first.htm Screencast: Lokalize intro tutorial for KDE translators (open project, fill translation memory, widget text capture, approval status)]
    * [http://api.kde.org/4.14-api/kdesdk-apidocs/lokalize/html/annotated.html KDE SC 5 API Reference]
    * [http://lokalize.program.net.ua/lokalize-glossary.htm Screencast: using glossary in Lokalize]
    * [https://bugs.kde.org/enter_bug.cgi?product=lokalize&format=guided Report a bug]
    * [http://lokalize.program.net.ua/ All the screencast made for Lokalize]
     
    * [http://api.kde.org/4.x-api/kdesdk-apidocs/lokalize/html/index.html KDE 4 API Reference]
    <!--T:23-->
    [[Category:Development]]
    </translate>

    Latest revision as of 08:19, 29 February 2024

    Lokalize
    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


    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

    Downloading Lokalize binaries for Windows

    The latest release build of Lokalize for Windows is available as a build artifact in the Windows Qt5.15 project, under [sidebar] > Deploy > Package registry, at https://invent.kde.org/teams/ci-artifacts/windows-qt5.15/-/packages ; search for "Lokalize" and choose a "release" build.

    The latest nightly build of Lokalize for Windows is also available at the same place; search for "Lokalize" and choose a "master" build.

    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