SiComponents Forums

Hello Roberto, Yes, you can save/export all projects into one single SIB file but you have to be sure that ALL forms in all projects have different names, so every form has a unique name in order to have them all inside one SIB file. And then dispatcher and TsiLang components will be able to disting...

Hello, There is a global variable siLang_Def_UsedInCpp declared in siComp unit. You can assign it to True at application's initialization and C++ special chars like \n, \t and others will be treated accordingly. Additionally, every TsiLang component has a public field named UsedInCpp , you can set i...

Hello, If you use only Win32 as a target platform for your project then you can check the following FAQ entry: https://www.tsilang.com/tsilang-faq/#9 (just replace "AnsiString" in the code sample with "string" as this sample code was written in "non-Unicode" times). In case you need to support other...

Hello Roberto, Yes, in this case you need to export translations to external file, send it to translators and them load it back into DFMs. Saving and loading could be easily performed in TsiLang Expert. No need to send the DFMs. You can check the following links: 1. https://youtu.be/6R54hJ9FX14 - Ts...

Hello Roberto, 1 - Yes, although they will be updated at run-time once you assign dispatcher property. But in order to work properly it is recommended to configure languages in BPLs too. You can select all forms in BPL in Expert and configure them at the same time in a bulk. 2. "FileName" property o...

Hello, You can try to use only TsiLangLinked in packages and assign CommonContainer and Dispatcher properties upon package initialization. Something like the following: 1. In a package declare 2 global variables for holding reference to TsiLang and TsiLangDispatcher from the main application. 2. In ...

The Update Manager shall work now as well. Thank you again.

Hello,

Thank you for reporting this. Please download the standalone Dictionary Manager installer at: https://www.sicomponents.com/soft/Dicti ... _Setup.exe

Hi Malcolm,

Thank you for the info. But TsiColorDialog was never removed from components palette. It should be there as always.

5. We will try to implement this. Thank you!

Hello, TsiLangRT component is not applicable for FMX applications. Please use TsiLang instead. Only the following components available under FireMonkey applications: TsiLang, TsiLangLinked and TsiLangDispatcher. As other components are designed for specific tasks which are applicable only under Wind...

3. OK, will try to implement this.

These are changes to your sample that make it work (they are marked with // !!!! ): // !!!! move this here var SibFile: string; procedure TDM.DataModuleCreate(Sender: TObject); var FL: string; begin FL := Application.ExeName; SibFile := ChangeFileExt(FL, '.sib'); if FileExists(SibFile) then begin //...

Hello,

3. Is there any sense for this?

4. Right-click on TsiLang on the form and check "Ignore removals". Then TsiLang won't automatically delete data related to deleted components. Uncheck it again to re-activate.

But in this case your TsiLang on "Form1" won't be loaded from the file. So you may update your code a little: 1. In OnLinkToDispatcher event load ASiLang from Dispatcher's FileName 2. And then update the translation using ReplaceStringValue. Something like this: procedure TDM.siLangDispatcher1LinkTo...