Re: [pgAdmin4][Patch] - Encoding Fixes
| От | Dave Page |
|---|---|
| Тема | Re: [pgAdmin4][Patch] - Encoding Fixes |
| Дата | |
| Msg-id | CA+OCxozDGvyVC6gGTyyBU-kK_Pk=tV2wsHcdNZeoV6=qLB+suw@mail.gmail.com обсуждение исходный текст |
| Ответ на | [pgAdmin4][Patch] - Encoding Fixes (Khushboo Vashi <khushboo.vashi@enterprisedb.com>) |
| Ответы |
Re: [pgAdmin4][Patch] - Encoding Fixes
|
| Список | pgadmin-hackers |
Hi
On Tue, Feb 26, 2019 at 9:01 AM Khushboo Vashi <khushboo.vashi@enterprisedb.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
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
В списке pgadmin-hackers по дате отправления: