summaryrefslogtreecommitdiff
path: root/src/include
diff options
context:
space:
mode:
authorJohn Naylor2021-08-26 14:06:12 +0000
committerJohn Naylor2021-08-26 14:06:12 +0000
commit1563ecbc1be8b8e5c57651cf5c87f90dea9aea8f (patch)
tree352dc9c770ec3e66279b7cd6b26c08097e08c0e3 /src/include
parentf8c8a8bccc23f6ca38f7a92c9a614e73fa1fcfb6 (diff)
Revert "Rename unicode_combining_table to unicode_width_table"
This reverts commit eb0d0d2c7300c9c5c22b35975c11265aa4becc84. After I had committed eb0d0d2c7 and 78ab944cd, I decided to add a sanity check for a "can't happen" scenario just to be cautious. It turned out that it already happened in the official Unicode source data, namely that a character can be both wide and a combining character. This fact renders the aforementioned commits unnecessary, so revert both of them. Discussion: https://www.postgresql.org/message-id/CAFBsxsH5ejH4-1xaTLpSK8vWoK1m6fA1JBtTM6jmBsLfmDki1g%40mail.gmail.com
Diffstat (limited to 'src/include')
-rw-r--r--src/include/common/unicode_combining_table.h (renamed from src/include/common/unicode_width_table.h)2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/include/common/unicode_width_table.h b/src/include/common/unicode_combining_table.h
index 3a02ed5c626..a9f10c31bc8 100644
--- a/src/include/common/unicode_width_table.h
+++ b/src/include/common/unicode_combining_table.h
@@ -1,4 +1,4 @@
-/* generated by src/common/unicode/generate-unicode_width_table.pl, do not edit */
+/* generated by src/common/unicode/generate-unicode_combining_table.pl, do not edit */
static const struct mbinterval combining[] = {
{0x0300, 0x036F},