Re: typos
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Amit Kapila <amit.kapila16@gmail.com>
Cc: Justin Pryzby <pryzby@telsasoft.com>, pgsql-hackers@lists.postgresql.org
Date: 2023-01-03T08:41:58Z
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
Commits
-
Fix various typos in code and tests
- ef7002dbe0b0 16.0 landed
-
Fix typos in code and comments
- 5f6401f81cb2 16.0 landed
-
Remove function declarations from headers for some undefined functions
- 69fb29d1affb 16.0 landed
-
Fix typos in comments, code and documentation
- a80740a7c979 11.19 landed
- dfaa705ce423 12.14 landed
- 1c89549ca48d 13.10 landed
- e373e5578bc3 14.7 landed
- c772dfe07a9d 15.2 landed
- 33ab0a2a527e 16.0 landed