WorldServer - How do I turn off auto-translation?

In tm.properties, this property is set to true per default:

#enable_auto_translate=true

I don't want numbers to be automatically translated and auto-substituted, so I have set it to false:

enable_auto_translate=false

and restarted the Idiom and the File Type Server services. However, after segmentation of my file with a File Type, in Browser Workbench, numbers are still being auto translated:




How do I turn this feature off?

When using a File Type filter (for example, for Word documents in *docx format, the Microsoft Word 2007-2019 File Type) and the Studio scoping mode (which is set in the Project Type), the property enable_auto_translate is irrelevant and can be left to true without any impact. This property is only valid and relevant when using the WorldServer 9.x scoping mode and the old Legacy filters. Both these settings are not recommended: we recommend using the latest filters/file type and the Studio scoping mode for better integration with Trados Studio.

So if you are using a File Type and the Studio scoping mode, to avoid auto-substitution of numbers, these 2 properties are relevant and should be set to false:

studio_enable_recognize_numbers=false
studio_enable_auto_substitution_for_numbers=false

After changing these properties, restart WorldServer and create a new project. The numbers will be no longer auto-translated. The target segments will remain empty.

Other relevant properties for auto-substitution of dates, times and measurements can be disabled as well if required (they are enabled per default). In tm.properties, check the sections

### Studio Enabled/Disabled Recognizers
### Studio Enabled/Disabled Auto-Substitution Options

and set the relevant properties to true or false as required.

These articles are relevant:

WorldServer - which configurations control the Auto-translation?
WorldServer Translation Memory Modes - What are Studio-aligned and WorldServer 9.x TM scoping modes?
Difference between the WorldServer 9.x Scoping Configuration and the Studio-aligned Scoping Configuration