Alvaro,
> My point. These days I mostly use UTF8, but presumably the file got
> mangled somewhere down the line. Remember that any decent email program
> is supposed to recode the file according to the headers and the local
> encoding of the reader -- and it works fine most of the time. But for
> these kind of things it is bound to fail at some point, which is why I
> prefer to avoid the UTF8. I mean, why use the unreliable solution when
> the reliable one is just as easy?
Let me regenerate that file, and I'll zip it before sending it in, which
should prevent browser/MUA mangling.
--Josh
