TMFs?
Tony van der Hoff
tony at mk-net.demon.co.uk
Wed Sep 8 22:50:46 BST 2004
Stefan Bellon <sbellon at sbellon.de> wrote in message
<4ceb558d65sbellon at sbellon.de>
> Dear OSLib maintainer,
>
> I'm copying here a discussion that took place on zap-devel regarding
> the OSLib StrongHelp manual. The main problem started with the fact
> that the OSLib StrongHelp manual is not searchable from within Zap. The
> result of the discussion was ...
>
> Christian Ludlam wrote:
> > On 8 Sep Stefan Bellon wrote:
> > > Christian Ludlam wrote:
> > > > I don't think this is the only problem, but could you have a look
> > > > inside your OSLib manual and see if all the files are untyped?
> > > > Mine are, and StrongHelp only looks for files typed as Text when
> > > > it's doing an 'F1' lookup.
> > >
> > > Yes, you're right, all files inside the OSLib manual are untyped
> > > ones that have "00000000 00000000" as load and exec address instead
> > > of a filetype.
> > >
> > > Is this a "bug" regarding StrongHelp specification and should I
> > > file a bug report against it on the OSLib list or is it a problem
> > > with the StrongHelp application which you can fix?
>
> > StrongHelp deliberately only looks for Text files when doing its 'F1'
> > search, so that manual authors can provide some keywords and hide
> > other 'internal' documents. For example, inside the OS manual you can
> > look up OS_AMBControl (because it's a Text file) but not OS_areas
> > (because it's Data). All files are searched with the Freetext search.
>
> > Previous OSLib manuals had the proper type information, so presumably
> > it's a problem with their new Linux build system.
>
> Replies to oslib-user at compton.nu only, I think.
>
I've already replied on the Zap list. But, Christian's right. I'll fix it.
Away for the next couple of weeks, though.
Cheers,
--
Tony van der Hoff
Buckinghamshire England
More information about the oslib-user
mailing list