gergoe

Thank you for looking into that! We've discussed it internally and come to the conclusion that trimming the spaces is indeed something we shouldn't pursue further, the message (which is more than just a message by the way; it in fact blocks the user for proceeding with a trailing space - don't know if that was intentional Hiroshi) should bring the attention of the user to the fact that there might be something wrong with the input. I had conducted a little research on the use of leading/trailing...

In the project where we are looking after ~1000 users educating them on how to move the mouse when selecting a piece of text (the password) sounds somehow inappropriate (but on the other hand we have daily requests on authentication issues, so we'll consider that option): The passwords contain symbols, which does not count as word characters, thus double-clicking does not work in those situations; Selecting the line by moving the mouse from the beginning of the line to the next line in a downward...

I share your concerns regarding manipulating user input, but having a white-space around input values is a grey-zone. If there would be statistics available on how many times it would appear because of an accident or intentionally, I'd be very sure of the result of that. That's why I suggested second-guessing (in this very particular case) the VCS password, because in the vast majority of cases the white-space will be added by accident - not intentionally. The warning message from Hiroshi is very...

Hiroshi, I agree on avoiding the altering of user input especially during authentication, but in the case of long passwords (when it's difficult to see how many characters were entered/pasted) it becomes impossible for the user to confirm their input. If they copy their passwords from somewhere (and they almost always do), they risk of including trailing white-space, so they require to use an intermediate step/program to verify their input before entering it in OmegaT. This requires skill and training...