[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
I would suggest that the more general <varname> be considered as well; I'm working on a filesystem project where variable expansion in path names will be a key component. <varname> seems like a sufficiently general-purpose element to be considered for smallcptr.char.mix. -John Daily jdaily@progeny.com > / 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? > > Be seeing you, > norm > > -- > Norman Walsh <ndw@nwalsh.com> | A hen is only an egg's way of > http://www.oasis-open.org/docbook/ | making another egg.--Samuel Butler > Chair, DocBook Technical Committee | (II)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC