Re: Adding visual clues that accesskey exists

2023-01-20 Thread Corey Huinker
On Fri, Jan 20, 2023 at 6:07 AM Peter Eisentraut < peter.eisentr...@enterprisedb.com> wrote: > On 18.01.23 22:49, Corey Huinker wrote: > > Attached is a patch to add the nav- tags to the header (could just as > > easily have done the footer) for up/down/left/right and the j

Re: Adding visual clues that accesskey exists

2023-01-18 Thread Corey Huinker
> > I agree that hot key discoverability could be better, but I don't think > this is an issue in the PostgreSQL documentation; it's something the > browser should handle. The job of the HTML markup is to declare the key > -- then it's up to the browser how to present it. Otherwise, every > singl

Adding visual clues that accesskey exists

2023-01-13 Thread Corey Huinker
Today I discovered that we already have accesskey support for navigation of our documentation. And it's been there since at least 2007, according to the mailing list archives. I discovered this accidentally, because I was researching something and just instinctively hit the right arrow in the vain

Re: Additional Chapter for Tutorial

2020-04-17 Thread Corey Huinker
> > I plan to extend over time the part 'Tutorial' by an additional chapter > with an overview about key design decisions and basic features. The > typical audience should consist of persons with limited pre-knowledge in > database systems and some interest in PostgreSQL. In the attachment you > fi

Re: Getting our tables to render better in PDF output

2020-04-13 Thread Corey Huinker
On Mon, Apr 13, 2020 at 12:28 PM Tom Lane wrote: > Corey Huinker writes: > > I was thinking that there were references that included parameters, but > I'm > > not finding any with actual parameter values, so at most we'd lose the > "()" > > of a re

Re: Getting our tables to render better in PDF output

2020-04-13 Thread Corey Huinker
> > > I did a quick check by adding id tags to all 700-or-so s in > func.sgml (don't get excited, it was a perl one-liner that just added > random id strings). I did, actually, get excited for a second. > The runtime difference for building the HTML docs > seems to be under 1%, and negligible f

Re: Getting our tables to render better in PDF output

2020-04-12 Thread Corey Huinker
On Sun, Apr 12, 2020 at 8:38 PM Tom Lane wrote: > Corey Huinker writes: > > On Sat, Apr 11, 2020 at 6:41 PM Tom Lane wrote: > >> Is that going to be a problem for the docs toolchain? If > >> the anchors are attached to individual function names rather than > >

Re: Getting our tables to render better in PDF output

2020-04-11 Thread Corey Huinker
On Sat, Apr 11, 2020 at 6:41 PM Tom Lane wrote: > Corey Huinker writes: > > If it's ok to work on doc patches during the feature freeze, and if we're > > already tweaking function documentation, would it be possible to add in > > anchor ids to function definit

Re: Getting our tables to render better in PDF output

2020-04-11 Thread Corey Huinker
On Sat, Apr 11, 2020 at 4:51 PM Tom Lane wrote: > I set this idea aside during the final v13 commitfest, but I figure that > it's fine to work on documentation improvements during feature freeze, > so I'm going to try to push it forward over the next few weeks. If it's ok to work on doc patches

Re: Keyword BYTEA missing from Documentation Appendix C

2020-02-07 Thread Corey Huinker
I'm working on a glossary patch with an actual technical writer, so it may belong on that new page. On Fri, Feb 7, 2020 at 10:15 AM Tom Lane wrote: > PG Doc comments form writes: > > https://www.postgresql.org/docs/12/sql-keywords-appendix.html > > BYTEA missing from Keyword list. > > Is this i