http://en.wikipedia.org/wiki/Strikethrough#Combining_characters
http://en.wikipedia.org/wiki/Combining_character
(opposed to the usual
dead key diacritics, accents etc)
http://en.wikipedia.org/wiki/Precomposed_character#Comparing_precomposed_and_decomposed_characters
Seems like these combining characters (or 'decomposed'?) don't work for every browser and/or charset. Precomposed unicode chars would be safer, but obviously don't exist for strikethrough.
I never knew there was this system where the modifying char(s) go behind the one being modified, but it makes much for sense for multiple diacritics.
Until now I only knew about the dead keys for ^ ´ ` to make à ó etc.
Also a nifty thing I discovered recently:
Quote: "When Windows later transitioned to Unicode, the 0-leading codes had become so well known as well that a third method needed to be invented to produce Unicode codepoints. Although codepage 1252 is quite close to the start of Unicode and it would seem logical to just allow larger numbers to be typed, other international sets did not match. In addition, some users were accustomed to the composition exiting after the third digit without releasing Alt, and numbers larger than 255 being translated modulus 256. To enable the third method, a user must set or create the registry key HKCU\Control Panel\Input Method\EnableHexNumpad with type REG_SZ to value 1 and reboot (logging out and logging back in is sufficient). Once the registry key is set, the following method can be used to enter Unicode codepoints:
- Keep the Alt key pressed. Press the + key on the numeric keypad.
- With the Alt key still pressed, type the hexadecimal number using the numeric keypad for digits 0-9 and the normal keys for a-f.
"
Source:
http://en.wikipedia.org/wiki/Alt_code
I never really understood why those Alt Codes are a different code from Unicode. But with this method you can just hld the Alt Key and enter +336 on your numpad, et voilà, you have a combining strikethrough (which goes AFTER every character to be struck)
Let's test this thing... He̶ll̶o W̶or̶ld̶!
Uhm. Well. I have a strikethrough after the E, second L, the W, r and d. Atleast here it looks like it applies the strike to the following char
̶̷A̶̷n̶̷o̶̷t̶̷h̶̷e̶̷r̶̷ ̶̷t̶̷e̶̷s̶̷t
Here every char has a +336 and +337 in front of it (see Strikethrough article for reference.)
Also I just realized I
finally know how people create those "Zalgo" texts!
Here's two screenshots of these things how I see them:
On Win 7 with Firefox 22.0... looks okayish, just realized this here looks nothing alike:
Anyone getting unrecognized characters / boxes?
Edit: I just noticed in IE that the "seperate" examples in the strikethrough article are supposed to have the strikes on blank spaces between the chars, I guess? I was wondering why both looked nearly the same... dunno why FF does that.
