From: Axel Beckert <abe@de...> - 2009-03-08 02:07:02
I just did some refactoring (especially this very long "use vars" line
:-), but also added a new feature. See
for a summary of the changes and
for a diff of the new feature, which btw. is disabled by default.
About the new feature, the flag $encode_8bit_chars:
Special characters, e.g. German umlauts, in the links to posts weren't
URL escaped in Blosxom before. This broke my setup several times,
because some browsers took the link with a ISO-Latin-1 umlaut in a
filename, converted _that_ to UTF-8 (which is the declared charset for
the content) and _then_ followed the link which then of course
resulted in a 404, because the link went to e.g.
because in the HTML source the link pointed to
Sure, even links should not contain umlauts in ISO-Latin-1 if the
content is declared UTF-8, but since they do in my case, partially for
historically grown reasons, they need to be URL escaped, everything
else causes breakage somewhere.
This is currently done with a regexp (haven't found an appropriate
function in CGI.pm) and should also URL escape some other unusual
characters like blanks, etc. in file names.
So basically I think, this should be enabled by default, but I'm not
sure if it causes any breakage somewhere where I just don't expect it
or haven't thought of. So it's disabled by default.
I would also like to make a 2.1.3 release with at least the changes
since 2.1.2 until now. As far as I see, the above listed feature would
be the only new feature, everything else is either refactoring or
Any comments on the feature, refactoring or the plan to make a new
P.S.: My blog at http://noone.org/blog currently runs the version at
HEAD of the repository.
Axel Beckert - abe@..., abe@... - http://noone.org/abe/
Get latest updates about Open Source Projects, Conferences and News.