Translations of LXQt
CMake Shell
Permalink
Failed to load latest commit information.
compton-conf Updated Ukrainian translation Jan 15, 2017
libfm-qt Updated Ukrainian translation Jan 15, 2017
liblxqt liblxqt_tr.ts update Dec 19, 2016
lximage-qt Add/update Turkish translations Dec 28, 2016
lxqt-about Add/update Turkish translations Dec 28, 2016
lxqt-admin Update Turkish translations Jan 2, 2017
lxqt-config Add/update Turkish translations Dec 28, 2016
lxqt-globalkeys Updated Ukrainian translation Jan 15, 2017
lxqt-notificationd Add/update Turkish translations Dec 28, 2016
lxqt-openssh-askpass Add/update Turkish translations Dec 28, 2016
lxqt-panel Add/update Turkish translations Dec 28, 2016
lxqt-policykit Updated Ukrainian translation Jan 15, 2017
lxqt-powermanagement Add/update Turkish translations Dec 28, 2016
lxqt-runner Add/update Turkish translations Dec 28, 2016
lxqt-session Add/update Turkish translations Dec 28, 2016
lxqt-sudo Add/update Turkish translations Dec 28, 2016
obconf-qt Add/update Turkish translations Dec 28, 2016
pavucontrol-qt Update Danish translations Dec 14, 2016
pcmanfm-qt Updated Ukrainian translation Jan 15, 2017
qterminal Update Turkish translations Jan 2, 2017
.travis.yml travis: Do not require more than needed Oct 26, 2016
AUTHORS Bump year Jan 2, 2017
CHANGELOG Release 0.11.2: Update changelog Jan 1, 2017
CMakeLists.txt Use LXQtConfigVars CMake module Oct 26, 2016
COPYING AUTHORS and COPYING added (#7) May 13, 2016
README.md Update README.md Sep 7, 2016
check_ts.sh build: Add automated testing Oct 12, 2016

README.md

lxqt-l10n

Overview

This repository is providing translations ("localization") in terms of the Qt TS files of all components maintained by the LXQt project.

The transfer from the components' distinct repositories to this single one was made in order to ease handling the translations by systems like Pootle or Transifex which is the long-term goal.

Desktop Entry files (*.desktop) remain in the distinct components' repositories for the time being as these are not yet covered by Pootle or Transifex anyway.

There are two ways to make use of the translations summarized in this repository.
Components can pull their translations from this repository at build time. This is what all components covered by this repository are doing by default right now.
The repository can be built independently of the other components. This allows for building the translations without downloading at build time which in turn can mitigate restrictions of build systems. Building the repository that way can be favourable regarding performance as well as the repository itself is architecture agnostic so translations have to be built once only instead of one time per component and architecture. The repository can be built as a whole, splitting into several packages is possible as well.

Compiling

General

Git, CMake, qttools and LXQt component liblxqt as well as its dependency libqtxdg are needed to build translations from this repository, no matter whether components are pulling from this repository or the repository is built itself.

Pulling translations at build time

With regards to downstream packaging it's worth noting that the prerequisites stated above may have to be added to packages providing components like ComptonConf which don't need them at runtime and hence eventually didn't need them at all so far.

All components are by default pulling their translations at build time right now. This can be toggled by a boolean CMake variable PULL_TRANSLATIONS.

Building the repository itself

A selection which components shall be considered can be made by a boolean CMake variable WITH_<component>, e. g. WITH_LXQT_PANEL. It defaults to ON for all components included in this repository. CMake variable PULL_TRANSLATIONS as stated above has to be set to OFF in all components which are meant to be covered by repository lxqt-l10n as file conflicts will result otherwise.

To build run trias cmake, make and make install as usual. Make target install accepts a variable DESTDIR=<path>.

Contributing

As tools like Pootle or Transifex haven't been implemented yet we have to ask users to take a not too convenient approach which involves dealing with local source code checkouts.
It is depicted in wiki page Translation.