[latexrefman] Add Arrows subsection

[Hefferon, Jim S.]

> I put the lasy definitions into common.texi

Thank you, that is a real improvement to have the symbols in the .pdf.  I had no idea where to put it.

> It occurred to me that it might be nice to show the Unicode code point
(as textual information) even when the character is output

I'm not opposed but I always have in mind an intermediate LaTeX user and I'm not so sure how they would use that information.   Maybe I just have in mind an American LaTeX user.  :-)

> I also wondered about stating "must load latexsym" for the lasy symbols,
but failed to do it.

I intended to do that.  May take a couple of days to get done.

> Also some problem with "Declaration" and "Terminal input/output"

Yeah, there is someting weird there.  If I do svn update then it restored my .html files for this:

ftpmaint at millstone:~/Documents/latexrefman/trunk$ svn update
Updating '.':
Restored 'latex2e-help-texinfo-tree/latex2e/Terminal-input_002foutput.html'
Restored 'latex2e-help-texinfo-tree/latex2e/terminal-input-slash-output.html'
U    latex2e.texi
U    ChangeLog
U    src/easyurls.py
U    aspell.en.pws
U    common.texi
 U   .
Updated to revision 730.

Dunno what that is about.  Just figured I offended svn in some way.

Jim

----------
Give Truth a Chance.

________________________________________
From: latexrefman <latexrefman-bounces+jhefferon=smcvt.edu at tug.org> on behalf of Karl Berry <karl at freefriends.org>
Sent: Tuesday, November 13, 2018 6:34:58 PM
To: latexrefman at tug.org
Subject: Re: [latexrefman] Add Arrows subsection

I put the lasy definitions into common.texi (taking the math classes
from latexsym.dtx) and used the characters in the math symbols list.
Seemed to work ok. (I did not bother to commit new pdf/etc., though,
since I knew that would happen soon enough anyway.) Thanks for doing the
work.

It occurred to me that it might be nice to show the Unicode code point
(as textual information) even when the character is output, as in the input
  @BES{2135,\aleph} Aleph, transfinite cardinal (ordinary).
would produce
  \aleph  <alephchar> (U+2135) Aleph, trans ...

where the (U+xxxx) string is new. Wdyt? I'm not sure, but more
information seems better than less information? Overall, probably all
occurrences of @BES[U] need to be reviewed anyway for lacking control
sequences, random use when not needed in Texinfo, etc.

I also wondered about stating "must load latexsym" for the lasy symbols,
but failed to do it. (Didn't try it, but that's what latexsym.dtx says.)

I noticed there is a bug in (it seems) texinfo.tex resulting in
l.1466: Undefined cross reference `\accent-snt'.
and a few others (with texinfo.tex 2018-09-21.20). Looks like it happens
with commands that are already defined (\accent, \smash, \wlog, etc.).

Also some problem with "Declaration" and "Terminal input/output" (index
entries?).

I'll look into them sometime. Sigh. --thanks, karl.