Talk:Alt code

From Wikipedia, the free encyclopedia

This is the talk page for discussing improvements to the Alt code article.

Article policies

Contents

[edit] What about making a separate page with the list on it?

We could make a page called "Windows Alt keycodes list" that would contain the list, while this page just held information about it.Humphreys7 (talk) 14:22, 6 March 2008 (UTC)

Since no one has said anything on the topic, I am going to go ahead and move the table to: "Windows Alt keycodes list". Humphreys7 (talk) 14:15, 12 March 2008 (UTC)

[edit] Is this list necessary?

The alt keycode numbers are just ACSII codes for the given symbol. Is this list necessary? Jaxal1 17:56, 15 February 2006 (UTC)

Hi Jaxal1, it basically is not ASCII. I just made a complete rewrite of the article. Still, the list is no more necessary, as the correct lists can already be found on the corresponding code page article pages.
I hope the information given is correct for all versions of Windows, regardless of the language version used (I use a German XP). --Abdull 17:17, 19 February 2006 (UTC)
This is excellent. Thank you for change. Jaxal1 01:39, 20 February 2006 (UTC)


[edit] How to Type the letter, for example ü in Waldseemüller ?

For those characters whose decimal equivalent number is less than 256, below process is valid for them.
If you want to use "ü" (u with diaeresis) instead of "u", for example, like in "Waldseemüller", then use these keyboard strokes / keys :
Press "W", "a", "l", "d", "s", "e", "e", "m". Then press ...
Alt + 0252 (it means, first press the "Alt" (Alternative/Alternate) key in your keyboard, and keep on pressing it (or keep on holding it) with your left hand, then press the digits 0 2 5 2 in sequence, one by one, in the right-side numeric keypad of your keyboard, then release the Alt key).
Then press "l", "l", "e", "r".
Then you will get Waldseemüller.
To make it linkable (to goto the article,) use two third brackets at the beginning and at the end of the name, like this example, [[Waldseemüller map]], then you will get (hyper-)linkable Waldseemüller map.
If you want to link to that (English) article through URL, then use below (hex) code ...
For example, hex code "FC" stands for "ü" (its decimal equvalent is 252, and its html (decimal numerical) equivalent is ü). Use "%" symbol before the hex code, to express the "ü" character, in a URL.
http://en.wikipedia.org/wiki/Waldseem%FCller_map
or, http://en.wikipedia.org/wiki/Waldseem%C3%BCller_map
~ Tarikash.

[edit] How to type for example, Œ (Latin Ligature OE) ?

For those characters whose decimal equivalent number is above 255, the Alt + Decimal_Equivalent_Number keycodes will not work, for most characters, except few characters like, for example, € (Euro Sign, Alt+0128, Html-Dec:€, Hex:20AC), Ÿ (Latin Cap Y with Diaereesis, Alt+0159, Html-Dec:Ÿ, Hex:178), etc which are re-mapped below 255.
The decimal equivalent number of Œ is 338. Html decimal equivalent is Œ. Html hexadecimal equivalent is Œ. Hex equivalent number is 152.
To obtain Œ, open or start the Microsoft Wordpad or Word in your computer.
Press "1", "5", "2". Then press ...
Alt + x (it means, first press the "Alt" (Alternative/Alternate) key in your keyboard, and keep on pressing it (or keep on holding it) with your left hand, then press the letter x, just one time, then release the Alt key).
Then you will get Œ. Now you can copy and paste this character where you want to use it.
If you press Alt+x again, then Œ will turn back to its equivalent hex code 152. This way you can get/reveal the hex code of other special characters also. In a website, if you see/find a special character that you want to use it, either copy and paste it, or, copy-paste into Wordpad, and use Alt+X to obtain/reveal its equvalent hex code. Use chart to find its equvalent decimal code, or, use the html hexadecimal numerical equivalent code to display that character.
Few other example: for (Ohm Sign), type 3A9 Alt+x. For ∙ (Bullet Operator), type 2219 Alt+x. For ∞ (Infinity), type 221E Alt+x. For ≠ (Not Equal To), type 2260 Alt+x.
~ Tarikash.

[edit] more codes?

