| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: typos |
| Date: | 2023-01-03 08:41:58 |
| Message-ID: | Y7PqVj4O4PnRsWeW@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jan 03, 2023 at 01:03:01PM +0530, Amit Kapila wrote:
> One minor comment:
> - spoken in Belgium (BE), with a <acronym>UTF-8</acronym> character set
> + spoken in Belgium (BE), with a <acronym>UTF</acronym>-8 character set
>
> Shouldn't this be <acronym>UTF8</acronym> as we are using in func.sgml?
Yeah, I was wondering as well why this change is not worse, which is
why I left it out of 33ab0a2. There is an acronym for UTF in
acronym.sgml, which makes sense to me, but that's the only place where
this is used. To add more on top of that, the docs basically need
only UTF8, and we have three references to UTF-16, none of them using
the <acronym> markup.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michail Nikolaev | 2023-01-03 08:43:54 | Re: Data loss on logical replication, 12.12 to 14.5, ALTER SUBSCRIPTION |
| Previous Message | David Geier | 2023-01-03 08:38:20 | Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc? |