> On 23 Feb 2022, at 2:50 pm, Wietse Venema wrote:
>
>>>
>>> TWO settings to enable UTF8? Bah.
>>
>> No, because the second one would be *ON* by default.
>
> And that would be an incompatible change from LATIN1?
Only if also "smtputf8_enable = yes". That is, with "smtputf8_enable = yes"
we'd
Viktor Dukhovni:
> > On 23 Feb 2022, at 6:38 am, Wietse Venema wrote:
> >
> > TWO settings to enable UTF8? Bah.
>
> No, because the second one would be *ON* by default.
And that would be an incompatible change from LATIN1?
> It would probably be better named "utf8_disable" and then
> be "off"
> On 23 Feb 2022, at 6:38 am, Wietse Venema wrote:
>
> TWO settings to enable UTF8? Bah.
No, because the second one would be *ON* by default.
It would probably be better named "utf8_disable" and then
be "off" by default.
--
Viktor.
Phil Stracchino:
> On 2/23/22 06:38, Wietse Venema wrote:
> > TWO settings to enable UTF8? Bah.
>
> I have to admit that my feeling on this is "Let LATIN1 die". The future
> is encoded in UTF8/UTF16.
Agreed, for the longer term. But the patch was for the stable release.
Wietse
On 2/23/22 06:38, Wietse Venema wrote:
TWO settings to enable UTF8? Bah.
I have to admit that my feeling on this is "Let LATIN1 die". The future
is encoded in UTF8/UTF16.
--
Phil Stracchino
Babylon Communications
ph...@caerllewys.net
p...@co.ordinate.org
Landline: +1.603.293.848
TWO settings to enable UTF8? Bah.
Wietse
On Tue, Feb 22, 2022 at 07:10:44PM -0500, Wietse Venema wrote:
> There are two #ifdef SNAPSHOT blocks.
>
> - The one in dict_pgsql_lookup() returns not found when SMTPUTF8
> is enabled, but a query is not valid UTF8.
>
> - The one in plpgsql_connect_single() sets the PgSQL client encoding
>
