Nice to see there's a workaround:)
As to the...
I'm glad this was a quick fix, instead some ugly plugin i would have had to use.
..I wouldn't say a plugin would be an ugly way of doing this:-) Because next time you upgrade, you'll have to:
1) save the changes to the code of post-template.php somewhere,
2) upgrade wordpress, by deleting old WP files (including post-template.php)
3) edit manually again post-template.php so as to include the fix you need,
and this will happen every time you make an upgrade;)
A plugin, on the other hand, would make things much easier - upgrade, reactivate plugin, and do not edit core files:)
But I do not know how easy/hard is to make this using a plugin - I am not strong in programming, unfortunately...
For now, I have to make only one change when I upgrade - to the file wp-db.php in /includes, because MySQL on my host uses Latin-1 or something of the sort as default encoding for interaction with php scripts, and as I use UTF-8 in my blog, to make characters display correctly both in the database and in my blog, I have to add
mysql_query("SET NAMES 'utf8' COLLATE 'utf8_unicode_ci'");
in wp-db.php, otherwise things go quite messy:(
(You may refer to this thread for more info:)
And I'm dreaming one day to find an easy way to modify wp-db.php using a plugin instead of manual edit, but I guess this is quite complicated...