Alas, they don't mean anything without knowing what encoding you use
However they look like incorrectly encoded UTF-8 characters. The first is incorrect (it's not valid UTF-8), but the byte sequence 0xE2 0x80 0xA6 (2nd line) is the "three dot" character (that is "…", one char!) encoded in UTF-8. The 3rd line is the same + an extra normal dot, so that would be "…."
But then again, it might just as well have been iso-8859-1 encoding, and in that case they mean just the characters as they are displayed in your post...