SiComponents Forums

To exclude mutliple components you can use DoNotTranslate property and its editor which allows to exclude multi-selected components.

This looks like you haven't recompiled all files well when upgrading to new version. Be sure to delete all DCU, OBJ files from old version before instaling newer one.

Please use only correct and polite words when posting in forum.
Thanks.

When excluding only particular property of component, this property of this component will be added to SmartExcludeProperties property and won't be listed in translations. When ou select "Do not translate all properties" of component, this component will be added to DoNotTranslate property...

In order to have active language set before running the application you will need to set ActivaLanguage property to needed value at design-time and build your project. But then you will have 2 EXEs.

This is strange why something with loading doesn't work for you. Could you please create sample project which reproduces the wrong behavior and send it to us? Then we would try to investigate where the origin of problem is. You may try to save/load to/from SIB files using SaveAllToBinaryFile/LoadAll...

Do you need a separate SIL file for each form? Or one SIL file for all forms from project? You can save all forms into one SIL file and they will "rertieve" only needed info when loading from SIL file. In case you don't need to allow end-user to change translations at run-time I would reco...

It looks like your SIL file is incorrect or doesn't contain all needed information. 1. To create SIL/SIB file from your project I would recommend to use TsiLang Expert and File|Save/Load... menu 2. To load SIL/SIB file at run-time just either set FileName property of TsiLangDispatcher or set Storage...

Thanks for reporting this.
Please use Update Manager to download updated version which includes this fixed.
Thanks again.

This looks like the forms which have problems with translating are created later than SIB file loaded. In order to load SIB file for all forms even for run-time created you should: 1. Either set FileName property of TsiLangDispatcher to your SIB file name. 2. Or use OnLinkToDispatcher event to load ...

The requested demo is available at:
http://www.sicomponents.com/soft/TaskSc ... unDemo.zip

TsiLang components have SaveToStream/LoadFromStream methods which could be used to save loas translations to/from database. And as far I know several customers have used this capabilities to use database as translations storage.

1) sometimes even though SilEditors default font for Korean is Hanguel you need to set CharSet to Hanguel for each module in this section. You then get ??(questionmarks) when getting the translations from the dictionary. Yes, SIL Editor uses the Font/Charset info from file first if this is availabl...

Checked and this works fine too for us. Are you sure you have specified the correct Charset (Hanguel) for Korean language? What OS do you use?

Checking...
Btw, you may use not Suggest Translation but Get Translation and then it for sure should work correct.