| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgsql: Add unistr function |
| Date: | 2021-03-31 06:30:45 |
| Message-ID: | 91389353-687d-3996-c393-877d22ea5e90@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
On 31.03.21 05:31, Tom Lane wrote:
> Peter Eisentraut <peter(at)eisentraut(dot)org> writes:
>> Add unistr function
>
> This has had negative consequences for PDF docs builds:
>
> [WARN] FOUserAgent - Glyph "?" (0x441, afii10083) not available in font "Courier".
> [WARN] FOUserAgent - Glyph "?" (0x43b, afii10077) not available in font "Courier".
> [WARN] FOUserAgent - Glyph "?" (0x43e, afii10080) not available in font "Courier".
> [WARN] FOUserAgent - Glyph "?" (0x43d, afii10079) not available in font "Courier".
>
> I'm not sure if we have a way to put Cyrillic characters in the
> docs, but if we do, this isn't it.
fixed
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2021-03-31 07:21:43 | pgsql: Add errhint_plural() function and make use of it |
| Previous Message | Peter Eisentraut | 2021-03-31 06:30:14 | pgsql: doc: Remove Cyrillic from unistr example |