Re: Test From Blue Wave Door
  By: Michiel van der Vlist to mark lewis on Sun Jun 07 2020 16:18:20


 MvdV>> No CHRS kludge.

 ml>> the OP is behind in his updates... sbbs and sbbsecho have been through
 ml>> a lot of changes and updates in the last 1.5 years...

 MvdV> The point was that without a CHRS kludge one can not expect non ASCII
 MvdV> to be correctly displayed at the reader's end.

yep... sbbs should be properly applying a CHRS control line to posted messages
based on the message (and header) content...

 MvdV> Without a CHRS kludge, one is limited to ASCII only if one wants it
 MvdV> readable at the other end.

true... the point of my response was that the original system is behind in its
updates... note the dates below and compare to the original post's sbbsecho TID
line...

----- snip -----
rswindell
Tue May 05 2020 05:35 pm PDT

Modified Files:
src/sbbs3/qwktomsg.cpp  1.85    1.86    diff

Log Message:
Automatically detect the character set of QWK-imported messages (that don't
already have a FidoNet "CHRS" header) and create/set the FIDOCHARS header field
accordingly (UTF-8, ASCII, or CP437). This should resolve the issue I observed
of QWK-posted messages on FidoNet with the wrong CHRS header value (i.e. CP437,
when the message body in fact contained UTF-8).

-----

rswindell
Tue Sep 17 2019 03:29 am PDT

Modified Files:
src/sbbs3/echocfg.c     3.48    3.49    diff
src/sbbs3/rechocfg.c    3.40    3.41    diff
src/sbbs3/sbbsecho.c    3.140   3.141   diff
src/sbbs3/sbbsecho.h    3.35    3.36    diff

Log Message:
Added support for auto-detection of incoming UTF-8 messages (default: enabled).
If an incoming message contains no CHRS/CHARSET control line *and* the message
text contains valid UTF-8 character encodings, set the FTN charset value to
UTF-8 so the message will be displayed/handled accordingly.
I did not add checks for header fields (to/from/subject) - we should probably
auto-detect UTF-8 in those as well, but for now, I don't see messages coming
into FidoNet echoes with UTF-8 in the header fields.
Incremented SBBSecho/EchoCfg version to 3.10.

-----

rswindell
Thu Aug 22 2019 09:50 pm PDT

Modified Files:
src/sbbs3/js_msgbase.c  1.251   1.252   diff

Log Message:
Add ftn_charset property for message headers. This header field corresponds
with the FTN (FTS-5003) "CHRS" control line/paragraph. The values recoginized
by Synchronet are:
    "ASCII 1"
    "CP437 2"
    "UTF-8 4"

These values indicate that header fields and body text of a message are
encoded with the specifiec charset. The default (assumed charset, if not
specified), is CP437.

-----

rswindell
Sat Aug 03 2019 03:07 am PDT

Modified Files:
src/sbbs3/sbbsecho.c    3.126   3.127   diff

Log Message:
Export a default CHRS: (charset) value of "UTF-8" when any of the header fields
contain UTF-8 characters.

-----

rswindell
Fri Aug 02 2019 01:31 am PDT

Modified Files:
src/sbbs3/sbbsecho.c    3.124   3.125   diff

Log Message:
If SBBSecho imports a message with a "CHRS" control line with a value of
"UTF-8", set the msg's auxattr MSG_HFIELDS_UTF8 flag because FTS-5003 states:
  "The character set identifier applies to all parts of the message,
   including the header information and the control lines like origin
   and tear line."

----- snip -----

there are more CHRS and CHARACTERSET related commits to the repository...

one can go here for more information:

  http://cvs.synchro.net/commitlog.ssjs?5000

drop/change the "?5000" from the URL for default or specific number of commits
to list...


)\/(ark
--- SBBSecho 3.11-Linux