This template is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing
I can't add non-linked text or redlinks to the template, that's why I created pages about 4 missing keys. Do you have any good source of information about these keys? --Michaelas1008:52, 6 October 2006 (UTC)[reply]
I don't intend to pursue this with any enthusiasm if there is a dispute, but I have a few comments in reply to the Edit summary by User:Dispenser who reverted my changes.
While it is true that the style I used is more appropriate for the monobook skin than other skins, monobook is nevertheless the default skin, as seen by those not logged into an account (the vast majority of wikipedia users) and therefore, statistically speaking, it is more appropriate to use styles suited for the monobook skin.
I appreciate that NavBoxes may have their own style. Although I support standardisation, there is no such policy, so where disputes arise on whether a NavBox looks better or worse, I will not argue.
I do not understand what you mean by "regression in terms of syntax"
Much of issue I had was how you did it, not what you did. For instance: If the built in class then the skinning issue wouldn't be a problem. The following are issues I had taken with you edit:
CSS issue:
Hard code styles. You hard coded too much style information when it would be better and easier to use class="navbox" which contains nearly all of the information.
HTML issues:
Unquote of attributes (Hint: everything needs to be quoted).
Converting CSS styles to deprecated HTML attributes. BGCOLOR, ALIGN, WIDTH were deprecated in the HTML 4 spec.
I've gone ahead and used {{navbox generic}}; the syntax is much easier to read, and it now uses the same style as most other navboxes around Wikipedia. I shrunk the width to keep it vaguely the same shape as it was previously, but you can pull out "style = width: 75%" to make it span the page width, and add "color = #6CF;" to change back the titlebar color. grendel|khan16:13, 19 February 2007 (UTC)[reply]
This part of the template looks really strange to me.
Dead key is not a logical title for a topic heading, nothing sensible can be nested under it. It itself should be an item under 'Modifier keys'. It could argued that 'modifier' is ruled out because it is not used simultaneously with another key (as in `+a but it certainly modifies the following letter: `a to prooduce à.
Compose key is not a dead key any more than Caps Lock is. It is a kind of lock key in that it controls the following inputs until the desired character is produced: unlike the major lock keys it doesn't need to be released.
Mix-up between Command key (Apple), Windows key and Super key.
In the template there is a slash between the Command key and the Windows key.
It is a common misconception that they are related, due to modern misuse of modifier keys (esp. the Ctrl key which is used nothing like it's purpose).
The Windows Key is mainly a re-branding of the Super key (as is said in the first paragraph of the Super key's article).
--GoodClover (talk) 15:40, 9 January 2021 (UTC)[reply]
Add "standards" section.
There are various standards such as ISO/IEC 9995 which detail keyboard layouts and how some modifier keys are used, such as the Shift key.
I think it would be good to have these on this either in a "standards" section or in the current "concepts" section.
--GoodClover (talk) 15:45, 9 January 2021 (UTC)[reply]