This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Feature Transfer Error in Korean
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 02, 2012
11:23 AM
Feature Transfer Error in Korean
The IS feature transfer error message in Korean is truncated. Can this be fixed?
See attachment.
See attachment.
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 02, 2012
12:54 PM
I'm having trouble finding this string; is it one we provide? Or is it possible it's related to the Unicode updates for IS2011—have you checked all function prototypes for proper use of STRING and WSTRING?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 02, 2012
03:50 PM
I don't know anything about Unicode updates for IS 2011.
I don't know which function prototypes you are referring to. I don't use any custom InstallShield script.
I don't know which function prototypes you are referring to. I don't use any custom InstallShield script.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 02, 2012
06:32 PM
This issue will occur with any Asian language or any languages not using the standard ASCII character subset. The cause of this behavior is related to how the feature transfer error object is built for InstallScript MSI projects. In this case, it is actually just a structure defined in internal script code that contains error information (as opposed to pure InstallScript projects which use a normal COM interface). The string members of these structures are still declared as ANSI strings. As a result, storing any non-standard ASCII based characters in these string members will either result in the strings becoming corrupted or possibly truncated (due to incorrect size calculations).
I've submitted work order IOA-000069733 to address this issue in a future release. As a workaround, you can override the OnComponentError function in your script to display alternate error strings instead of ones obtained from the ErrorInfo object/structure (see OnComponentError for how errors are normally displayed).
I've submitted work order IOA-000069733 to address this issue in a future release. As a workaround, you can override the OnComponentError function in your script to display alternate error strings instead of ones obtained from the ErrorInfo object/structure (see OnComponentError for how errors are normally displayed).