Re: Local overview cache

On Tue, Jan 26, 2010 at 03:51:22PM -0800, Sergey Kubushyn wrote:
> Hi guys,
> 
> It looks like there is a long standing bug with overview cache. You store it
> in UTF-8 (why not use what server sent?) but recode it from network charset
> next time it is used that makes article subjects unreadable. A simple
> example--in Russian newsgroups they mostly use KOI8-R encoding (but not
> always; there is also Windows-1251, UTF-8, ISO8859-5) -> most Linuxes use
> UTF-8 for their consoles -> you save KOI8-R (and other) message overview in
> UTF-8 -> works OK for the first time before that cache is used -> then you
> recode _UTF-8_ subjects to the local (also UTF-8) encoding using KOI8-R to
> UTF-8 recoding rules thus making them garbage. The only way to see articles
> properly after that is to remove that overview cache and restart tin.

the local overview records are in the local charset (8bit chars are mime
encoded if not configured to not do so, see below).

once you screwed up you local overview cache (i.e. by turning off mime
encoding), there is now way back except removing the cache.

> And guys, who told you that no mime header should be included when 8bit
> encoding is used? There are at least 4 different encodings used in Russian
> newsgroups and how is newsreader supposed to know which one to recode from
> for display?

tin generates mime headers when the charset is != US-ASCII and
post_8bit_header=OFF (which is the default).

urs
-- 
"Only whimps use tape backup: _real_ men just upload their important stuff
 on ftp, and let the rest of the world mirror it ;)" - Linus