Modmap: Where to put it; cancelling built-in mods (#655)

[Spike-from-NH]

Separately, is this section tight enough?

• I say that "Typically" a layout has only one modmap; should this be mandatory?
• I say the modmap is inside <keyboard> but outside any <row>. Should it be before any row?

Also: In Swipes, the boldfacing and shading of certain of the compass points suggests there is a distinction when there isn't. At most, the center cell should be highlighted. I don't know Markdown well enough to fix this.

[Julow]

I say that "Typically" a layout has only one modmap; should this be mandatory?

Currently, the second modmap would erase the first one. This should be made into an error though and should be described as such.

I say the modmap is inside but outside any . Should it be before any row?

No constraint on that.

In Swipes, the boldfacing and shading of certain of the compass points suggests there is a distinction when there isn't.

Table have a mandatory header row and this is a limitation of Github Markdown. Perhaps this can be fixed by writing a raw HTML table ?

[Spike-from-NH]

Thanks! The HTML tables look much better.

But all tables seem to have a default style of shading every other row, which is inappropriate here—It implies there's something special about w and e.

[Julow]

That's fine !