Description
Translatoin files in here: barrier/src/gui/res/lang/
- Translate your language translation file
.ts
. - For translation, use the "Qt linguist" tool.
- Compile this
.ts
into.qs
: Qt linguist'sMenu
-File
-Release
- Pull request new
.ts
and.qs
to GitHub.
The latest string may not be reflected. String changes detected from barrier/src/gui/src 's history. Strings are enclosed in tr("")
or <string></string>
.
e.g. In 24b6e4b, The Fingerprint dialog' string has split for 2.4.0. Therefore, each translated file that does not reflect this update will have the Fingerprint dialog in English. This change was made the day before the 2.4.0 release and no one has updated the translation. If there are new changes , please let us know via this issue.
Here is a near-perfect file for2.4.1. #1854 (It's manual, so there may be mistakes.) Reflect the changes in your language file by text editor.
For developers
If only a code change is made (below 1. ), it could remain in place for years, reverted to English.
Correct change procedures
- Change the source code.
- At least reflect it in barrier/src/gui/gui.ts
:gui.ts
is just a collection of English strings. Any changes to this file will help the translators recognize the need for an update.
: The program does not refer tofilename
andline
in the location tag. This is seen by humans. And line numbers change frequently, so approximate is fine. Once added, leave the line numbers as they are. Otherwise, you will not be able to check the differences with each translation file.
: Or, please let us know via this issue. - Reflect the changes in all
.ts
on barrier/src/gui/res/lang/ and compile to.qs
.
All of the projects I know of are either 2 orProceed to 3. It would be nice to have someone in charge of doing 3.