Right now, when you lock content, because it is tagged as not translatable, Studio does not perform any whitespace normalization, so it will keep the spaces you have in the source file. SDL Support reports that this is because they are trying to preserve our file structure. But this forces the user to choose between one feature or the other: either the content is tagged as non-translatable or the whitespace gets normalized. But why can't we have both? It seems logical that users would want to be able to have the whitespace normalized even if it is non-translatable. Otherwise, you are forcing us to unlock content that may then be accidentally translated. The other problem is that we end up with translation units saved in the TM with all kinds of whitespace and paragraph marks.