How many combinations are there? And how do we find them all? hehe. I was just messing around one day and found some neat ones ALT+789 = § ALT+456 = ╚ ALT+158 = ₧ ALT+154 = µ ALT+2547 = ≤ --72.146.66.200 14:08, 3 August 2006 (UTC)

Actually, the possiblities are nearly endless. Heres an example: 3跠?}?ç(?Õ?}髿疦瞯粇S6դ. You can do nearly anything. AstroHurricane001(Talk+Contribs+Ubx) 17:42, 7 January 2007 (UTC)
╔═╦═╗■┌─┬─┐
╠═╬═╣■├─┼─┤
╚═╩═╝■└─┴─┘

Examples of box making.  Razorclaw ¦ 20070419215452

[edit] The page is broken

look for 227. Thats where its broken. -IP User 22:02, 22 May 2007 (UTC)

I fixed it yesterday. The problem was "rowspan." --에멜무지로 01:35, 5 July 2007 (UTC)

[edit] Redundant tables

I think the character tables in this article are completely redundant. Character tables for the obsolete code-pages can already be found in their respective articles, Code page 437, Code page 850, and Windows-1252. A character table for the complete Unicode character set would obviously be too large. If nobody objects, I will remove these tables and replace them with links to the aforementioned articles, as well as some ideas on where to get additional character charts from (e.g. Windows character map, or unicode.org). — Timwi (talk) 14:37, 1 February 2008 (UTC)


[edit] Non-Windows Alt codes

Are there Alt codes for operating systems other than Windows? Otherwise, a merge of this article with Windows Alt keycodes may be considered. --Abdull 17:23, 19 February 2006 (UTC)

Yes, there are, but it may still make sense to merge the pages, since the differences are small. DOS supported Alt codes; so does Linux (in console mode). --217.147.80.29 12:10, 23 February 2006 (UTC)

Agree. There's nothing here that isn't provided by Windows Alt keycodes or Unicode#Input_methods. EdC 18:21, 5 March 2006 (UTC)
Hm. I've improved it somewhat; maybe the best solution would be an article on Codepoint-based Unicode input systems which this could redirect to. EdC 19:05, 5 March 2006 (UTC)

[edit] Quick Key bias

Is it really NPOV to have a comment saying that "Quick Key ... excels at ....", written by the author of that program? Perhaps a user with experience of the program might be able to provide a less biased view :-) 192.118.76.35 08:16, 22 March 2006 (UTC) I would be very grateful if you would prodvide us with a review of the software. An unbiased review would be very welcome. —The preceding unsigned comment was added by 216.135.95.189 (talk • contribs). 8 April 2006

[edit] Article title

I agree that that Codepoint-based Unicode input systems would be the most accurate title, and from an Encyclopedia point of view, this article should be merged to reduce repetition. However, in my opinion, the sort of people with the computer skills and vocabulary to get through the first paragraph of "Unicode Input Methods" already understand alt codes. Most computer users (sadly enough) have a very hard time comprehending the fact that computers store text in numerical format, and will faint the first time they see something like U+FFFF. —The preceding unsigned comment was added by 216.135.95.189 (talk • contribs). 8 April 2006

[edit] Great work

Great work on the page. It definitely looks nicer. —Preceding unsigned comment added by 216.135.95.189 (talk • contribs) 8 April 2006

[edit] Alt+0### is not a Unicode input method

The "###" in "Alt+0###" is not a Unicode code point and therefore this is not a Unicode input method. On my US Win2K system it appears to be giving me Windows-1252 characters. For example, Alt+0128 gives me the Euro symbol, and anything above 255 is entered as if I had typed it modulo 256 (e.g., 256=000, 257=001, and so on). This misinformation about it being "Unicode" is repeated on Unicode#Input methods as well. Please research the actual behavior and fix the articles.—mjb 00:40, 1 May 2006 (UTC)

I've actually seen some systems, with no relevant third-party software, configured in such a way as to allow unicode input (i.e. Alt-9674 = ◊) - This keeps getting repeated everywhere, and I've seen it with my own eyes, so at some point we need to track down what configuration results in this behavior. —Random832 16:53, 17 March 2008 (UTC)