i summon one kim

Well, this is only for those of you who browse with MSIE: the images on my (non-blog) pages are back. For example, I’m sure the Proxy through SSH document is easier to follow with the screen captures visible, instead of staring at blank spots. (The blog pages were already fixed earlier.)

I wonder how many more times I’m going to be writing about the same problem — it is just so very annoying that I have to at least vent a little after fixing the same thing over and over. This time I had to add an extra <div> element on the pages, which makes it even more frustrating (“unnecessary” extra elements). Well, I put some comments in the code so I’d remember why it is there…

Not that I noticed this one on my own, either. I was talking to someone about a page, and got an odd “what picture?” response. At least I now immediately remember to fire up MSIE when I hear something like that.

Alternative browsers you could switch to: Firefox and Opera.

The recent Microsot Internet Explorer (IE) problem was bothering me, because it meant the pages were not usable with IE. I wouldn’t mind a cosmetic problem as much (even though they tend to get to me, too) but links not working and pictures not being visible is just too annoying.

I was playing with the CSS, experimenting with the “floating dt” that I had avoided in the last workaround due to it “disappearing” on IE. When I made the dd element floating as well, I saw that IE was rendering the contents below and outside the white box (#envelope) that holds the main content on each page. In the past this has been a giveaway for IE miscalculating the size of the containing element, and sure enough — the “fix” was an added width: 100% property for the misbehaving container.

The “invisible images” were restored to visibility with the same fix on the appropriate container. I’m glad it didn’t need another couple of hours of CSS tweaking in the dark.

It’s nice to have the site working again, but I’d rather not spend my free time on something stupid like inventing workarounds for a buggy browser. (Not that I expect Microsoft to pick up any hints from here.)

Enjoy!

My brother just told me that this site is broken (again) in Microsoft Internet Explorer: the links in the “asides” entries are not clickable and pictures in posts are not visible (but the layout still has their space reserved). This is especially frustrating since there haven’t been any changes to the site code (XHTML or CSS) since September 11th, and everything definitely worked then in both Firefox and IE. Of course, there have been a number of “IE updates” since through Windows Update…

I’d like to fix this right away, but I’m far too busy with other things at the moment. I did try a couple of CSS changes, but didn’t land on the solution yet.

In the mean time: Get Firefox already. :-)

I was having trouble with ½ and ¾ in an article I was trying to publish on another WordPress-powered site. First I thought my browser was acting up, but soon became doubtful and realized I should look at the source of the page generated by WordPress. To my surprise I saw that the entity codes had been deliberately mangled.

I tracked down the source of the problem in the WordPress code. This patch fixes the problem.

Call me an Internet addict (it might be accurate, actually), but I’m very used to having broadband Internet access always. I consider having available on-demand (some might say “constant”) access to my Internet-connected servers the norm. I read my mail on-line (in plain text, no less). My RSS aggregator is on-line on the web. I contact my friends on-line on IRC.

Yet there are times when I’m not online. Most commonly this used to be while commuting to and from work. I’d be on the train for about an hour each way. My favorite pastime for the commute was reading. But sometimes I would have liked to write down some thoughts, either for the blog or maybe for an email reply.

I knew about offline blogging tools but I had never really looked into them. I had experimented with Windows Notepad and the Blackberry memo application. Both are fine for writing the bulk of the text, but the “cleanup” tended to be too tedious: there are a number of fields you still have to fill in before a blog entry can be published or an email sent out.

I recently went through the weblog clients listed in the WordPress Codex to see what my options were. I chose to install w.bloggar on my laptop. With just a little bit of configuration (and a couple of tweaks on my non-standard WordPress installation to accommodate language selection) I had successfully published a test entry. Quite painless so far.

With w.bloggar I can set all the common post attributes (title, tags, timestamp) without any of the tedious cut-and-paste that would be necessary without a dedicated offline blogging tool. Once I’m connected to the Internet I can easily open each saved post and publish it. (That statement will be validated by the fact of this post appearing on my site…)