marcmagus | (Reply)

S	M	T	W	T	F	S
						1
2	3	4	5	6	7	8
9	10	11	12	13	14	15
16	17	18	19	20	21	22
23	24	25	26	27	28	29
30

1hand - 3 uses
allergies - 4 uses
cabinet - 7 uses
calendar - 3 uses
chromium - 4 uses
computer - 3 uses
convention - 8 uses
cvd - 6 uses
dance - 24 uses
devnull - 3 uses
drugs - 3 uses
dw - 24 uses
encoding - 8 uses
food - 9 uses
games - 5 uses
geeky - 2 uses
gentoo - 3 uses
hair - 12 uses
hands - 10 uses
health - 4 uses
house - 3 uses
humor - 4 uses
internet - 3 uses
jlj - 4 uses
lenses - 3 uses
linux - 8 uses
lj - 12 uses
meme - 4 uses
music - 3 uses
navel-gazing - 6 uses
nethack - 4 uses
newport - 4 uses
noncon - 8 uses
pain - 3 uses
politics - 6 uses
polyphasic sleep - 8 uses
programming - 3 uses
quest prizes - 4 uses
rant - 8 uses
regency - 8 uses
science! - 6 uses
test - 9 uses
tools - 36 uses
tv - 4 uses
twitter - 3 uses
ui - 5 uses
vim - 5 uses
voting - 2 uses
wtf - 3 uses
zelda - 7 uses

no subject

Monday, May 11th, 2009 03:26 pm (UTC)

No, because instead of using, for example [Level3Shift]-[apostrophe] [e], I either need to remember or look up é or, worse, look up whatever the numeric codepoint for it (and I forget if the latter is still encoding-dependent or defined to be a Unicode codepoint). There has to be a way to set things up so everything in the toolchain agrees on the encoding, and it's not like I'm using something obscure.