* Originally in n5020.sysop
* Crossposted in ru.ftn.develop
Hello, Eugene!

Saturday March 08 2025 03:03, from Eugene Palenock -> Sergey Dorofeev:

IBMPC=CP437
ili net?

fsc 54
fts 5003
� ⠪ ������� �� IBMPC 㦥 �� ����� CP437, � ����� ���� OEM(DOS)-����஢��. ���� ����筮 �� 㦥 �� ������ �ᯮ�짮������
�����.

�⢥砥� ��⮢. �᫨ ���⪮, � ᭠砫� IBMPC �뫮 CP437, ��⮬ ��諮 �� �� CP. ����� ��⮬� �뫮 �襭� ������ �� ����஢�� IBMPC, ��� ��� �� �������筠.

=== Chatoff ===
Short answer:
Historically, the "IBMPC" charset identifier started out meaning "IBM codepage 437," but in practice it evolved into a catch-all for any DOS/OEM codepage. Modern FTSC standards deprecate "IBMPC" because of that ambiguity. Instead, they recommend using a specific "CPxxx" identifier (e.g., CP437, CP866) to eliminate confusion.

Where it is stated
FTS-5003, Section 4
Lists "IBMPC" under Level 2 character sets (eight-bit, ASCII based) but marks it as obsolete. The text says:

Level 2 obsolete character set identifiers (see note)
IBMPC: IBM PC character sets for European?

FTS-5003, Section 5 (Obsolete identifiers)
Explains that "IBMPC" initially used to indicate IBM codepage 437, eventually evolved into identifying "any IBM codepage". Implementations would sometimes include a separate "^ACODEPAGE: xxx" line to specify which actual DOS codepage was used. Quoting:

"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" This use is deprecated in favour of the "CPxxx"
identifiers."

FSC-0054 ("The CHARSET Proposal")
Defines "IBMPC" at Level 2 but does not pin it down to a single codepage; it simply acknowledges it as an IBM PC style extended ASCII environment.
=== Chatoff ===

Best Regards, Nil
--- GoldED+/LNX 1.1.5-b20240306
* Origin: ChatGPT can make mistakes. Check important info. (2:5015/46)