GUACAMOLE-968: Add Norwegian keymap

[oxcrag]

No description provided.

[necouchman]

Overall looks okay to me - as with your PR on the client side:

• Addition of the Makefile entry should be in (roughly) alphabetical order.
• Pull Request and Commit Messages need the GUACAMOLE-968 tag on them.

[oxcrag]

I fixed the entry order, renamed the pull request, and the commit message for the new version of the files. Is there a way of changing the previous commit message after the fact, or will that do bad things to the pull request/version management?

[necouchman]

Is there a way of changing the previous commit message after the fact

Yes, you can do an interactive rebase, choose the option to modify the commit message, and then fix the messages. After you're done do a force push and it should be good.

[necouchman]

Also note that the correct format for both PR (which you've done properly) and commit messages is "GUACAMOLE-968: ".

[oxcrag]

I'm (slowly) getting the hang of this; thanks again! I think the requested changes are in place now.

[mike-jumper]

Sorry - jumped the gun there. The overall changes look good, but the commits should definitely be combined. If the commits embody distinct, logical changes, it would make sense to keep them, but their messages are identical:

[necouchman]

This also may need to be updated, now, to take into account changes from #285 and #287 as part of GUACAMOLE-518.

[mike-jumper]

Yep. Caps Lock will not behave correctly without the keymap dictating Caps Lock's behavior.

[necouchman]

@oxcrag This still needs to be updated to take Caps Lock changes into account.