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

[Nik Clayton <nik@nothing-going-on.demon.co.uk>]

On Fri, Jan 12, 2001 at 08:10:21AM -0500, Norman Walsh wrote:
> / 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?

I've just gone through the rest of the FreeBSD documentation set --
that's the only thing that will bite us in <filename> (I'm transitioning
our DTD customisation from 3.1 to 4.1).  The requirement now for
<segtitle> in <segmentedlist> was a surprise, but I can handle that.

Looking through the DTD at everything else that uses smallcptr.char.mix,
I suppose it's feasible that <prompt> might need it as well.  Do you
want me to submit an RFE requesting that <envar> be added back?

N
-- 
Internet connection, $19.95 a month.  Computer, $799.95.  Modem, $149.95.
Telephone line, $24.95 a month.  Software, free.  USENET transmission,
hundreds if not thousands of dollars.  Thinking before posting, priceless.
Somethings in life you can't buy.  For everything else, there's MasterCard.
  -- Graham Reed, in the Scary Devil Monastery