Artem Kuchin writes:
16.05.2019 15:25, Sam Varshavchik пишет:It's highly likely that few of those messages are actual, authentic Unicode messages, but rather improperly encoded messages that, according to adopted EAI standards, must now be treated as Unicode content.Well, that does not change a thing. Still after seem them client call/write to support, waste my time and their own time too.Seems like world is not ready for this new standards and strict following them creates more problems than solves.
There's probably some truth to that. However there are clear benefits to improved EAI, and if things were left in place as they were, no progress will ever be made.
I guess this problem is more likely to appear in mass mailing systems (like corporate news, price list senders, etc) custom written in some languages like perl or python.I am still shocked that TB still did not implement UTF8 POP3 and IMAP protocol extensions.
That, unfortunately, is because TB is not really being actively developed any more, only maintained. It's on life support. That's what I read elsewhere. No new features are being developed, which is a shame, because it was, and still is, pretty good.
pgpQtMx1vLYBk.pgp
Description: PGP signature
_______________________________________________ Courier-imap mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
