Re: handling of absolute source file paths

["Eli Zaretskii" <eliz@gnu.org>]

> Date: Sat, 1 May 2004 19:14:20 +0200
> From: Baurjan Ismagulov <ibr@ata.cs.hun.edu.tr>
> 
> On Wed, Apr 21, 2004 at 08:51:55AM +0200, Eli Zaretskii wrote:
> > Note that it doesn't specify what happens if the file's name starts
> > with a slash or otherwise has leading directories.  It would be good
> > to augment the manual with a more explicit description of cases such
> > as yours.  Would you like to do that?
> 
> I've tried to do that.

Thanks.

> I've removed a paragraph that seemed no longer
> relevant. Please review.

A few minor comments, and then the patch can go in:

> +For example, suppose an executable references the file
> +@samp{/usr/src/foo-1.0/lib/foo.c}, and our source path is

First, file names should have the @file markup, not the @samp markup.

>                  The subdirectories of source path directories or
> +parts of the source pathname are not looked up.

Please say "source file name", not "source pathname".  The GNU
project documentation does not use the term ``pathname''.

Also, this specific sentence is not very clear; perhaps an example
using the file names and the source path from your example would help
understand it better.

>  Plain filenames,
> +relative pathnames, pathnames with dots, etc. are all treated as
> +described above.

Please add a ``@:'' after ``etc.'', so that TeX would not typeset
that as an end of a sentence.