This is the mail archive of the
docbook@lists.oasis-open.org
mailing list for the DocBook project.
Re: Environment Variables in File/Directory Names
- From: Karl Eichwalder <ke at gnu dot franken dot de>
- To: Norman Walsh <ndw at nwalsh dot com>
- Cc: docbook at lists dot oasis-open dot org
- Date: Mon, 03 Dec 2001 19:54:56 +0100
- Subject: DOCBOOK: Re: Environment Variables in File/Directory Names
- References: <Pine.LNX.4.21.0111211536020.28721-100000@miami.datech2.er.heitec.net><87vgg4uqi4.fsf@nwalsh.com> <shg06s9693.fsf@tux.gnu.franken.de><87lmgk8tad.fsf@nwalsh.com>
- Reply-to: Karl Eichwalder <keichwa at gmx dot net>
Norman Walsh <ndw@nwalsh.com> writes:
> Sorry, I should have been more clear. In my experience, the
> distinction isn't often important.
All the markup we're doing isn't important -- contents count! ;)
> I haven't used systems that automatically put the leading $ on envars
> or anything and the principal value in marking them up was for
> searching.
I saw it in books done with LaTeX.
> A user searching for the "FOO" envar is probably interested in both
> FOO and $FOO (provided the FOO in question is an environment
> variable).
Sure, you are not wrong! Automatic indexing is another reason to use
<envar> or <literal role="envar">.
--
ke@suse.de (work) / keichwa@gmx.net (home): |
http://www.suse.de/~ke/ | ,__o
Free Translation Project: | _-\_<,
http://www.iro.umontreal.ca/contrib/po/HTML/ | (*)/'(*)