[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: DOCBOOK: <filename>'s transition to smallcptr.char.mix, 3.x -> 4.x
Norman Walsh <ndw@nwalsh.com> writes: > / Nik Clayton <nik@nothing-going-on.demon.co.uk> was heard to say: > | This means that constructs such as > | > | <para>Your ssh key pair will be placed in the > | <filename><envar>$HOME</envar>/.ssh</filename> directory.</para> > | > | which were valid in 3.x are no longer valid. > | > | Is there a recommended alternative way to mark up this sort of text? > | Wanting to mark up the environment variable, while still indicating it's > | part of a filename seems fairly natural to me. > > This may be evidence that we reduced the content model of filename > (and perhaps other elements) too far. Is there anything else that > should be allowed? Certainly <replaceable> would be useful in filenames. -- -------------------------------------------------------------------------- Thomas André Berger Open Systems Computing AS email: thomasbe@osc.no Kongensgt. 9, N-0153 Oslo, Norway phone: +47 2331 4758 phone +47 2220 4050, fax +47 22 20 02 85 -------------------- http://www.osc.no/ ----------------------------------
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC