Hi
I cannot answer for mailman, but in general, utf8mb4 is definitely the way to go for MySql; the original utf8 implementation in MySQL supported only 3-byte characters, and that excludes quite a number of character codes that are commonly used, notably various emojis.
I would not suggest use of the latin1 (or indeed any of the others, eg cp1251) character codings for any purpose these days; UTF-8 is almost equivalent in one byte and extends to a far greater coverage. The only situation you should need the older options us to interoperate with old software.
On the basis of the above, if the docker containers is fixed with latin1, I would suggest that is a bug.
Regards,
Ruth
On 08/12/2020 17:05, matthew@alberti.us wrote:
Hi,
I've been working for quite a while to setup a production mailman3. Using the docker containers, I have been pretty successful getting it to work. Part of the challenge now is that there are a lot of issues when importing archives from mailman2. This of course is more common on lists that are over 10 years old.
From what I've been reading, it seems like Mailman3 expectsthe mysql database to use UTF8 encoding. It appears, by default, that when using the docker-mailman containers, that the character set is set to latin1. This may explain why there are lots of import errors, and maybe also why there are a lot of errors when threads are deleted in hyperkitty's UI.
Is it the case that UTF8 is the preferred character set? Ialso saw some threads indicating that maybe utf8mb4 is more preferred. I'd like to try to change the character_set on the database, if that is advisable.
Also, is Hyperkitty 1.3.4 officially released? I see that thelist.org instance is using it, but the latest announce I've seen is for 1.3.3.
Thanks.
- Matt Alberti
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/