Mercury13

@coolvitto Orig = original. Tran = translation. 1. It keeps track of what original you translated. Example: if I do grammar check, what I’m doing now, I’ll be able to...

UTranslator 0.4 with “Mark as bad” released. You use 100% and HiDPI is not for you, but I replaced pixel images with SVG. 0.3.7 with “Translate with *.uorig” was released...

No, you should create using File/New (or take from my repo, I already created) ja.UTRAN.

Of course, it’ll be a translation, but… empty (0 translated of almost 2000), and you should port your work using “Translate → Another *.uorig”. (I did not change original since...

Just edit ja.utran and give it to me with any means possible (pull request, archive etc). To preserve the work you’ve already done, you may need this  Select your...

I invented this approach to L10n for myself, but it proved the best for translating a living program that’s released frequently. First in a commercial program, then recreated an open-source...

The common approach is Gettext, and it’s suitable for living program, and cool for unofficial translations, but suitable for short strings only.

What is general operation? Even partial translation is nice. 180k characters (I counted one day) are not a cakewalk.

Then go to project settings and turn off pseudo-localization, as there will be untranslated strings and you are not going to touch them.   At least translate short strings.

Need to think more about this feature. If you need to see it somehow, what will you do?