[KLUG Members] Invalid byte sequence in conversion input

[Adam Tauno Williams]

> I had a problem before with whitespace being some odd characters.  In
> that case Evolution was converting white space in txt files into some
> odd ascii, and when I did copy/paste the result wouldn't work elsewhere
> (though it --looked-- fine).
> 
> I'd check your white space.

If you can do an "cat {filename} | od -a | more" and you can see what
the character really is.  There are lots of non-visible ASCII
characters,  and this happens pretty often when you switch between
Unicode and Non-Unicode applications.