Re: Misleading "For more information..." placement

2023-03-27 Thread Daniel Gustafsson
> On 27 Mar 2023, at 17:04, Randall Sindlinger wrote: > Fantastic! I'm rather used to things just going off into the ether. > I know I've > seen minor things before, so next time I notice one, I'll send it in. Please do, postgres is made by the community and no report is too small to be valuabl

Re: Misleading "For more information..." placement

2023-03-27 Thread Randall Sindlinger
>On Sun, Mar 26, 2023 at 5:18 PM Daniel Gustafsson wrote: > > > I'd suggest moving that last sentence to > > immediately after the first sentence, which ends with "...when the database > > is created." > > I think sentence with the link is better at the end, how about if we reword it > slightly to

Re: Misleading "For more information..." placement

2023-03-26 Thread Daniel Gustafsson
> On 25 Mar 2023, at 16:43, PG Doc comments form wrote: > The final sentence ("For more information refer to Section 24.3") is easily > read to refer to more information being available about character code zero > (NUL). However, section 24.3 has no mention of NUL, but rather the > available dat

Misleading "For more information..." placement

2023-03-25 Thread PG Doc comments form
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/15/datatype-character.html Description: In the paragraph > The characters that can be stored in any of these data types are determined by the database character set, which is selected when