Israel Herraiz: > As far as I know (considering what I have read in the documentation > and in the archives of this mailing list), Sup determines the encoding > using the environment variables and tries to decode all the messages > using that encoding. For people working in different languages and > environments (like me, I write in English and Spanish, some people > send me messages in UTF-8, some other in ISO-88159-1), having an > overall encoding for all the messages is not a good solution.
I agree wholeheartedly – I tried to use Sup a couple of weeks ago, but this issue made it unusable for me (I planned to hack on this some day, but my work and uni obligations do not leave any free time lately). :( To make matters worse, the relevant RFC actually requires emails to be encoded in the ‘tightest’ encoding possible – when I’m writing an email in Polish without any non-US-ASCII letters, it should be sent as US-ASCII; if I include Polish diacritical characters, it should be encoded as ISO-8859-2, but if I add some characters outside of it (say, ellipsis) it should be sent in UTF-8. As a result, I regularly receilve emails in US-ASCII, ISO-8859-2 and UTF-8 – but also in ISO-8859-1, ISO-8859-15, as well as some cyryllic encodings. I remember Mutt going through some growing pains to accomodate this, but has it all sorted out now (there is an issue of recoding the email one replies to to the encoding expected by the editor, for example). I’ll be more than happy to test any work done in this regard and I offer any knowledge that could be useful; unfortunately, I can’t promise any hacking time (I just got accepted for this year’s Summer of Code to hack on CiviCRM internationalisation – maybe Sup could apply to be a project in next year’s SoC edition?). -- Shot -- I grew up in Europe, where the history comes from. -- Eddie Izzard
pgpdG93Y1VodA.pgp
Description: PGP signature
_______________________________________________ sup-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/sup-talk
