Re: GB18030-2022 Support in PostgreSQL - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: GB18030-2022 Support in PostgreSQL
Date
Msg-id 38bd5e4b-5367-423e-bd39-d7b5a84fd7a2@eisentraut.org
Whole thread Raw
In response to Re: GB18030-2022 Support in PostgreSQL  (John Naylor <johncnaylorls@gmail.com>)
Responses Re: GB18030-2022 Support in PostgreSQL
List pgsql-hackers
On 12.08.25 06:57, John Naylor wrote:
> Before getting to that, I thought I'd bring this up to the community:
> 
> +# Copyright (C) 2000-2009, International Business Machines
> Corporation and others.
> +# All Rights Reserved.
> 
> The previous XML file didn't contain a copyright notice -- does anyone
> want to make a case for not checking unicode-org's source file into
> our tree because of this? The 2022 update changes it to
> 
> # Copyright (C) 2016 and later: Unicode, Inc. and others.
> # License & terms of use:http://www.unicode.org/copyright.html
> # Copyright (C) 2000-2012, International Business Machines Corporation
> and others.
> # All Rights Reserved.
> 
> ...and the above links tohttps://www.unicode.org/license.txt

Could we download this file on demand, like we do for the other input 
files for the conversion mappings?




pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: index prefetching
Next
From: Nathan Bossart
Date:
Subject: Re: Improve LWLock tranche name visibility across backends