Re: [pgAdmin4][Patch] - Encoding Fixes

From: Dave Page <dpage(at)pgadmin(dot)org>
To: Khushboo Vashi <khushboo(dot)vashi(at)enterprisedb(dot)com>
Cc: pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: [pgAdmin4][Patch] - Encoding Fixes
Date: 2019-02-27 11:27:25
Message-ID: CA+OCxozDGvyVC6gGTyyBU-kK_Pk=tV2wsHcdNZeoV6=qLB+suw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

Hi

On Tue, Feb 26, 2019 at 9:01 AM Khushboo Vashi <
khushboo(dot)vashi(at)enterprisedb(dot)com> wrote:

> Hi,
>
> Please find the attached patch to fix the encoding related issues.
>
> #3992 - View data causes errors with DB encoding EUC_JIS_2004
> #3982 - Encoding Problem with PGAdmin 4.2
> #3911 - Data output does not display Arabic in WIN1256 encoding database
> - The CSV download for the same encoding has also been fixed.
>
> I have tested the patch on Python 2.7, 3.5, 3.6 and 3.7.
>

You've added a couple of new encodings, but it seems to me that we should
just add everything that PostgreSQL supports. For example, we now have
win1256, but what about 866, 874, 1250, 1251 etc?

The full list is at https://www.postgresql.org/docs/11/multibyte.html

Any reason not to do that?

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Dave Page 2019-02-27 13:39:52 pgAdmin 4 commit: Fix support for bigint's in JSONB data. Fixes #3587
Previous Message Dave Page 2019-02-27 11:00:43 Re: Result grid rendering (was: Re: [pgAdmin4][Pattch] - RM #3673 - "Download as .csv" F8 does NOT work when one of joined files is a TEMPORARY file)