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

[Rik]

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

JWE, you may be able to re-define the @code{} macro somewhere in texinfo.tex
in the directory above doc/interpreter.  However, I see this as a specific
problem with the transpose operator and not a general problem of getting @code
to change its ways based on what is inside the macro.

For reference, there are 9 occurrences of a transpose operator at the end of
an @code{} macro.  I'm lazy and would just change these occurrences rather
than fighting with Texinfo.  My 2 cents.


expr.texi:640:@code{x'}.
expr.texi:783:@code{x.'}.
linalg.texi:826:then a factorization of @address@hidden@address@hidden'} can
be obtained
linalg.texi:1262:@address@hidden * @var{TR} * @var{UR}' = @var{U} * @var{T} *
@var{U}'} and
linalg.texi:1431:such that @code{a*u == u*h+rk*ek'}, in which @code{rk =
linalg.texi:1432:a*u(:,k)-u*h(:,k)}, and @code{ek'} is the vector
sparse.texi:709:@address@hidden@var{A}'} if @var{A} in not symmetric.  The
optional
sparse.texi:1762:Factorize @address@hidden * @var{S}'}.
sparse.texi:1765:Factorize @address@hidden'}



    _______________________________________________________

Reply to this item at:

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

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