Special Characters Issue when using Wordpress HTML messages
Hello,
We are having trouble where we are using a WordPress server send messages our to a few of our lists as HTML embedded messages. We do not want the messages to be shown as Plaintext, so we have that setting turned off in WordPress and in all our lists' settings.
The messages come through just fine, but several characters are being changed to "?". Some of these include ` and - . We recently upgraded from 2.1 to 3.3 and we love the new system, other than the fact that our news messages are looking bad because of all the "?" in them. The charset was set to US-ASCII, but I have changed it to UTF-8 and that has not seemed to do anything.
Any ideas on how we can prevent these characters from being changed?
On 3/22/22 07:46, ryan.anderson.4--- via Mailman-users wrote:
Hello,
We are having trouble where we are using a WordPress server send messages our to a few of our lists as HTML embedded messages. We do not want the messages to be shown as Plaintext, so we have that setting turned off in WordPress and in all our lists' settings.
You can accept HTML and not convert it if in Postorius -> Settings ->
Alter Messages, assuming Filter content is yes, ensure Pass types
includes text/html or maybe text to include all text maintypes and
both Collapse alternatives and Convert html to plaintext are set to No.
The messages come through just fine, but several characters are being changed to "?". Some of these include ` and - .
They probably aren't ` and -, but rather things like Unicode Left Single Quote and En Dash.
We recently upgraded from 2.1 to 3.3 and we love the new system, other than the fact that our news messages are looking bad because of all the "?" in them. The charset was set to US-ASCII, but I have changed it to UTF-8 and that has not seemed to do anything.
When you say you changed the character set to UTF-8, what did you do?
If you set
[language.en]
charset: utf-8
in mailman.cfg and restart mailman core, that should allow those characters without replacing them.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Hi Mark,
Thanks for the reply. I changed the language.master in the schema.py.
[language.master] # Template for language definitions. The section name must be [language.xx] # where xx is the 2-character ISO code for the language.
# The English name for the language. description: English (USA) # And the default character set for the language. charset: utf-8 # Whether the language is enabled or not. enabled: yes
ryan.anderson.4--- via Mailman-users wrote:
Thanks for the reply. I changed the language.master in the schema.cfg.
[language.master] # Template for language definitions. The section name must be [language.xx] # where xx is the 2-character ISO code for the language.
# The English name for the language. description: English (USA) # And the default character set for the language. charset: utf-8 # Whether the language is enabled or not. enabled: yes
And I replied but didn't include the list. My reply, reconstructed from memory:
That change together with restarting Mailman core should allow those characters unreplaced as long as it isn't overridden in mailman.cfg. Note that it will apply only to new messages and not to previously archived ones.
However, there are two issues with editing the master this way. It will affect the default settings for all languages, and it will be undone with any upgrade.
It is much better to add
[language.en]
charset: utf-8
to your mailman.cfg
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Mark Sapiro -
ryan.anderson.4＠go.mnstate.edu