Page 1 of 1

MLS/ITT: Language file upgrading logic

Posted: 26 Nov 2012 12:56
by Borut
In v11.70.0123 there appears to be an additional bit of intelligence when upgrading the language file, for cases where some original strings have changed between the MLS versions. This logic is - as far as I understand - necessary, since strings are internally being searched for in the .lng on the basis of their original English versions in program (or the Reference.lng).

Very nice!

I would just want to make sure my reaction on that was OK. I have done the following:
  • - Copy-pasted the strings listed into editor.
    - Searched manually (I have done it in ITT) for those of them, for which the translation already existed (as visible in the copied strings in the editor).
    - Recreated the translation of each such string (cut&paste the translation from the editor into ITT and applied).
Is this what was supposed to be done? (in my case one of the strings has been translated already.)

Thank you.
Borut

Re: MLS/ITT: Language file upgrading logic

Posted: 26 Nov 2012 14:48
by admin
Perfect! :)

These are cases where for different reasons the automatic upgrading does not work (but the human brain can manage), and cases where items were dropped from the interface (but I did not want to throw away your work without giving you the chance to save it).

Note that very likely I will further improve the upgrading logic in future. It is growing, and I'm growing into this new area of thinking. The goal is, of course, to make it as convenient as possible for the translators.