On Fri, Mar 13, 2009 at 09:14:11AM -0400, Ken Murchison wrote:
Sorry for the typo in the Subject.
Ken Murchison wrote:
I just put together a release candidate for Cyrus 2.3.14. I'd
appreciate any independent testing before I release this to the masses.
I spent some time last night working out why the cyrus.cache entry for a
specific message differed on a master and replica system. An eight bit
character in a To: header (allowed by reject8bit: no) had been
transformed into a space character in the cache on the replica.
The root cause turned
On Thu, Mar 19, 2009 at 11:25:56AM +, David Carter wrote:
I spent some time last night working out why the cyrus.cache entry for a
specific message differed on a master and replica system. An eight bit
character in a To: header (allowed by reject8bit: no) had been
transformed into a
So we have a stack of interfaces that take a character
pointer, a length - sometimes even a malloced length,
and have reallocation possibilities. If you want to
pass back the length you realloced to, you need to
pass _three_ different variables to the function like
so:
int f(char *base, int
Hi,
Does anybody actually use the ISO-2022-KR charset here? Does
anybody know who's responsible for it?
I ask because of:
http://en.wikipedia.org/wiki/EUC-JP#EUC-KR
and
https://bugzilla.andrew.cmu.edu/show_bug.cgi?id=2301
Which leads me to believe that using the new KSC-5601 charset
is
