Translation
- Fluency in English;
- Good understanding of ShareX settings so that during translation you know exactly what you are translating;
- How to use GitHub so you can pull/push translations;
- Good patience - because translation can take long time and can be boring. So it is better for you to not waste your time if you are going to give up in middle of translation.
Best way would be to contact us using web site contact form and after that using Hangouts (Google Talk) to contact further because probably you are going to have a lot of questions to ask when translating.
We are using ResX Resource Manager Visual Studio extension when translating to other languages:
https://visualstudiogallery.msdn.microsoft.com/3b64e04c-e8de-4b97-8358-06c73a97cc68
Standalone version of it also exist here:
https://resxresourcemanager.codeplex.com/releases (ClickOnce Installer)
Screenshot of it:
You just need to use this software/extension and set columns to your language.
When committing you must make sure only your language files are committed. For example, if you are translating to Turkish then the only ".tr.resx" files should be committed and not ".resx" because English translation file should never be changed.
"Properties\Resources.resx" files contains hard coded string translations which means these texts used in codes.
Some fields do not require translation:
They are marked as "Invariant" in software/extension which makes them gray. But sometimes when the form is edited in Visual Studio form designer, these "Invariant" marks can get removed automatically and there is no solution for it.
There can be situations where your translation text could stay behind or front another control (overlapped) most probably because while we were designing our UI we were not thinking about translation. We have tried our best to make majority of the UI friendly for dynamic text size but if in your language one text is say 4x bigger than English text then in some places problems can happen. In this case you can tell us that in messenger so we could try to change the UI to fit your translation or optionally you can try to find shorter translation because translation not need to be identical word to word as long as it is understandable. If we were to make UI from scratch then we would make UI more friendly for multi languages but it is too late now.
Note: This information is never required for translators but we have still included these in case you wondering how it works.
When you set "Localizable" property "True" in form then default (English) resx file will be automatically created for that form. All controls text, position, size etc. fields will be automatically created in this default resx file.
After that when we add new control to the form, its resx field is automatically created. When we also update text on any control its resx field automatically updates. Therefore, we don't need to add each controls translations manually. Position and size of control can also be updated in resx file e.g. one language can have bigger sized control than for another language to be able to fit properly; otherwise it would inherit default resx control size and positions.
We are using Resharper to be able to move hard coded strings to resources file with one click because it can't be automated.