Hacking:Localization: Difference between revisions
Changing valentina to seamly / seamly2D
(Added section Common mistakes.) |
Ronanletiec (talk | contribs) (Changing valentina to seamly / seamly2D) |
||
(21 intermediate revisions by 2 users not shown) | |||
Line 1:
<languages />
<translate>
<!--T:1-->
This file contains some important hints for translators.
<!--T:2-->
The current status of the
<!--T:3-->
Translation of
<!--T:4-->
We recommend this short video with [https://www.youtube.com/watch?v=zw677Bp1En8 Transifex Translation Editor Tutorial].
<!--T:5-->
The more progress we make the more complex
== Add new language == <!--T:6-->
== Several source files ==▼
If you don't see your language already in the list you can create a language request. But be sure that your request contains not only language code, but also country code. Example of correct codes: en_US, en_CA, en_IN, ru_RU, de_DE. Wrong requests: nl, uk, ja etc. Wrong requests will be rejected.
Note. If your language doesn't have a country code on Trainsifex you can use single language code.
<!--T:15-->
After translation 10-20% of valentina.ts strings you have right to ask us include translation to Seamly2D distribution. Feel free to push us or [[Hacking:Making pull requests|make a pull request]] yourself if we missed this fact.
▲== Several source files == <!--T:7-->
At the same time transifex can have several source files that represent different branches of code. Source file without number "valentina.ts" represent last unstable changes in code. This file unstable and can be changed many times before the release. Translations from this source you will find in each unstable installer we provide.
<!--T:8-->
From the other side source file "
<!--T:9-->
Which source file prefer to take? Main goal is to translate all strings. So we recommend begin work with "stable" source file and then update "unstable" just by uploading them like unstable on Transifex. Most time they have more than 90% similar strings. System yourself clean all "old"
== Internationalizing
You should remember several aspects when you translate
<!--T:11-->
* Do not translate strings that you don't understand!!
*
* If you don't know how correctly translate measurements you can begin with file measurements_p998_*.ts. It contains Seamly2D's internal standard that should be translated literally.
* Some text
* Translate only text.
== Fixing typos == <!--T:17-->
== Applying translation ==▼
From time to time you may find typos in source strings. You can help us eliminate them too. All you need is to edit appropriate translation for language '''English (United States)'''. After next synchronization test will show us your fix and appropriate string in source code will be fixed.
You do not need to do anything. One of developers will download all changes and apply it.▼
▲== Applying translation == <!--T:12-->
▲
<!--T:13-->
But in case you build the project from source code you need to do additional moves.
* Check if after you last edit localization someone applied it. Try to find commit with comment "'''Lupdate'''" in appropriate branch. Usually develop or release. Don't forget compare dates.
* Update to a branch head.
* Call '''Clean All'''.
* Call '''Run qmake'''.
* Call '''Build All'''.
<!--T:16-->
In case you want speed up update you have two options:
* Ask us to update localization (recommended for newbies).
* [[Hacking:Making pull requests|Make a pull request]]. Before making a pull request we recommend run '''TranslationTest''' binary and test current changes. There are a lot common mistakes that tests cover and help to fix.
== Common mistakes == <!--T:14-->
* Space letter inside measurement name.
* Missed place holder i.e. %1, %2 ... %99. For example instead of '''%1''' a string has '''
* A last special character (<code>.</code>, <code>:</code>, <code> </code>, <code>\n</code>, <code>!</code>, <code>?</code>, <code>;</code>) in translated and original string does not match.
</translate>
|