Avoid using ELLIPSIS macro

[lsahn-gh]

Some strings using the macro cannot be translated in the right way,
because PO files are made by source code instead of compile-time code.
The macro is actually translated while compilation and therefore it
causes the issue, #2275.

To fix the issue, use the literal ellipsis string instead of it.

Fixes #2275

[TingPing]

The reason this was done in the first place is msvc doesn't like non-ascii text.

[lsahn-gh]

I changed it to use ellipsis utf-8 hex code itself in the messages. This is probably a solution for windows too. Another solution is to use three dots there.

[TingPing]

I guess that works, it doesn't help the situation for translators though.