Wesley's Tool-Box

After giving some thoughts, I bit the bullet and instead of using that 'wes.mine.nu' as the base domain of the website and having 'Tool-Box.info' redirecting to it, the 'Tool-Box.info' is now the base domain itself. This service cost some money, but I thought it would be worth the trouble.

What happens at the moment is that http://wes.mine.nu/ and http://tool-box.info/ both connects to the same location. However, I had previously configured http://tool-box.info/ to redirect to http://wes.mine.nu/blog/ which goes to the blog site (yes, this place). http://wes.mine.nu/ had a test page set up that I had created in a minute to test out the DDNS connection and it didn't make any sense anymore. So basically, you would need to connect to http://tool-box.info/blog/ to see this place instead of http://tool-box.info/ because you would end up with the test page instead.

But that doesn't look as good as before, right?

Since I'm too lazy to set up a new 'front page' for the site, I have now configured the server so that connecting to http://tool-box.info/ will be exactly like connecting to http://tool-box.info/blog/ .

You don't have to remember a new URL. Yay!

Now, I will be deprecating the 'wes.mine.nu' domain in a few days, so if you had any URL linked from my site, now is the time to update to the 'tool-box.info' domain.

Static page plugin on my blog was having problems... seems to be fixed now. Sorry for the minor inconvenience while I was trying various settings to try overcome it.

The much awaited 10.4.2 update is here... Hope it fixes a bunch.

Alright, good news for all those who wanted Korean support on my website.
After wasting a whole day, I have created an up-to-date Korean support for the s9y blog system. It seems to be working okay, although there are a couple of labels that look weird (it's not fixable from my end so I've reported this to the creator of s9y). There is also now a language support drop box on the right. You'll be able to see the site in Korean and read Korean versions of the articles (not all that much atm).

How is it that the English setting is defaulting to ISO-8859-1 encoding...
This corrupts any Korean entries... not good for multilingualism.

As a workaround I simply switched the encoding field in the English language data to UTF-8.
Seems like this is the way to go if the menus are to remain English and have Korean entries intact.

Anyways, I think this should help mark the first successful Korean blog entry.