Internationalization Pattern

[schanzer]

From @prestontw : each parser could call out to a separate file for aria-labels, which contains an index of all the labels for all the node-types, indexed by human language.

So new Literal(l.from, l.to, v, {aria-label: `${v}, un Numero`}) would become something like:
new Literal(l.from, l.to, v, {aria-label: `${v}, ${labels.getLabelFor("number")["Spanish"]}`})

[justinpombrio]

Two thoughts on this:

1. It's weird that this is done in the parser. I've put a function called .shortDescription() on ASTNode(). As is, it just looks up options["aria-label"]. But instead, the method could be .shortDescription(language), and everything that uses "aria-label" could instead call .shortDescription().
2. We now have pluralization, enumeration, and support for multiple languages? It might be time to adopt an actual internationalization library.

[schanzer]

In principle, ASTNodes should know how to describe themselves, since they're already responsible for rendering themselves.