The latest beta now has a set of redesigned dialogs that should hopefully make translation a lot easier.
All controls have been sized/positioned to allow much longer text without the need for the translator to resize/reposition dialogs/controls.
The only exceptions are button sizes, which are all now a standard 50x14. However, many of the buttons have been positioned in a way that allows them to be widened with no changes to layout. On my to-do list: implement a method that, for each dialog, will determine the needed button size based on the button text and will resize/shift buttons/button groups and resize dialogs as necessary.
Regarding translations:
I mentioned in the previous beta release that I had joined Crowdin to experiment with translations/resources. Looking at the amount of text that needs to be translated, this is going to take a lot of time and work for each language. I am wondering whether the best approach might be to get the resources professionally translated as a first step, eg. by Alconost, for a base set of EFIGS language support, and users can then provide feedback and updates to the translations over time. My main concern is that much of the text is mIRC/IRC/Scripting-specific and a translator would need to be aware of context and terminology, especially since there are so many context-less short strings. These translations can then be included in the release and would need to be updated before each release. In any case, something to think about.
