Bug 235577 - per-target encoding settings stored incorrectly in RC file
Summary: per-target encoding settings stored incorrectly in RC file
Status: RESOLVED NOT A BUG
Alias: None
Product: konversation
Classification: Applications
Component: general (show other bugs)
Version: Git
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Konversation Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-27 22:22 UTC by argonel
Modified: 2010-04-27 22:36 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description argonel 2010-04-27 22:22:14 UTC
Instead of being stored in the channel record itself, a channel encoding is stored separately under the [Encodings] group. This is should be in the channel record. Additionally, the format is ugly, eg: "ServerGroup 1 #konversation=UTF-8". This will only continue working as long as the ServerGroup id doesn't change.
Comment 1 Eike Hein 2010-04-27 22:36:55 UTC
The design of this and the practical reasons for it were discussed at length last year in #konversation.

The note about the id is also incorrect - the only requirement is that the contents of the file are self-consistent, because it's read in at app startup to build up internal data structures, and flushed out to disk again in a self-consistent state later.