Re: DOCBOOK: <filename>'s transition to smallcptr.char.mix, 3.x -> 4.x

From
Shomas Bndre Cerger
Date
2001-01-16T17:05:05+00:00
ID
Thread
Re: DOCBOOK: <filename>'s transition to smallcptr.char.mix, 3.x -> 4.x
Norman Walsh <> writes:

> / Nik Clayton <> 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:             Kongensgt. 9, N-0153 Oslo, Norway
 phone: +47 2331 4758		   phone +47 2220 4050, fax +47 22 20 02 85
-------------------- http://www.osc.no/ ----------------------------------