Column vectors vs matrices about asciimathml HOT 6 OPEN

Yeah, I'm not sure what the docs were intending to show there. Maybe @adius can shed some light on that, as he has primarily maintains those

from asciimathml.

Any updates on this? Thanks

from asciimathml.

Mh … yeah that does not make too much sense.
I guess the docs should just talk about the visual differences between the syntaxes
and not the semantical. After all there are not really any semantical differences.
Some authors use them in different ways, but there seems to be no common consensus, right?

from asciimathml.

Either that or introduce a semantical difference (which may not break much actually, and would be a great addition in my opinion), as exposed in first comment. Use […] for row and (…) for column input.

It could be a great addition to ease programatically generating ASCIIMath.

from asciimathml.

Yeah, I like the idea, but it's not backwards compatible and might break too much code.
I don't think it's feasible…

from asciimathml.

The current doc is contradictory between the text ("matrices" and "column vectors") and the examples given.

Thus, breaking depends on the reference. If reference is the JavaScript parser on http://asciimath.org/, then, it will break. But if reference is the text from the doc, it does not break :)

Anyways, I can offer as a solution to this issue:

• To update the doc, removing the "column vectors" statement, and grouping both syntax under "matrices".
• To think about another notation that could be introduced to handle the "column vectors" properly, without any breaking changes.

from asciimathml.