Re: Gnus; Restore multi encoding support for NNTP

[LdBeth]

>>>>> In <87sfueb3y1.fsf@gnus.org> 
>>>>>   Lars Ingebrigtsen <larsi@gnus.org> wrote:
Lars> LdBeth <andpuke@foxmail.com> writes:

ldb> That would only solve the problem displaying the groups list from
ldb> server-mode, after Gnus saves the decoded group names in ~/.newsrc.eld
ldb> and reads in from a new session, it would not able to correctly figure
ldb> out the original group name from the starup screen group-mode. That is
ldb> why a mapping is needed (and it needs to be saved with the
ldb> .newsrc.eld file).

Lars> It knows the coding system to use for that group name, so it can use
Lars> that when encoding the name, too, surely?

Probably you mean using the coding system in
`gnus-group-name-charset-group-alist'?

That won't work in certain case, say, there's a group name on a server is
"nntp+news.newsfan.net:\346\265\213\350\257\225" (in UTF-8)
while the rest group names on that server are in GBK, so I set

```
(setq gnus-group-name-charset-group-alist
       '(("\346\265\213\350\257\225" . utf-8)
         ("news\\.newsfan\\.net" . gbk)))
```

And it's not able to use that to correct encode the names.

What's worse is when there are two group names having different coding
systems decoded to the same UTF-8 string for the same server, if gnus
doesn't correctly record which one uses which, well... (This is the
reason for using charset string property for that)

-- 
LDB