Setting up the Pre-translation feature

Once the pre-translation tab is enabled, you will need to properly set up the pre-translation with your workflow.

To set up the pre-translation feature, perform the following:

Select the Project Workflow tab from the project summary page.
From the Pre-translation Notification list box, select the team or person who will be notified when a document is uploaded to pre-translation, and then click Save.

Note: The team or person selected will automatically be notified every time a document is uploaded into pre-translation.

Select the Settings tab.
Under the Document Options section, select the file types that you want to require pre-translation, and then click Save.

You can select one of the following options:
- Don’t allow – disable pre-translation for all files
- Any file – files that cannot go through the regular workflow or cannot go through an importer are sent to pre-translation
- Specific files – only the specified file types are sent to pre-translation

Note: You can specify multiple file types.

The following file types are supported by the importer:

odg	md	xml	xls	cpp	txml
strings	docx	tmx	icml	ditamap	doc
regex	sdlxlf	srt	mif	vsdx	dita
pptx	properties	html	rtf	idml	ts
csv	pdf	indd	json	ttx	odt
ods	ppt	txt	rdf	yml	resx
zip	odp	tsv	catkeys	xlf2	xlsx
wix	po	lang	xlf	dtd

Note: When a specific file that is accepted by the importer is chosen, you can force the file to go into the pre-translation queue.

For example:

PO files are automatically sent to the importer, however, if a PO file is specified in the "Specific files" option, then it will go to pre-translation for that project instead.

The following file types are restricted by the importer:

ade	cab	ex	lib	pif	vbe
adp	cgi	exe	lnk	ps1	vbs
air	chm	ex_	mde	rpm	vxd
apk	cmd	flatpak	msc	scr	war
app	com	hta	msi	sct	wsc
appimage	cpl	ins	msix	shb	wsf
appx	deb	ipa	msixbundle	snap	wsh
appxbundle	dll	iso	msp	sys
bat	dmg	isp	mst	udl
bin	ear	jar	nsh	vb