Hi support,
I'm using the the components TSiLang for translation purpose.
I tried to get the resource strings from the EXE wich is build without RTL and dynamic libaries.
For example I got the string "Freitag" and translated also the string, but nothing changed if I switch between the languages.
Here I also add the sample file
https://supportcenter.devexpress.com/ti ... th-tsilang
Thanks
Thomas
DevExpress resource strings
Re: DevExpress resource strings
Hello,
The most possible that these strings are taken not from the resources but from the Locales. Try to translate locale strings in Locales section of TsiLang and don't forget to set ChangeLocales property to True:
The most possible that these strings are taken not from the resources but from the Locales. Try to translate locale strings in Locales section of TsiLang and don't forget to set ChangeLocales property to True:
Best regards,
Igor Siticov.
Igor Siticov.
-
- Posts: 20
- Joined: Tue Oct 05, 2021 1:52 pm
Re: DevExpress resource strings
Hi,
I have set the property but I don't have the Locales
Thanks
Thomas
I have set the property but I don't have the Locales
Thanks
Thomas
- Attachments
-
- SIComp.png (196.85 KiB) Viewed 4661 times
-
- Posts: 20
- Joined: Tue Oct 05, 2021 1:52 pm
Re: DevExpress resource strings
I have to delete the component TsiLang and add again.
Now I have the "Locales" but the strings still are not changing.
The wizard found the resource strings but the text will not be changed during runtime.
Now I have the "Locales" but the strings still are not changing.
The wizard found the resource strings but the text will not be changed during runtime.
Re: DevExpress resource strings
Hello,
You don't need to use the Resource Import Wizard in this case. Just enter the translations for the items in Locales section of TsiLang.
If this still won't work then this would mean that DevExpress controls initialize the UI strings once upon creation using the Locales and don't update them lately.
Maybe as a trick (workaround) would be to use the following at run-time:
1. Change the active language in TsiLang with translated Locales.
2. Re-create DevExpress controls.
To re-create controls it might be enough to save and then load them to the stream.
You don't need to use the Resource Import Wizard in this case. Just enter the translations for the items in Locales section of TsiLang.
If this still won't work then this would mean that DevExpress controls initialize the UI strings once upon creation using the Locales and don't update them lately.
Maybe as a trick (workaround) would be to use the following at run-time:
1. Change the active language in TsiLang with translated Locales.
2. Re-create DevExpress controls.
To re-create controls it might be enough to save and then load them to the stream.
Best regards,
Igor Siticov.
Igor Siticov.
-
- Posts: 20
- Joined: Tue Oct 05, 2021 1:52 pm
Re: DevExpress resource strings
Hi,
I tried it with the DEBUG version and this is working. The string are located in "Strings".
So something is different between DEBUG and RELEASE but I use in both versions NO dynamic link lib.
So I will chekc each option for both and then I should find the problem.
Thomas
I tried it with the DEBUG version and this is working. The string are located in "Strings".
So something is different between DEBUG and RELEASE but I use in both versions NO dynamic link lib.
So I will chekc each option for both and then I should find the problem.
Thomas
-
- Posts: 20
- Joined: Tue Oct 05, 2021 1:52 pm
Re: DevExpress resource strings
Hi,
the most parts are translated but DateNavigator from the component Scheduler is not transalated.
the most parts are translated but DateNavigator from the component Scheduler is not transalated.
- Attachments
-
- Bild_2024-12-19_202016284.png (22.01 KiB) Viewed 4588 times
-
- Posts: 20
- Joined: Tue Oct 05, 2021 1:52 pm
Re: DevExpress resource strings
Hi,
so everyting is working nearly fine.
1. The dialog property is not available for TSiLangLinked only for TSiLang
2. If I switch to "French" the Button for standard dialog with "Yes" and "No" is "Abort" and "Retry". I think it related to issue 1.
3. The resource String from DEBUG version can be used also for Release. But the Resource string from Release cannot be used
4. The resource string "Dezember" from the calendar is not a resource string it is shown due to the locale/region of the windows system
5. All other parts of the control Scheduler are changing the language after getting the focus (clicking with mouse)
Thomas
so everyting is working nearly fine.
1. The dialog property is not available for TSiLangLinked only for TSiLang
2. If I switch to "French" the Button for standard dialog with "Yes" and "No" is "Abort" and "Retry". I think it related to issue 1.
3. The resource String from DEBUG version can be used also for Release. But the Resource string from Release cannot be used
4. The resource string "Dezember" from the calendar is not a resource string it is shown due to the locale/region of the windows system
5. All other parts of the control Scheduler are changing the language after getting the focus (clicking with mouse)
Thomas
Re: DevExpress resource strings
Hello,
Just set CommonContainer property of TsiLangLinked to any TsiLang from the project and translate the Dialogs property of that TsiLang.1. The dialog property is not available for TSiLangLinked only for TSiLang
2. If I switch to "French" the Button for standard dialog with "Yes" and "No" is "Abort" and "Retry". I think it related to issue 1.
I don't know how DevExpress components use resource strings for display, sorry.3. The resource String from DEBUG version can be used also for Release. But the Resource string from Release cannot be used
Try to translate the Locales property in TsiLang, this might help with this one.4. The resource string "Dezember" from the calendar is not a resource string it is shown due to the locale/region of the windows system
Best regards,
Igor Siticov.
Igor Siticov.