[Octave-bug-tracker] [bug #34661] Confusing documentation for transpose operator: `x.''

[Rik]

Follow-up Comment #12, bug #34661 (project octave):

>>Is there a reason to not have @xcode{} simply expand to @code in all formats
except Info?

I don't think so, which is why I prefer the @tex/@ifnottex construction over
@verb because it uses the @code macro where it can.  I suppose it would be
even better to use @ifinfo/@ifnotinfo since that is more specific.

The bolding is not true bolding, but rather the effect of @code in the pdf
output for my machine.  The glyphs of the fixed width font chosen by @code
have heavier serifs and make the code segment seem slightly bold with respect
to the thinner serifs of ordinary text.

Here is my stab at the required macro.  It is almost right, however the
expansion always adds a space after the end of the macro in the Info output. 
This means to use it the word following the macro has to abut the closing
curly brace.  It looks a little weird and it doesn't allow for having @xcode
at the end of the sentence because a space would be inserted before the
period.  If someone is handier with Texinfo maybe they can figure out how to
do better.


@c The following macro works around a situation where the Info/plain text
@c expansion of the @code{XXX} macro is `XXX'.  The use of the apostrophe
@c can be confusing if the code segment itself ends with a transpose
operator.
@macro xcode {arg}
@ifinfo
arg
@end ifinfo
@ifnotinfo
@code{arg}
@end ifnotinfo
@end macro


Sample usage:


code 1 is @xcode{XXX}and code 2 is @xcode{YYY}



    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?34661>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/