Re: kbd and similar command within code

[Patrice Dumas]

On Mon, Jul 30, 2012 at 11:09:35PM +0000, Karl Berry wrote:
> 
>     There are 2 issues, should --- -- '' `` be kept as is or should it be
>      like in code-style.  
> 
> In @r, I think the --- should be transformed into an em-dash, etc.

Ok.  It is not the case right now in tp, but it is done in makeinfo in
C.  I'll do that soon.

> The fact that the @r is inside @code (or @example) seems irrelevant to
> me.  Ditto for @i, @b, @sansserif, @slanted.  @t inside @code/@example
> should just be a no-op, I guess.  It is in TeX, anyway.

Ok.

>     And second is should there be quotes for the most inside @code?
> 
> I think: no.  Again, the nested @code doesn't seem relevant to me,
> because of the intervening @r.  What matters is that @code is (directly)
> inside @r, @r is regular text, hence @code should behave like it does in
> regular text.
> 
> The place where I can see an argument for using quotes for @code is when
> it is nested directly inside a code environment:
> 
> @code{something @code{else}}
> -> something 'else'
> 
> Or
> @example
> @code{else}
> @end example
> -> 'else'
> 
> However, I don't feel strongly about it.  Whatever behavior you have is
> ok by me, and I'd rather not document it :).  Irrelevant in practice.

I think you want it completly backward of what I just implemented,
following the manual (about kbd in code).  Indeed, what I just
implemented is something along 

  'no change in font' => no quote
  'change in font from normal text to monospace' => quotes

Which translates to @code in normal text, or in @r gets quotes, but not
when directly in @code or @example!

-- 
Pat