Bug 134645 - charset choice - first declared, then UTF
Summary: charset choice - first declared, then UTF
Status: RESOLVED UNMAINTAINED
Alias: None
Product: knode
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-25 19:23 UTC by Paweł Różański
Modified: 2018-09-04 18:34 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Paweł Różański 2006-09-25 19:23:56 UTC 
Version:           0.10.2 (using KDE KDE 3.5.4)
Installed from:    Debian testing/unstable Packages
OS:                Linux

I would like to declare for example iso-8859-2 as default charset, but if post contains characters which can't be encoded to iso-8859-2, KNode should warn and ask if I would like to convert them to question marks and post it encoded in iso-8859-2 (just like now) or to change encoding for UTF. It would be great if there were checkbox in configuration labeled always post as UTF-8 if default charset doesn't match.
Comment 1 Andrew Crouthamel 2018-09-04 18:34:34 UTC 
Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I am closing this bug.