This is the mail archive of the
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.firstname.lastname@example.org><email@example.com> <firstname.lastname@example.org><email@example.com>
- Reply-to: Karl Eichwalder <keichwa at gmx dot net>
Norman Walsh <firstname.lastname@example.org> 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
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
Sure, you are not wrong! Automatic indexing is another reason to use
<envar> or <literal role="envar">.
email@example.com (work) / firstname.lastname@example.org (home): |
http://www.suse.de/~ke/ | ,__o
Free Translation Project: | _-\_<,
http://www.iro.umontreal.ca/contrib/po/HTML/ | (*)/'(*)