#8147: New message should not default to CP1252
---------------------------------+----------------------------
Reporter: rq | Owner: czeidler
Type: enhancement | Status: new
Priority: normal | Milestone: R1
Component: Applications/Mail | Version: R1/Development
Resolution: | Keywords:
Blocked By: | Blocking:
Has a Patch: 0 | Platform: All
---------------------------------+----------------------------
Comment (by siarzhuk):
Replying to [comment:12 bonefish]:
> Why would a user want to set the character set? Seriously, what's the
use case?
As Rimas already noted above, Chinese are using their's own Unicode
standart GB18030 that is not compatible with UTF-8.
> The only thing I can come up with is that you want to send a mail to
someone from whom you know that they use an ancient mail client that
doesn't support certain charsets. How realistic is that?
With Russian "encodings soup" it is realistic scenario. ;-) Many clients
are still using koi-8r, cp1251 etc.
> I would remove the option and let Mail internally first try a simple
legacy charset and, if that doesn't work, fall back to UTF-8.
I propose the following:[[BR]]
1) Introduce the string B_TRANSLATE_CONTEXT("Default (UTF-8)", "Default
Message Compose encoding") as the key to select default encoding in the
mentioned menu;[[BR]]
2) During translating, for example, to Russian, the Translator can decide
to use "Windows CP-1251 charset" translation for this string;[[BR]]
3) At the run time the program use localized string as key in the menu and
fallback to UTF-8 in case encoding was not found.[[BR]]
--
Ticket URL: <http://dev.haiku-os.org/ticket/8147#comment:13>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.
