Check a spreadsheet

A client's Excel request usually has one source column and many language columns. It has to be told which two to compare.

Check a spreadsheet, 39 seconds, narrated, with captions.

Read the transcript

1. Check a spreadsheet. A bilingual Excel or CSV file.
2. 1. Drop the sheet on Run a check. Here an Excel bilingual of 5 segments.
3. 2. Press Run the check. Confirm the columns opens first.
4. 3. Check the source and target columns. The first rows show what each column holds.
5. 4. Pick the ID and note columns. Optional. A note goes with its segment to the report.
6. 5. Press Use these columns. The sheet runs like any bilingual file.
7. Next: Read the report.

1. Drop the .xlsx on Run a check as usual.
2. Confirm the columns opens. It guesses, and you correct it.
3. Set Source to the English column and Target to the language you are reviewing.
4. If the workbook has several sheets, pick the sheet too, then Run.

It guesses (here: Source English and Turkish) and shows you the first rows so you can check.

Check this every time

If the wrong column is chosen, the check compares the wrong two languages and the result is meaningless. The dialog is there so that choice is yours, not a guess.

The optional columns

An ID column gives each row a stable segment id, so a finding names the row the way your tool does. A Note column is carried into the report as the segment's note.

When the sheet is rejected

"No source/target column" means the header row could not be identified: usually a title or banner row above it, or column labels the tool does not recognise. Map the columns by hand in the dialog, which overrides detection entirely.

When the rows look like a QA report rather than a bilingual file, the dialog says so before you run and lets you continue with the columns you chose.