| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Ralf Schuchardt <rasc(at)gmx(dot)de> |
| Cc: | Marco Lechner <mlechner(at)bfs(dot)de>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: support for DIN SPEC 91379 encoding |
| Date: | 2022-03-27 17:47:23 |
| Message-ID: | 202203271747.p2lx5is5rdtj@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 2022-Mar-27, Ralf Schuchardt wrote:
> where did you read, that this DIN SPEC 91379 norm is incompatible with UTF-8?
>
> In the document „String.Latin+ 1.2: eine kommentierte und erweiterte
> Fassung der DIN SPEC 91379. Inklusive einer umfangreichen Liste häufig
> gestellter Fragen. Herausgegeben von der Fachgruppe String.Latin“
> linked here https://www.xoev.de/downloads-2316#StringLatin it is said,
> that the spec is a strict subset of unicode (E.1.6), and it is also
> mentioned in E.1.4, that in UTF-8 all unicode characters can be
> encoded. Therefore UTF-8 can be used to encode all DIN SPEC 91379
> characters.
So the remaining question is whether DIN SPEC 91379 requires an
implementation to support character U+0000. If it does, then PostgreSQL
is not conformant, because that character is the only one in Unicode
that we don't support. If U+0000 is not required, then PostgreSQL is
okay.
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-03-27 18:06:25 | Re: support for DIN SPEC 91379 encoding |
| Previous Message | Per Kaminsky | 2022-03-27 16:30:46 | Performance issues on FK Triggers after replacing a primary column |