| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(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 list of acknowledgments to release notes |
| Date: | 2018-10-14 14:12:26 |
| Message-ID: | 9ad38164-5dfa-badd-1095-c4e0ebd968e2@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
On 14/10/2018 04:03, Tom Lane wrote:
> Oct 13, 2018 9:58:10 PM org.apache.fop.events.LoggingEventListener processEvent
> WARNING: Glyph "?" (0x144, nacute) not available in font "Times-Roman".
> Oct 13, 2018 9:58:10 PM org.apache.fop.events.LoggingEventListener processEvent
> WARNING: Glyph "?" (0x15e, Scedilla) not available in font "Times-Roman".
> Oct 13, 2018 9:58:10 PM org.apache.fop.events.LoggingEventListener processEvent
> WARNING: Glyph "?" (0x15f, scedilla) not available in font "Times-Roman".
> Oct 13, 2018 9:58:10 PM org.apache.fop.events.LoggingEventListener processEvent
> WARNING: Glyph "?" (0x131, dotlessi) not available in font "Times-Roman".
>
> I wonder how well these characters will render in different viewing
> tools. Maybe there's not much to be done, but should we entity-ify
> the list where possible?
This is not related to the encoding of these characters in the source.
It's just that we have never used these characters in previous releases
(new contributors). A workaround would be to "unaccent" the affected
names. Or look for a more complete font. Or just leave it alone.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2018-10-14 14:24:55 | Re: pgsql: Add TAP tests for pg_verify_checksums |
| Previous Message | Michael Paquier | 2018-10-14 13:26:24 | pgsql: Avoid duplicate XIDs at recovery when building initial snapshot |