£ never used to cause me a problem on the old RH9. But these days most web servers seem to be set to en_us.UTF-8, where outputting £ will give you a nasty ? in the browser, needs to be £ these days.
On a side note just noticed something annoying about HTML::Entities, if your input is already encoded, such as £, you'll get £, thought it would have checked for encoded characters and skipped them?
Lyle | [reply] |
On a side note just noticed something annoying about HTML::Entities, if your input is already encoded, such as £, you'll get £,
well, how would you encode it? given an input like
If you write & in HTML, it turns out as &
The expected output of such a text after encoding would be:
If you write & in HTML, it turns out as &
Now you're saying, only the last ampersand should be escaped? Because the first one is already escaped? No, you
never know if a text is already escaped.
| [reply]
[d/l] |
thought it would have checked for encoded characters and skipped them?
That would be BAD! Decoding and encoding your post would change "such as £" to "such as £".
On a side note just noticed something annoying about HTML::Entities, if your input is already encoded
Duh?
The same thing happens if you try to encode characters twice.
The same thing happens if you try to encode URL characters twice.
The same thing happens if you try to zip a string twice.
etc
| [reply] |