Hi! Miros/law wrote:
> OK, but this patch does not enable full utf-8 support (it merely causes > slrn not to be broken in most popular configurations). Full utf-8 > support (and MIME support) is something that mutt has. From the > newsreaders, both tin and slrn to this moment do not have really decent > handling of multiple encodings. Actually, the patch _does_ provide full support for utf8 (and all other encodings known to libc, except UTF-16 en -32). > The patch in slrn at this moment does not allow for setting your > preferred output encoding Actually, it does, in the only sane way possible (IMO), namely through the locale settings. > and does not allow for setting the default > encoding that should be applied to 8-bit headers wthout charset > declaration. That's true, but that is trivial to add. Norber wrote: > There's one thing I can do to make everyone happy... provide two > binary packages, one called slrn which does not contain the charset > patch, and the other one called slrn-utf8 which does contain charset > patch. That's a rather ugly solution, if you ask me. Would you rather consider adding a patch as I suggested above, that adds a new config option "default_header_charset" or so, which controls the charset to fall back to for non-encoded headers? I can see if I can hack on that later today... Bas. -- Bas Zoetekouw
