GenoProSupport (12-Oct-2011)I agree. The language should work like GenoPro translation, where there is a default dictionary, and the user may add extra dictionaries.Perhaps in Config.xml, a node named <Dictionaries> could be added<Skin Name="English Narrative Report" Language="EN"> <Dictionaries> <Dic Language="FR" File="DictionaryFrench.xml" /> <Dic Language="IT" File="IT.xml" /> </Dictionaries> ...</Skin>The other solution is having GenoPro search for any file matching the wildcard Dictionary*.xml. In this scenario, a dictionary would be as easy as adding a file such as DictionaryFR.xml and the last two letters would indicate the language of the dictionary. This would add a restriction on the naming of the xml files (for instance, one could not name a dictionary as MyCustomDictionary.xml") however would make it simpler for development.When listing all the skins, GenoPro would list also the available languages, where the default dictionary is always Dictionary.xml (this way, if someone does a partial translation of a language, there is always value available in Dictionary.xml)I like the idea of having several DictionaryXX.xml files in the skin. I think I have suggested this in the past.However there is also a need for multiple Config.xml files as well. GenoPro should attempt to locate a ConfigXX.xml file, wheere XX is the language code the user is using for GenoPro itself. e.g. ConfigFR.xml. If that file is not found then the default Config.xml should be used. Genopro should merge the ConfigXX.xml and Config.xml files by replacing tags in Config.xml where there is a matching tag in ConfigXX.xml. The DictionaryXX.xml and Dictionary.xml should be merged in a similar way. 'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn" Edited: Thursday, October 13, 2011 by genome
<Dictionaries>