The Automation features of Beebox are among the most exciting. While you can control each translation workflow step manually with the user interface, you can also automate some or even all operations. This includes operations such as detecting new source file, machine translation, creating new human translation jobs, exchanging jobs with translators or a TMS and creation of translated files.
...
- Submit translation requests: Automatically sends source files in New status to the TMS.
- Get latest translation status: Polls the TMS to see whether work is completed or cancelled in TMS and downloads preliminary and final files if available.
- The time interval in which Beebox polls the TMS can be specified below.
- Cancel workflows: If you cancel work in Beebox you can choose to cancel the work in the TMS as well.
...
Maintenance
These are operations that clean up data.
...
- For more information on Powershell scripting read: Powershell Scripts
- Beebox also lets you execute C# code to post-process translated files. See: Translated File Action
Statistics
If you mark the option "Save translation status to disk" beebox will generate in "out" directory filestatus.json file.
This file has data about all files (processed, or in the queue).
The file can contain the following data
| Code Block | ||
|---|---|---|
| ||
{
"skip": 0,
"count": 163,
"total": 163,
"files": [
{
"locale": "es",
"localename": "Spanish (es)",
"folder": "",
"file": "TRANSLATION_KAMINO_OUT_20190315132853\\k_partners_al-budget_FB.xml",
"segments": 22,
"words": 103,
"chars": 0,
"inJobSegments": 0,
"inJobWords": 0,
"uptodate": true,
"readyToBuild": false,
"notReadyToBuild": false,
"statusc": "Uptodate",
"status": 1,
"sfdate": "2019-03-15T13:29:06.3331946Z",
"sfdatemin": 43200,
"tfdate": "2019-03-15T13:52:28.1830645Z",
"tfdatemin": 43200,
"tdate": "2019-03-15T13:52:28.0737415Z",
"deadline": "2019-03-16T14:25:00Z",
"fmeta": [
{
"k": "dcrSource",
"t": "DCR source name",
"v": "k_partners_al-budget_FB_en"
}
],
"tmsDocuments": []
}, |