Checking string format

The earlier versions of Radialix supported checking validity of format specifiers used by the functions printf, FormatMessage and .NET String.Format. The translation validity check parameters had individual options for each of these formats.

The format type was tightly bound to the resource type. The printf format was used for strings in the resources RT_STRING, RT_RCDATA, RT_DLGINIT, ~HARDCODED, etc., FormatMessage – for strings in the resources RT_MESSAGETABLE, and String.Format – for any strings in .NET applications. Printf was the only format used when checking validity of translation memory.

In version 2.08, the validation of format specifiers has been fully revised. Now, there is only one option used in the translation validity check parameters; that’s Inconsistent format specifiers.

The string format type is now defined by the StringFormat property, which is available for all strings, and also resources, resource types, files and translation memory.

The Format column is added to the strings spreadsheet and the translation memory editor. The column displays current string format. The editing of format is available from the context menu of the strings spreadsheets – via the Edit>String Format … item. The respective button can be placed on the editor toolbar as well. This dialog can also be opened by double-clicking on a cell in the Format column.

The String Format option was added to the parameters of the strings spreadsheet and translation memory filter.

In version 2.08, the list of supported string formats has been expanded essentially – now 25 different formats are supported.

The StringFormat property has three special states:

- (dash)  - indicates that the string does not contain format specifiers; specifier validity check is not performed for the string.

<Parent> - string format is taken from the owner’s StringFormat property; for strings – from resource or translation memory file, for resource – from resource type, for resource type – from file, and for file – the default value from the parser.

<Default> - uses the format predefined for the respective file and resource type.

Customizing columns in translation memory editor

In version 2.08, we have added customizing the position and composition of columns of the spreadsheet. It is done the same way as in the string editor spreadsheet – using the commands from the contents menu of the spreadsheet header.

Two new columns– Comment and Format – have been added to the translation memory spreadsheet.

Removing all comments

In version 2.08, the Project>Remove Comments item has been added to the main menu. The command removes all comments from a project. Comments in linked translation memory files are not removed by this command.

“Clear” button in comment editing dialog

The Clear button has been added to the comment editing dialog; it removes all text in the entry field.