There is a warning in the psql console about character encoding that doesn't match the system encoding. Some Windows machines still use the legacy 1252 that may not support all utf-8 character encoding.
The warning from the psql console
WARNING: Console code page (850) differs from the Windows code page (1252). 8-bit characters might not work correctly. See psql reference page "Notes for Windows users" for details.
Recommended Solution
Set the Windows character encoding from 1252 to utf-8
Not Recommended Solution
Set the character encoding in psql to 1252 (This may be setting the psql to use a legacy character encoding)
Some suggested solutions online don't persist after the terminal restart
client_encoding is already in UTF8 in psql but this doesn't solve the issue (I think the system and psql encoding need to match)
SHOW client_encoding;
client_encoding
UTF8
(1 row)
- [Checking the Beta `UTF-8` support on windows solved the issue](https://stackoverflow.com/questions/57131654/using-utf-8-encoding-chcp-65001-in-command-prompt-windows-powershell-window)
Checking the system info with `[System.Text.Encoding]::Default`
System info before the checkbox is checked
```bash
IsSingleByte : True
BodyName : iso-8859-1
EncodingName : Western European (Windows)
HeaderName : Windows-1252
WebName : Windows-1252
WindowsCodePage : 1252
IsBrowserDisplay : True
IsBrowserSave : True
IsMailNewsDisplay : True
IsMailNewsSave : True
EncoderFallback : System.Text.InternalEncoderBestFitFallback
DecoderFallback : System.Text.InternalDecoderBestFitFallback
IsReadOnly : True
CodePage : 1252
System info after the checkbox is checked (all 1252 changed to utf-8 and its 65001 number equivalent)
Related to https://github.com/upleveled/system-setup/issues/76
There is a warning in the
psql
console about character encoding that doesn't match the system encoding. Some Windows machines still use the legacy1252
that may not support allutf-8
character encoding.The warning from the
psql
consoleRecommended Solution
1252
to utf-8Not Recommended Solution
1252
(This may be setting the psql to use a legacy character encoding)Some findings
client_encoding
is already in UTF8 in psql but this doesn't solve the issue (I think the system and psql encoding need to match)client_encoding
UTF8 (1 row)
System info after the checkbox is checked (all 1252 changed to
utf-8
and its65001
number equivalent)Conversation in https://github.com/upleveled/system-setup/pull/80 about this
https://github.com/upleveled/system-setup/pull/80/commits/60ddd090753fefa7b956e4c13eed5d9863a3efcc#r1668603246 https://github.com/upleveled/system-setup/pull/80/commits/60ddd090753fefa7b956e4c13eed5d9863a3efcc#r1674257929