Not Considering

Hi - we cannot consider this at this point in time unfortunately. Leading and trailing spaces are trimmed from the segment when stored in TM and are also typically treated as content between segments and never part of the segment. As a potential workaround, it might be possible to use non-breaking spaces (Alt+0160 character code) and keep those in the segment.

Respect spaces at the end of segments

Some clients provide files from XML exports or other tools that contain spaces at the end of segments.

Those spaces are required to be kept, as otherwise the end result will have, say, a full-stop plus the first letter of the next sentence without any whitespace in between.

Currently, even though I translated the segment with the ending space, it is not honored in the TM, i.e. the segment gets written to the TM without that space and counts as a 100 % match the next time the same segment (with the ending space) occurs, leading to issues on the client's side.

Guido Lenz
Parents

  • A very good idea! Especially when working with Transit PackageHandler, it is extremely annoying that the spaces are not saved to the TM (heither are tags). When segments are autopropagated, only the first segment is correct and all the others (with trailing spaces or tags) need to be reviewed and corrected manually. This is time-consuming ...

Comment

  • A very good idea! Especially when working with Transit PackageHandler, it is extremely annoying that the spaces are not saved to the TM (heither are tags). When segments are autopropagated, only the first segment is correct and all the others (with trailing spaces or tags) need to be reviewed and corrected manually. This is time-consuming ...

Children