There is a bug in the parser. Comments are sometimes not handled correctly. What happens: When the parser gets an '*' or '/', it takes the next token and checks if it is a '/' or a ')'. In the case of a double-slash the line is handled as a comment. In case of a '*)' the current comment ends. Despite the fact that the next token has been already got, it reads the next token again. That's why the token after a '*' or '/' is ignored.

Example:

{ This is a Comment / }

In the .dpr-file may cause a hang-up of Helicon-Translator.

The parser ignores the '}' after the '/', and runs into a loop.

Workaround:

Please avoid '/' or '*' at the end of the comment., e.g.

{ This is a Comment }

The format of binary dfm-files has slightly changed in Delphi 6. Helicon Translator 4 does not support this file-format, but there is an unsupported work-around:

The difference to the previous format is that Delphi 6 stores Ansi-String-Properties not longer as Ansi-Strings but as UTF-8-encoded Unicode strings in binary dfm-files. A workaround for this program is to store the forms as Text-DFM by enabeling of this option in Delphi. In order to do this, just right-click on the forms and enable the Text-DFM option in the context-menu.

The combo box "Type" in the "Custom Properties" contains duplicate entries.

Pressing of the "Remove" button in the custom properties dialog does not update the list of properties, but the property is removed anyway.

Update to version 4.03 or newer.

When the exchange file is importet and edited in Excel and then rewritten, Helicon Translator can not longer read the exchange file.

There are 3 reasons:

1) Helicon Translator inserts tabs at the end of all lines. This causes the "Header missing" error message

2) MS Excel strips quotes from the field by default. This can be switched of

3) If a field contains double quotes, the whole field data Excel re-encloses the whole field in quotes again.

Helicon Translator does not parse nested comments correctly:

Example:

uses
Unit1 in 'Unit1.pas' {Form1},
(*
AnotherUnit in 'AnotherUnit.pas' {AnotherForm};
*)
Unit2 in 'Unit2.pas',
Unit3 in 'Unit3.pas' {Form3},
Unit4 in 'Unit4.pas' {Form4};

In this case, Helicon Translator ignores the forms Form3 and Form4, because the ';' is not interpreted as part of a comment.

Sometimes, the compilation of a resource library fails with the following error message:

Linking resources
Error: ???????
Error creating library

This seems to happen under Win9x only.