Hi there,
I just downloaded yesterday the latest version of TsiLang components. Great job you made.
But one problem I still have: We heavily use DevExpress components on our forms and they introduced in almost every of their components now STYLES.
Style for inactive, hottracked, active, selected items. Every visualization is managed by styles.
When we deal with different charsets and fonts, then - for instance - there is only one solution in TsiLang: Dealing with Extended Translations. This works but for a normal user (and translators are not programers) this is inconveniently or even not realizable.
Do you plan to handle those nested properties in future?
Or is there already a way to handle this - lets say: Not for each single component (like in Extended Translation) but for all subcomponents called "Defaultstyle.Font.charset" or "Defaultstyle.Font.Name"?
A small bug I found in the D5-Version of TsiLang: DoNotTranslate, Excludedproperties at designtime produces exception: Designsize of panel1 not declared. But this I can change myself.
The biggest headage we have with fontnames and charsets in nested components like Devex's because we want to give away the basic sib-files to external translators.
Thanks in advance for every idea which may help,
Karl