9.01.2007 pisze Norbert Tretkowski ([EMAIL PROTECTED]): > * Miros/law Baran wrote: > > If introduction of a change that will decrease your user base and > > cause deterioration of user experience was something you desired > > (the whole pl.* hierarchy is now hard to read using your patched > > version of slrn), fine by me.
> The reason why I reactivated the charset patch for etch was because > users wanted to use slrn in an utf8 environment. 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. The patch in slrn at this moment does not allow for setting your preferred output encoding and does not allow for setting the default encoding that should be applied to 8-bit headers wthout charset declaration. In terms of user's experience (and in regard to at least the pl.* hierarchy) it's a regression -- slrn in this form is mostly unusable for Polish users. In other words, damned if you do, damned if you don't. > Stop blaming me for things you don't know the background! I'm not blaming you, I was just venting off a little frustration (you see, I don't want you to reverse the patch, I merely have noted that current implementation is incomplete; marking this as wishlist and wontfix without even making a simplest inquiry *did* anger me a bit). Jubal -- [ Miros/law L Baran, baran-at-knm-org-pl, neg IQ, cert AI ] [ 0101010 is ] [ BOF2510053411, http://hell.pl/baran/tek/, alchemy pany! ] [ The Answer ] WARNING TO ALL PERSONNEL: Firings will continue until morale improves. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
