2) and the other way round:
This is because the system picks up the error data from within the Dic selected for the Rep Lang.To avoid this, i.e. to keep a consistant Lang for these Log Msgs, I suggest to move/transfer the 28 <Error.../>, the 5 <Warning.../> and the 6 <Parameters.../> elements from the Dic(s) to the Genopro Lang pack(s).JC
The property ReportGenerator.SkinLanguage was designed for that purpose, allowing a script to make runtime decisions about the selected language.
ReportGenerator.SkinLanguage
ReportGenerator.BaseLanguage
Having reread the other post relating to this issue, it appears to me that text displayed whilst generating a report, such errors, warnings and comments must be stored separately to the text used in the report itself, as suggested by jcguasp. I now suggest that they be stored along with the config parameter descriptions, perhaps in a section GenerationMessages. Then GenoPro should localize these texts in a similar way to that proposed for configuration parameter descriptions and help tips. The report generator will require new method(s) to access these, or modify the existing Report.LogError/Warning/Comment. The message content can be either plain text or a Report Generator phrase with arguments, and so the method(s) need to cater for this.
GenerationMessages
Report.LogError/Warning/Comment