aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/mb/Unicode/convutils.pm
diff options
context:
space:
mode:
authorHeikki Linnakangas <heikki.linnakangas@iki.fi>2016-11-30 14:53:57 +0200
committerHeikki Linnakangas <heikki.linnakangas@iki.fi>2016-11-30 14:53:57 +0200
commit2c09c93ce1b80a417b7c372c43f5089c0d691749 (patch)
tree0e8b15d6c3bedd63e2c889ae9ea53f9053f8fb66 /src/backend/utils/mb/Unicode/convutils.pm
parentb2cc748b09456ea24cdd00a7691ce33db9a1af45 (diff)
downloadpostgresql-2c09c93ce1b80a417b7c372c43f5089c0d691749.tar.gz
postgresql-2c09c93ce1b80a417b7c372c43f5089c0d691749.zip
Remove code points < 0x80 from character conversion tables.
PostgreSQL treats characters with < 0x80 leading byte as plain ASCII, and they are not even passed to the conversion routines. There is no point in having them in the conversion tables. Everything in the tables were direct ASCII-ASCII mappings, except for two: * SHIFT_JIS_2004 code point 0x5C (backslash in ASCII) was mapped to Unicode YEN SIGN character. * Unicode 0x5C (backslash again) was mapped to "REVERSE SOLIDUS" in SHIFT_JIS_2004 These mappings never had any effect, so there's no functional change from removing them. Discussion: https://postgr.es/m/08e7892a-d55c-eefe-76e6-7910bc8dd1f3@iki.fi
Diffstat (limited to 'src/backend/utils/mb/Unicode/convutils.pm')
0 files changed, 0 insertions, 0 deletions