Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mGmWg-0002co-OG for pgsql-hackers@arkaria.postgresql.org; Thu, 19 Aug 2021 18:12:26 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mGmWf-00056j-Gv for pgsql-hackers@arkaria.postgresql.org; Thu, 19 Aug 2021 18:12:25 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mGmWe-00056b-Ja for pgsql-hackers@lists.postgresql.org; Thu, 19 Aug 2021 18:12:25 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mGmWZ-00044L-Fj for pgsql-hackers@postgresql.org; Thu, 19 Aug 2021 18:12:23 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id EC7AF5C00F8; Thu, 19 Aug 2021 14:12:15 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Thu, 19 Aug 2021 14:12:15 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=6j2NNqPAO3UgRKCpTGkDQgBEC2Jov/FNBhVGKCl9H dM=; b=DBH7ABK7bscUhhsFeHvmLBw5hobLzH3ALRbYKlsnlE2tgKNzJ46NJ81Tx J+8Ru8T77g+M/7mNl3j8GgYIaMJ38Co5FwgN4cXxjWJcnCFbbMyC60UZ7fvIK02U 2QDi5ys61Za6ol//2bIrkPXlbh6lp1y218dB+r/AH1eWEY57pDEx2ue/jBtyN9dE MJXO+mL+90h7W53YkpK8rtqxlYPyMBqPmrsXzdTUdRZRBpSSVR9zO0R/Hj/r/5+e 6mfaYooDTUQHF/UquNkc9Qdn80+2eBtXRpnBW2mAtzW2+w6S9VKePD7QsCTyOy8L Gg7tXufGkrdfs6X2uPeH9A0zm/SPg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrleejgdduudelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepuffvfhfhkffffgggjggtgfesthekredttdefjeenucfhrhhomheprfgvthgv rhcugfhishgvnhhtrhgruhhtuceophgvthgvrhdrvghishgvnhhtrhgruhhtsegvnhhtvg hrphhrihhsvggusgdrtghomheqnecuggftrfgrthhtvghrnhepkeehieehvdegueeghfff ueeliedvgfeigffhheevvdegfefgfeetgeejudejjeehnecuvehluhhsthgvrhfuihiivg eptdenucfrrghrrghmpehmrghilhhfrhhomhepphgvthgvrhdrvghishgvnhhtrhgruhht segvnhhtvghrphhrihhsvggusgdrtghomh X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 19 Aug 2021 14:12:12 -0400 (EDT) Subject: Re: badly calculated width of emoji in psql To: John Naylor , Jacob Champion Cc: "michael@paquier.xyz" , "pavel.stehule@gmail.com" , "laurenz.albe@cybertec.at" , "pgsql-hackers@postgresql.org" , "horikyota.ntt@gmail.com" References: <9e3c847108bac6041f50e86d08d8835f5cf7cd78.camel@vmware.com> <2f7ca10c7847f69267685beca7b5aa92dd876259.camel@vmware.com> <27788f6c85b9485c3dd845875a3fdc285560c8d9.camel@vmware.com> From: Peter Eisentraut Message-ID: <49ad1fa0-174e-c901-b14c-c484b60907f1@enterprisedb.com> Date: Thu, 19 Aug 2021 20:12:10 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 16.08.21 22:06, John Naylor wrote: > Peter, does the combining char table exclude values > 0xFFFF for size > reasons, correctness, or some other consideration? I don't remember a reason, other than perhaps making the generated table match the previous manual table in scope. IIRC, the previous table was ancient, so perhaps from the days before higher Unicode values were universally supported in the code.