I both enjoy the seemingly-limitless bounds of Unicode (ah, Mac OS X; the Terminal supports it nicely) and yet still tend to stick to ASCIIisms in blogging. I think it's mostly because I've been doing this computer-mediated communication stuff so long that I remember when ISO Latin 1 was a huge step forward, long after I was set in my ways.
How set in my ways am I? I still put two spaces after a sentence-ending punctuation mark, that's how set in my ways I am.
But, just for the sake of experimentation: can I type 日本語？ Can I talk about Frosty the ☃? How messed up will this comment look, since I've been typing (er, generating anyway) raw Unicode into it? Will my mailed copy be usable?
In Opera 7.54 those characters show up as "not in this font" empty square boxes. The emailed version had a bunch of '=xx' codes which I can't read without consulting a Unicode chart: "=E6=97=A5=E6=9C=AC=E8=AA=9E=EF=BC=9F" -- twelve codes for four characters, so in addition to looking at the chart I need a quick refresher on the various ways Unicode is re-encoded for 8-bit environments.
Then again, I have all those fancy-schmancy characters turned on, because I read marginally in a bunch of character sets. :) I'm losing my Japanese a bit, though.
(no subject)
How set in my ways am I? I still put two spaces after a sentence-ending punctuation mark, that's how set in my ways I am.
But, just for the sake of experimentation: can I type 日本語？ Can I talk about Frosty the ☃? How messed up will this comment look, since I've been typing (er, generating anyway) raw Unicode into it? Will my mailed copy be usable?
(no subject)
As for two spaces after a period, yah, me too.
Ee, koko dewa nihongo ga imasu...