Keyword and Punctuator productions are an unreadable mess

[anba]

Simply removing one of to make it more readable apparently wasn't okay to do (2eb9eb2). Is it possible to layout these productions in some other way to make them more easy to read?

[bterlson]

With a quick CSS rule adding columns and word-spacing, I can achieve the following effect pretty nicely:

However, it doesn't look so nice with single-character tokens IMO:

I guess I need to find a way to make the number of columns adaptive based on width of viewport and width of contents, and keep the width fixed to alternatives line up nicely. Anyone have thoughts on how to do this?

[bterlson]

With a quick CSS rule adding columns and word-spacing, I can achieve the following effect pretty nicely:

However, it doesn't look so nice with single-character tokens IMO:

I guess I need to find a way to make the number of columns adaptive based on width of viewport and width of contents, and keep the width fixed to alternatives line up nicely. Anyone have thoughts on how to do this?

[claudepache]

@bterlson Use column-width: <min-width> together with column-count: <max-number>? (Disclaimer, I’ve not tried.)

[claudepache]

@bterlson Use column-width: <min-width> together with column-count: <max-number>? (Disclaimer, I’ve not tried.)

[bterlson]

@claudepache minimum column width isn't the constraint I want when I don't know the widths in advance. I'd want a min-width of ~20px for single characters ~20 columns, but that causes larger tokens to overflow and look horrible.

[bterlson]

@claudepache minimum column width isn't the constraint I want when I don't know the widths in advance. I'd want a min-width of ~20px for single characters ~20 columns, but that causes larger tokens to overflow and look horrible.