Sorry for my off-topic :) Generally, the translation process (going through .po files grabbed from git cloning and fixing missing/bad strings), is relatively simple. It's not a "Web 2.0" way but it is still made using nice and user-friendly tools (KBabel). I think the main problem is with synchronizing code with translations. Some strings are made "static" way (e.g. in TDE's hardware information dialogs) and they are not present in translation files. MCbx Dnia 17 lipca 2015 12:47 Michele Calgaro <michele.calgaro@yahoo.it> napisał(a): -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 07/17/2015 06:58 PM, iadest@o2.pl wrote: > There will be a release? What chance is for updated language files for translation upadting? MCbx R14.0.1 will be released as soon as ready. As already announced on the main website, the code base has been frozen and packages are now being built. For language translation updates, I will need to discuss with the other main developers. Before R14.0.0 was release, Tim did some work for that and we initially discussed how to "bring the translation process to the user", but then due to lack of time everything came to an halt. Cheers Michele
--------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting