9.01.2007 pisze Norbert Tretkowski ([EMAIL PROTECTED]): > > As in the bug title; after eliminating the mime_charset variable now > > there's no way to specify the default charset for the newsgroup or > > the whole running instance of slrn; this causes displaying '?' in > > place of diacritical chars in some subjects and From: fields, > > additionally it breaks scorefile patterns that use diacritical chars > > and are applied to these headers.
> Sounds more like a problem with some broken newsreaders, which don't > declare the charset in the subject when using diacritical chars. Yes, it is problem with some broken newsreaders. As it's quite impractical to go to the world and fix them all, other, not-so-broken newsreaders (including -- to this moment -- slrn) did the ugly workaround that allowed to define the default encoding. The change you so gratuitously introduced just in the last moment before the release did disable this quite usable feature. 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. I will not change the severity of the bug nor will play BTS wars on this one nor try to change your mind; change of newsreader is much less painful and tin already has better MIME handling than slrn. Thank you for caring for your users needs and for your fine cooperation. Jubal (sligntly overreacting, so do not take the sarcasm too hard) -- [ 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 ] Everything is controlled by a small evil group to which, unfortunately, no one we know belongs. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
