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
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.
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
>
Hello Paul,
Monday, May 9, 2016, 12:08:27 AM, you wrote:
> My preference would be the second variant (2 - 2 - 2), where no ToC
> has more than 2 levels and section ToCs are single-level. Since each
> top-level section has its own page, having a multilevel ToC at the
> top is not very useful
Hello Mark,
> > - toc.section.depth
> >determines the deepest section level that can appear in a ToC
> >
> > - toc.max.depth
> >determines the maximum depth (= number of levels) in any ToC
> >
> > - generate.section.toc.level
> >determines up to (or rather down to) which section level
On 8-5-2016 03:32, Paul Vinkenoog wrote:
> Hi all,
>
>>> I will look into the TOC issue this week. IIRC (it's been a while since
>>> I did any extensive work on the transformation stylesheets) TOCs are
>>> relatively easy to add and configure.
>
> Presence and appearance of ToCs in the output are
Hi all,
> I will look into the TOC issue this week. IIRC (it's been a while since
> I did any extensive work on the transformation stylesheets) TOCs are
> relatively easy to add and configure.
OK, that turned out to be infeasible from my holiday address, with a
half-broken laptop and a limited
On 01/05/16 00:12, Paul Vinkenoog wrote:
> I will look into the TOC issue this week. IIRC (it's been a while since
> I did any extensive work on the transformation stylesheets) TOCs are
> relatively easy to add and configure.
Paul ... I still have my own local copy of the fbwiki which provided
Hi Mark,
> I've been using the Firebird Language Reference for a while now, and I
> have some annoyances with its searchability.
8<
> In general I think the searchability of the documentation would be
> greatly improved if the TOC was three levels deep, and/or if the
> sections were
10 matches
Mail list logo
