[Scspamcop] Re: Internationalize SC reports - a little bit...?

[WazoO]

"Patto" <nobody at devnull.spamcop.net> wrote in message
news:f19etb$3ns$1 at news.spamcop.net...
> I don't know if there is anybody still doing maintenance on the SC code.

Credits and Thanks
http://www.spamcop.net/fom-serve/cache/138.html

> If so, I would like to suggest a small effort to stop distorting
> non-latin spam source text.  For instance...
> http://www.spamcop.net/sc?id=z1292523895z968197bd510d7f9a0b1390e94506f070z

It's not a 'small' effort, actually ....

At issue is the character-set handling involved between the server,
PHP, (My)SQL, the e-mails in question, on and on ....

The magic word in general is 'internationalization' .... folks
around the world are trying to deal with this issue ....

> There would be such a tiny little effort to preserve the original
> encoding, as found in this header line
> "Content-Type: text/plain; charset=ISO-2022-JP"

I wish this was true .... believe me ....

> If this is set to the same in the outgoing SC report, then the
> recipients would see the *original* source data, not question marks.

As stated above, it's not like the e-mail just sits there waiting to
be tossed out 'directly' .... it's actually grabbed, stored, manuplated,
handled, processed, etc. by a number of tools, not all of which can or
are configured to handle every character-set under the sun ....