Start a new topic

QA for double spaces / QA for non-translatables

Regarding the presence of double spaces in the source and target segments, there are these three variants:

  1. Source segment has one or more double spaces, in the target segment you only use single spaces (double spaces are likely to be typos in the source).
  2. Source segment has one or more double spaces, in the target segment you clone these double spaces (e.g. in display messages, to format text)
  3. Source segment has only single spaces, in the target segment you have one or more double spaces (double spaces are typos in the target).
Variant 3 is covered correctly by QA for double spaces.
Variant 2 is probably covered by QA for double spaces too, though you would get false positives here.
QA for non-translatables will give a lot of false positives for variant 1.

My proposal:

Take double (multiple) spaces completely out of QA for non-translatables. It's a real nuisance there.

Let QA for double spaces compare the source and target segment: if both contain double spaces at the same position, don't flag. If one of them has a double space at a position where it's missing in the corresponding segment (S or T), flag it.

Would the latter be a smart algorithm?


>Take double (multiple) spaces completely out of QA for non-translatables. It's a real nuisance there.


Please, Sir!

Especially with source documents that were created from PDF files by the client and are delivered as Studio projects, these double or triple spaces can be a nuisance. Removing them from the source side is tricky, since they can span tags.

Login to post a comment