...

...

...

...

"BG" == Ben Gertzfield <che@debian.org> writes:

>> Here's a tricky issue, one with a high rabbit hole probability
>> (which I'd like to avoid if possible ;).  OTOH, we could use a
>> simple heuristic to try to keep the prefix unencoded in the
>> common case: if the prefix contains only ascii characters, we
>> could choose to leave it in the default us-ascii (or really the
>> None) encoding.  If it contains non-ascii characters, we'd have
>> no choice but to encode it.

BG> OTOOH, we could make *this* the per-list setting; we could
BG> have the heuristic guess whether to encode or not if the list
BG> owner wants it. That way we don't have to have a ton of prefix
BG> character set settings, and we make the people who get angry
BG> at seeing [MyFrenchList] encoded in header QP happy.

Is subject_prefix the only place this option would make sense? If so, then I can probably add a boolean variable to the General admin page, otherwise I might want to add something to the Languages page.

BG> Sorry for being absent recently, I'm finally at a job that's
BG> challenging enough to make my brain not want to do coding at
BG> home. :)

That's good (I think ;). Welcome back, and I hope you'll stick around!

-Barry