Revision of several documentation pages

[hoppfrosch]

This pull request contains a revision on several documentation pages.

Main topics:

• Consistent Use of kbd-css
• Enhanced Anchors and links
• Consistent notation on several Topics (for example: Paste Mode <-> Paste mode <-> paste mode)
• Small reorganizations
• More smaller enhancements

[aviaryan]

I have merged it but there were several problems in this pull I saw later - In basic_help.html, pastemd is linked as < a href=pastemd>. It should be <a href=#pastemd> for things to work. Same for action mode <a href=actionmd>. Also make sure that some thing like <a name=actionmd> for the link to work.

+ is no key in paste mode. Pressing 5 will itself advance the clip position. Only the -(minus) key is required to change the sign. Link

I will correct these issues myself this time.

[hoppfrosch]

Sry for my negligence with this merge request - to much monotonous changes. Should have tested it more thoroughly. I hope you like it anyway .... In case of happening again, please report those things and I will fix it - so you've got less work in the end ...

[aviaryan]

Thank you for your pull requests. That separate shortcuts page was a very good idea... I hope to release a build soon... For future pulls, I will try to be more careful before merging them to the mainstream.

[aviaryan]

keyscss doesn't work with IE and hence clipjump.chm for the Channels page. See this issue. https://github.com/michaelhue/keyscss/issues/3 Do you have any idea ?

[hoppfrosch]

Sorry for the late answer - was on vacation for a few days.

Concerning the problems with michaelhue/keyscss#3 I don't have any clue yet. I simply took the style and used it.

As I see you already fixed it by replacing the keys.css. That's what I would have done as well. Is there still any action needed from me in this issue?

[aviaryan]

It's OK :+1: . IE has tons of incompatibility problems and no one seems to know the way around. I just thought you had some experience with the keys.css and so asked you. It's good we now have the solution.

[hoppfrosch]

Just for information: I tried to separate [kbd] and [kbda] on base of your solution by simply duplicating your solution (To have an optical difference between pressing and releasing a key - see https://github.com/hoppfrosch/Clipjump/commit/3161595c72781de70ac5917a33febf5a3f9da4b0)

But this does not work. What I did then was introducing a class [kbd.inverse] for the [kbd]-Selector (see: https://github.com/hoppfrosch/Clipjump/commit/3161595c72781de70ac5917a33febf5a3f9da4b0)

With this solution it looks fine - at least what I have seen ...

[aviaryan]

Yes, now IE seems to show it correctly. I tested the channels.html from your docu branch. BTW, what's with Google chrome now. It's shows a white boundary on black (pressed) keys.

[hoppfrosch]

I think that's part of the current css solution and therefore the same with unpressed keys (white boundary) - but a grey light is used, so one cannot distinguish between light grey and white border.

I will have a more detailed look on the CSS to avoid such borders .... (unless I'm mostly a CSS noob)

[aviaryan]

Interestingly in IE, basic_help.html shows white borders for black buttons and channels.html shows pure black buttons.
I will comment on your other pull request later.