Subj : src/sbbs3/sbbsecho.c
To   : Git commit to main/sbbs/master
From : Rob Swindell (on Debian Linux)
Date : Tue Sep 29 2026 19:00:50

https://gitlab.synchro.net/main/sbbs/-/commit/1debd362b1e3c690856c91b6
Modified Files:
	src/sbbs3/sbbsecho.c
Log Message:
SBBSecho: export a message's declared charset as its CHRS

A message posted with a MIME charset other than UTF-8 (for example from an
NNTP client set to ISO-8859-1 or Windows-1252) was exported to FidoNet as
"CHRS: CP437 2", so FTN readers mis-rendered its accented characters.

Netmail and echomail export now share ftn_charset(). When a message has
8-bit body text, no FTN charset and is not UTF-8, its MIME charset is
mapped to the matching FTS-5003 identifier: LATIN-1/2/5/9, CP1250/1251/
1252, CP850/852/866 (or CP437). Names are matched ignoring case, '-' and
'_'. Charsets FTS-5003 has no identifier for still export as CP437.

The configured origin line is CP437, so it is reduced to ASCII when the
message goes out in one of those other 8-bit charsets. A message whose
only 8-bit text is the origin line is still labeled CP437.

Fixes #1259

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
--- SBBSecho 3.37-Linux
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

.