#729 Word document properties incorrectly handled.

[Guido Leenders]

In Microsoft Word documents you can use Document Properties. These document properties are defined in the File menu and have a value for the whole document where you can insert it as a reference. When you change the value of a property, you just need to press ctrl+a and F9 to update all uses to the new value in the current block (body / headers / footers).

However, when you translate such a document with OmegaT, it will always include the referred document property in the document as a translateable text with some tags. However, the value is not actually in the document. Press ctrl+a and F9 changes it back to the untranslated value. You can not translate yet the document property values; they are not shown as segment.

It is more correct to:

a. Replace the referred document property with the surrounding <tags> by one big tag.
b. Allow the user to translate the document property values.

See attached sample.

[Guido Leenders]

In picture, the blue is text before and after the document property. The yellow shows the complex field characters included and the propertyname is green.

[Guido Leenders]

The document properties can be found for translation in custom.xml, for example:

<property fmtid="{D5CDD505-2E9C-101B-9397-08002B2CF9AE}" pid="6" name="InvantiveLicentieAantalProjectLeiders"><vt:lpwstr>onbeperkt</vt:lpwstr>

The name can remain, the text between <vt:lpwstr> is translateable. Please note that there are also integers, dates, etc as values, but I do not think they need to be translateable.

[Didier Briel]

As it is now possible to translate Word document properties (see [#828]), I close.

Didier