Re: [StrongED] StrongHelp's Contents utility

[Fred Graute <fjgraute@xxxxxxxxx>]

In message <mpro.p1cxkm006e1nl04wi.pittdj@xxxxxxxxxxxx>
          David Pitt <pittdj@xxxxxxxxxxxx> wrote:

> Fred Graute, on 22 Dec, wrote:
> 
> > In message <mpro.p1c1y1005v0qc049l.pittdj@xxxxxxxxxxxx>
> >           David Pitt <pittdj@xxxxxxxxxxxx> wrote:
> > 
> > > Fred Graute, on 21 Dec, wrote:
> 
>  [snip PROCindex code revision]
> 
> > > > I would appreciate it if a few brave souls could give this a try with
> > > > other manuals to see if there are any problems with this change.
> > > 
> > > Tomorrow.
> > 
> > Thanks David. I'm looking forward to your findings.
> 
> I have uploaded a selection of indexed manuals to :-
> 
> http://www.pittdj.co.uk/se/SHindex.zip

Thanks David.

> The only complete failure was AppBasic with a "string too long error".

The cause is page 'AppBasic.Utils.directives.shortadrs' which consists
of a single, long line of text. Contents sees this as the page title so
tries to include in its list.

Perhaps the length of the title should be limited to something like:
256 - length of filename - 4. For the link to work we need the full
filename, and -4 for the '<=>>' part of the link.

> The results may perhaps be best described as mixed. Care is needed on page
> content and one might feel a need to edit the generated Index and Contents
> files.

Yes, going through the generated pages to make sure it's all in order
seems prudent. Although Contents does a good job there are occasions
where it can produce a spurious link.

Cheers,
Fred.

-- 
StrongED Developer
http://www.stronged.iconbar.com/

-- 
To unsubscribe send a mail to StrongED+unsubscribe@xxxxxxxxxxx
List archives at http://diy.Torrens.org/RO/StrongED/index.html