You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a client who uses the U+2009 THIN SPACE character on either side of every forward slash (/) when the slash separates two options, i.e. "either / or", "this / that".
Matecat represents the U+2009 THIN SPACE character as a tag.
In some cases, it makes sense to replace the slash in the translated text with the word "and". In these cases, it also makes sense to replace the THIN SPACE characters with regular spaces.
However, since they are tags, it does not appear to be possible to simply omit them. It also not optimal to move them to the end of the segment where they will cause two THIN SPACES to be added at the end because this will have to be cleaned up after exporting the translation to the original file format.
The text was updated successfully, but these errors were encountered:
We have a client who uses the U+2009 THIN SPACE character on either side of every forward slash (/) when the slash separates two options, i.e. "either / or", "this / that".
Matecat represents the U+2009 THIN SPACE character as a tag.
In some cases, it makes sense to replace the slash in the translated text with the word "and". In these cases, it also makes sense to replace the THIN SPACE characters with regular spaces.
However, since they are tags, it does not appear to be possible to simply omit them. It also not optimal to move them to the end of the segment where they will cause two THIN SPACES to be added at the end because this will have to be cleaned up after exporting the translation to the original file format.
The text was updated successfully, but these errors were encountered: