Forum Discussion

Kristijan_Bratu_1's avatar
Kristijan_Bratu_1
Occasional Contributor
12 years ago

Testing application localized with Sisulizer

Hi,

we have application in our native languege compiled with debug infromation and there public, published, protected and private members of Delphi object are available.

Then we replace resources in executable with Sisulizer localization tool (http://www.sisulizer.com/online-help/OutputFiles.shtml). We localized texts only in resource strings and in *.dfm resources.

The size of application remained the same, which means that the debug information is included.

After localization Delphi object become inaccessible.

Did anyone have similar case?

Best regards,

Kristijan Bratuša

1 Reply

  • Kristijan_Bratu_1's avatar
    Kristijan_Bratu_1
    Occasional Contributor
    12 years ago
    Hi,

    The problem is that the Sisulizer tool changes the internal structure of the executable file and TestComplete cannot read debug info properly.

    Localization is not working on application compiled with internal debug information (TD32).

    For localization must be used external debug information (TDS files).

    Best regards,

    Kristijan Bratuša