> > I agree as well, and unfortunately, that page isn't properly using
> > any encoding, thus the failure.
> Just to make sure I get it right: you think that the a umlaut is not
> encoded correctly according to utf-8?
No, it is encoded right, assuming the page properly declares the
charset as UTF-8, which the original page does not. He needs to add the
proper charset tags to his page before the server sends it to the client.
> Well, I still worry :-/ I cannot change how the page generates the page
> and I cannot filter the pages while plucker-build downloads them.
> Overriding the encoding with --charset=utf-8 also had no effect, the
> characters are still broken in the Plucker viewer.
Parse it down locally and regex it out with before_command and some
sed or perl, or just prepend the proper charset to the page with
before_command. I see you're using Linux (and a very old version of
Evolution as well), so this should be no problem to do.
d.
_______________________________________________
plucker-list mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-list
