Bug 84779 - Switch default encodings to Unicode?
Switch default encodings to Unicode?
Product: Red Hat Linux
Classification: Retired
Component: postgresql (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Andrew Overholt
David Lawrence
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2003-02-21 05:41 EST by Tim Landscheidt
Modified: 2007-04-18 12:51 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-03-27 17:23:08 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Tim Landscheidt 2003-02-21 05:41:32 EST
It seems that by default the Postgresql server and frontend use the SQL_ASCII 
encoding. Given the Red Hat quest for Unicode "domination" :-), wouldn't it be 
better to switch defaults to Unicode? 
Besides, a utf-8 terminal and a psql using SQL_ASCII encoding do not get along 
very well :-(. 
- Switch initdb's default encoding to Unicode. 
- For psql, either: 
  - have a /etc/skel/.psqlrc with "\encoding utf-8" (does not affect existing 
users :-() 
  - add some magic to psql to determine whether the controlling tty has 
Unicode capability and set encoding accordingly (quick hack: check if LANG 
ends with ".UTF-8"?)
Comment 1 Andrew Overholt 2003-03-04 11:44:25 EST
I will think about this.  Thanks for the suggestions.
Comment 2 Andrew Overholt 2003-03-27 17:23:08 EST
For the time being (to maintain regression test passes, among other reasons), I
am going to keep the default encoding the way it is.  Client encoding can be
changed in dotfiles as you suggest.  Databases can be initialized with other
default encodings using `initdb --encoding=<encoding> -D <location of data

Note You need to log in before you can comment on or make changes to this bug.