After a long time away, I'm raising my head again on the java.net site. I once roamed these java.net streets as a JDK developer at Sun Microsystems, then as an end-user of the JDK while at a few startups, and now...well, I'm back again.
This is a test of the java.net blogging system to see how well it supports non-ASCII, UTF-8 text.
I notice that many of my older posts from the pre-Drupal days are now munged; non-ASCII, UTF-8 chars are now garbage characters.
Sigh...but new blogs seem to be correct.
I was experimenting with Java 7's
ResourceBundle classes recently. Java 7 introduces two new
FORMAT. You can set the default locale for localizable user interface resources independently from the default locale for data Format subclasses.
I admit that I haven't been particularly active in the i18n or Java standards bodies in the last few years. Pardon me, but I had a wild rumpus in a startup for almost 3 years, then joined Yahoo for a couple years, and BAM! ...
I recently installed Java 7 on my Mac OS X system. Although the installation went smoothly, I did run into one problem that might not be a big issue for you.
NOTE: I've updated this blog to avoid "mojibake" -- garbled characters. For some reason, the word TA in TANAKA in the name query key in examples was garbled. Originally all occurences of the word 中 were prefixed with the character for TA...for the common family name TANAKA. After removing the mojibake, I think you can still understand the purpose of the blog.
I've wanted to know how to do this for over a year. Not having the time in the past, well, the task just got delayed over and over. Now I finally figured this out, and I'm sharing with you. Surely there are other bloggers that prefer to use their own blog client and MarsEdit in particular if you're using an OS X client.
Yesterday a coworker complained that Excel wasn't displaying a CSV (comma separated values) file correctly. Our application allows the user to send a report via email. The application provides the report as a CSV file. Because the report can contain multilingual text, we've decided to encode it in UTF-8.
Everyone has something to say about the past. Few can see the future. Here are my predictions for 2010!