6.0.0-beta1
7/14/25

[#10157] Encoding select in Compose message screen
Summary Encoding select in Compose message screen
Queue IMP
Queue Version Git master
Type Enhancement
State Rejected
Priority 2. Medium
Owners
Requester anri (at) polynet (dot) lviv (dot) ua
Created 05/30/2011 (5159 days ago)
Due
Updated 06/07/2011 (5151 days ago)
Assigned
Resolved 06/07/2011 (5151 days ago)
Milestone
Patch No

History
06/07/2011 05:35:07 AM Michael Slusarz Comment #2
State ⇒ Rejected
Reply to this comment
No.  A user should not care what charset they are sending in.   
Especially since most users don't even know what charcter sets/UTF-8 
means.  And UTF-8 should be fine for sending any message.
05/30/2011 03:23:07 PM anri (at) polynet (dot) lviv (dot) ua Comment #1
State ⇒ New
Priority ⇒ 2. Medium
Type ⇒ Enhancement
Summary ⇒ Encoding select in Compose message screen
Queue ⇒ IMP
Milestone ⇒
Patch ⇒ No
Reply to this comment
Hi,
there are situations, when using 'default' encoding for given locale 
is not enough... Users have to be able to select alternative encoding 
for specific purposes.. E.g. ukrainian users besides "windows-1251" 
also use utf-8 and koi-8u... Please, bring back that encoding selector.
--
Andiy Kopystyansky

Saved Queries