On 12/9/20 6:39 PM, matthew@alberti.us wrote:
For core, the connection string seems to accept a tailing "?charset=utf8&use_unicode=1" per https://mailman.readthedocs.io/en/stable/src/mailman/docs/database.html So for core, maybe just updating the connection string to include "?charset=utfmb4&use_unicode=1" will just work? The link lists utf8 as the recommend encoding... maybe that should be updated?
I'm in the process of doing that update.
Seems the takeaway is that, for mysql databases only, the use of utf8mb4 is recommended, and it needs to be explicitly identified in the database settings for BOTH core and web, and probably somehow at database creation time?
It's not as critical for core because barring things like 4-byte utf-8 unicode graphics in list configurations, core doesn't store anything like that in its tables. The major issue is with HyperKitty where messages have emojis and other 4-byte utf-8 encodings in message subjects and bodies.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan