R. Bernstein

When doing something that makes massive changes like this, here is a technique I use that helps. First try this on a small example, and check it very carefully. Here...

@mmatera - this fills in some of the ideas from a while ago where there was confusion over formatting output. To start out with this PR just is handling Infix...

> @rocky, Encoding seems to be something at the level of the conversion of a box expression to a string ("boxes_to_string" functions), in order to have an encoding independent evaluation....

I'd like to clarify my purpose in doing this PR draft. The main goal here was to start steering work back to the area where it belongs. Historically, initially there...

> @Rock, also notice that locally, I found problems with > > ``` > make clean && make doc > ``` > > because the tests do not pass. Did...

> > Maybe this would be useful: in .m files, all the strings are translated to the ASCII representation, using escaped NamedCharacters. The same happens if you pass a string...

I make the copy and am currently running a "make doc". That reminds me of one _other_ thing that we have been glossing over that in the future we will...

> This is why I wonder if it makes sense to use the specific table for converting operators in the output. It would be simpler to translate them just as...

> > > > No, the problem is this one: the reference output is not encoded. For example, > > ``` > (pystonmathics) mauricio@mauricio-T15thinkpad:~/Projects/mathics-core$ make doc > (cd mathics/doc/latex &&...

> > > This is why I wonder if it makes sense to use the specific table for converting operators in the output. It would be simpler to translate them...