Hi all,
> So for now, let's take the most conservative approach and apply this
> change to the multi-page HTML build of the refdocs set only (i.e.
> LangRef and LangRefUpds) and leave everything else untouched.
I've committed the changes.
Cheers,
Paul
---
Hi Helen,
>> PDF is very different and already has the navigation pane, so local
>> ToCs are probably less useful there. However, we can do it if we want.
>> I've added a PDF with chapter ToCs to the above page as an example.
>
> Actually, the PDF bookmarks do the job efficiently, without resortin
Hello Paul,
Wednesday, May 11, 2016, 1:03:39 AM, you wrote:
> Helen wrote:
> But notice that the (local) changes I made only apply to multipage HTML.
> Of course we can do the same for monohtml (as you use for the rlsnotes),
> but we can also leave that build as-is or make other adjustments.
I'
Helen wrote:
>> My preference would be the second variant (2 - 2 - 2), where...
> I prefer the second version too. It uses a bit more real estate but
> it means one doesn't have to keep reverting to the top-level TOC if
> browsing for a specific function while not knowing exactly the one you
> w
Helen Borrie wrote Wed, 27 Apr 2016 03:17:00 +0300:
Hello, Helen
I would like to say a few errors in the description of Operator Precedence.
Common Language Elements->Expressions->SQL Operators->Operator Precedence
1. Arithmetic Operators. Among the arithmetic operators of places without
una
