SiComponents Forums

Resource Builder is able to operate with EXE files built with PE-header (WIN32 executables). Unfortunatelly 16bit executables (with NE header) are not supported.

No, this is not possible to automatically translate form wihout TsiLang component on it. The only way to fo this is the way you've used, using GetText() or GetTextOrDefault() methods to retrieve strings and assign them to UI elements of such form.

We hope one day this happen but we can't provide you now with any deatils.

Are you sure using latest version of TsiLang Components Suite?

This is pretty well described in help and User's Guide. Just check the "Translating CONST section topic" and FAQ entry:
http://www.sicomponents.com/lng_faq.html#2

Since TsiLang Components Suite VCL edition is ANSI based you should set Japanese as default language in your OS in order to have it supported in TsiLang Translation Editor.

This was a bug and it was fixed in current sources. Please re-download the install package from our site and install it. Sorry for this.

Yes, there is bug. We will fix it for next release. Thanks.

Hello,
It looks like not ALL files were correctly re-compiled. Just try to delete all DCU, OBJ, HPP files from TsiLang\Units folder and re-build the TsiLang package.

We're unable to reproduce mentioned bahavior. Could you please give us more details? May be you notice that empty Popup menus are deleted when closing the editor? If yes then this is correct behavior and the warning is showing there.

This looks like your SIL file doesn't conatin information about ExtendedTranslations property. In order to include it there you can at Design-time save all to SIL file using TsiLang Expert and this will save all translations and extended as well. After that after loading this SIL file at run-time yo...

I hope it will be released in next days.

There is bug and this should work "silently" we will include fix for this in next update release.

Again glad to see this. Morning is always better than night

Glad to see this.