Skip to main content

Apply fixes

A report can write its confirmed fixes into a copy of the file. Your original file is never changed.

Fix it and download the corrected copy, 32 seconds, narrated, with captions.
Read the transcript
  1. Fix it and download the corrected copy. In three quick steps.
  2. 1. Press Accept fix. Or press Edit and change the target yourself.
  3. 2. Check the edit. The segment is checked again straight away.
  4. 3. Open Download and choose Corrected file. Your original is never touched.
  5. Next: Set up a client.

What is applied​

Only confirmed findings with a fix the tool can make: a wrong number, a dropped tag, a term that must read a set way, a missing space. A finding the AI disputed, a finding you ignored and any finding whose fix is advice rather than a replacement are left alone. The change log lists every edit, segment by segment, with before and after.

A rule fix names the one place in the segment where the word stands. When the same word stands twice, the report shows the finding with advice and no written fix; you change the right one.

A spacing fix never removes a no-break space. The double-space fix keeps a no-break space that stands in the run, and the French spacing check writes the missing no-break space for you. A missing no-break space in French at warning is confirmed like other exact checks and Apply fixes writes it; at minor it waits for your decision. In the report, a no-break space in the evidence of a spacing finding shows as ␣, so you can tell it from a plain space.

Segments with tags​

A fix on a segment with inline tags may change the words between several tags and move a tag with its words, as word order needs in another language. Each tag stays exactly as it is in the file, only in its new place. A fix that would drop, repeat or add a tag, or close a pair before it opens, is not written: the finding keeps its advice and you make that change in your CAT tool.

How​

From the report, or from an assistant over the MCP server ("Apply the confirmed fixes, recheck the copy and show me what changed"), or through the API. A dry run shows the log only. The copy and its log download through a link that works for one hour; ask again for a fresh one.

You can also change segments by hand in the report and download the corrected file from there: see Edit a segment in the report.

Send the corrected copy back​

When the file came from somewhere the report knows, the Download menu also offers to send the corrected copy back there, under Send corrected copy. It is always one click of yours and always a new file or a suggestion: nothing is sent on its own and the original is never overwritten.

  • Dropbox: a file from a watched Dropbox folder. Save corrected copy to Dropbox puts name.corrected.xlf in a Corrected folder beside the original. When that name is taken the copy is saved as name.corrected-2.xlf and so on. The report shows where it went, and the folder check never checks the copy.
  • QA by email: a file you emailed in. Email the corrected copy sends it to the person who sent the file, as long as they are still a member of the workspace. A large file comes as a download link that works for 72 hours.
  • Smartling: a file the Smartling connection checked. Send findings to Smartling as issues posts each finding you edited as a Smartling issue with your text as the suggested fix. Nothing is written into the translation.

For an SDLXLIFF file you can tick With tracked changes for Trados first, and Dropbox or the email gets the copy with tracked changes instead. Each one sends a copy once: asking again for the same copy says it was sent before. The API gives the same corrected copy with one call.

Recheck​

Run the copy as a new check and the report says what was resolved, what remains and what is new. The same works when you fixed the file yourself in your own tool: run the new version and the report compares it with the last run of that file, with last time's decisions carried over.

Which files​

A single XLIFF file (SDLXLIFF, MQXLIFF, XLIFF 1.2 and 2 and the rest of the family), an Excel workbook (.xlsx or .xlsm) or a CSV or TSV file. In a workbook or a CSV or TSV file only the target cells change; styles, formulas, comments, other sheets, macros, the encoding and the line ends stay as they are. In a workbook a cell with a formula, a number or a date is left alone.

A software string file works too: a gettext .po file on its own, and a zip with the source and the translated .json, .resx, .strings, .stringsdict or .properties file. Only the changed values are written: the key order, the comments, the indentation, the encoding and the escaping style stay as they are, and a .po file's fuzzy flags are left as they are: a corrected entry that was marked fuzzy keeps its fuzzy flag, because whether the string is ready for use is the translator's call in their own tool. Two files dropped together have no corrected copy yet; check them as a zip. A value whose place in the file cannot be found exactly, such as a .resx name written twice, is left for you and the change log says so.

A package works too: a WorldServer package (.wsxz), a Trados project or return package (.sdlppx or .sdlrpx), a memoQ package (.mqxlz), an .xlz or a zip of such files. Each fix goes into the file inside the package that the report names, and only that file changes. Every other file in the package, the project file of a Trados package included, stays byte for byte as it is, in the same order. Trados recalculates the word counts and statistics when you open the package. A zip inside the package is written too; one more level down is left alone.

Tracked changes for Trados​

For an SDLXLIFF file you can also get the corrected copy with each fix as a Trados tracked change: in the report choose Corrected file with tracked changes (Trados) in the Download menu, or ask an assistant to apply the fixes with tracked changes. Only the words that changed are marked, the old words as deleted and the new ones as added. A reviewer opens the file in Trados Studio and accepts or rejects each change. Tags are never inside a tracked change and the written segments are set to Draft, as in the plain copy. A fix that moves a tag is left out of this copy, since a moved tag cannot be a revision; the plain corrected file has it.

This option is new. Open the file in Trados Studio and check it before you send it to a client. The plain corrected file stays the default.

What is never touched​

The original file. Locked segments. Segments the check skipped. Anything a person has not confirmed.