...
| Config name | Values | Default | Description |
|---|---|---|---|
| runtimeOptions.plugins.transit.writeInfoField.enabled | 0 or 1 | 0 | decides, if information is added to the target-infofield of a segment- further config values decide, which information. |
| runtimeOptions.plugins.transit.writeInfoField.exportDate | 0 or 1 | 0 | decides, if exportdate is written to infofield. |
| runtimeOptions.plugins.transit.writeInfoField.manualStatus | 0 or 1 | 0 | decides, if manualStatus is written to infofield. |
| runtimeOptions.plugins.transit.writeInfoField.termsWithoutTranslation | 0 or 1 | 0 | decides, if SourceTermsWithoutTranslation are written to infofield. |
| runtimeOptions.plugins.transit.writeInfoField.exportDateValue | Date | Optional, if empty the current date is used. If a specific date should be used, configure it in the form: YYYY-MM-DD | |
| runtimeOptions.plugins.transit.exportOnlyEditable | 0 or 1 | 1 | Per default only the content of editable segments is written back to transit file. This does not influence the Info Field! |
Debugging
Adding the following line to your installation.ini enables debugging output for Transit Plugin.
runtimeOptions.debug.plugin.Transit = 1Enabled debugging with the value 1 enables more verbose output in using transit im and export.
- You can also specify other integers than 1, the value is compared binary.
- If the debug value contains binary the integer 2: The whole string which would be written into the transit info field on export is written into PHP error log.
- If the debug value contains binary the integer 4: On export a validation is implemented, which checks the countings of red and blue terms in source and target. This check can be set to strict mode by setting debug & 4. Strict mode is useful to find termtagger issues. The content of the logged segments has to checked manually (see TRANSLATE-550)