[Mutt] #3023: hcache vs. switching charset
#3023: hcache vs. switching charset
ok, another case of hcache fscking the user for no good reason:
i switched the charset and then wondered why the index and the pager
disagree on certain header fields ...
yes, i know that this is documented, but WTF? why do i even have to care?
given that one might want to actively use two different charsets (e.g.,
one for local access and one for access from a vt200 ;), i see two
approaches:
1) make the cache charset-independent, like by encoding everything as utf8
2) hash the charset into the cache name
1) has the downside that it relies on iconv being compiled in. otoh, why
would one care for charset without iconv? 2) has the downside of
performance loss when switching charsets. i think 1) is the way to go with
a possible fallback on 2).
--
Ticket URL: <http://dev.mutt.org/trac/ticket/3023>