= Сообщение: 6506 из 7128 ====================================== FTSC_PUBLIC = От : Michiel van der Vlist 2:280/5555 19 Sep 22 14:45:06 Кому : Tim Schattkowsky 19 Sep 22 14:45:06 Тема : Automatically promote UTF-8 in editors? FGHI : area://FTSC_PUBLIC?msgid=2:280/5555+632865c9 На : area://FTSC_PUBLIC?msgid=2:240/1120.29+caaf9503 = Кодировка сообщения определена как: UTF-8 ================================== Ответ: area://FTSC_PUBLIC?msgid=2:240/1120.29+cb51100a ============================================================================== Hello Tim,
On Monday September 19 2022 11:46, you wrote to All:
TS> following the latest charset discussion, it came to my mind that it TS> might be a nice idea, to promote the transition from legacy charsets TS> to UTF-8 by editors automatically changing to charset on reply to TS> UTF-8 for areas where UTF-8 seems to be acceptable.
I already have it configured like that for this area for a decade or so.
TS> What do you think?
Good idea.
TS> destination area has this preference set to UTF-8. In some packages TS> (like WP), this is probably a single line of code. For areas, where TS> the audience is likely to use tools that cannot handle UTF-8, the area TS> default may be set to something else (e.g., IBMPC)
IBMPC is not a good idea as it is documented as obsolete, deprecated and ambiguous. It MUST NOT be used when creating new messages.
5. Obsolete indentifiers ------------------------
These indentifiers must not be used when creating new messages. The following only applies to processing messages that were created using old software.
Since the "IBMPC" identifier, initially used to indicate IBM codepage 437, eventually evolved into identifying "any IBM codepage", there exists in some implementations an additional control line, "CODEPAGE", identifying the messages codepage:
"^ACODEPAGE: xxx
This use is deprecated in favour of the "CPxxx" identifiers defined above. If found in incoming messages, however, it should be used as an override of the "CHRS: IBMPC" identifier.
