Posted by Yohan N. Leder on 05/20/06 00:43

In article <gsnbg.2271$UG1.2070@reader1.news.jippii.net>,
jkorpela@cs.tut.fi says...
> Besides, I was unable to observe the problem you describe. Your code for
> dumping raw data doesn't produce particularly readable output (I don't see
> line breaks).
>

As you said yourself, it's raw data and line break are not HTML line
breaks (ie. <br>). However, I could change every line break to <br>
before displaying, but it doesn't change anything about the problem.

Apparently you didn't seen anything wrong on your side... Then, it means
your particular plateform (browser, os) doesn't fall in this issue while
others do. What's your browser and operating system ?

Also, you said : "Again, you are complaining about error processing in a
situation where no particular error processing is required by the
specifications."... Right, because, effectively an euro sign is not
supposed to be processed in iso-8859-1. But wrong too, because in my
example, the transmitted data, when checkbox is checked, includes the
euro sign : strange... As stated by Alan J. F. elsewhere in the thread :
it seems to be an old well known bug.

And, to finish, it's always interesting to test everything as final user
will do : entering everything, even what was not foreseen by the
programmer... And the fact is that, even if I've choosen an iso-8859-1
charset, a French user using an Azerty keyboard is able (and encouraged
because the sign is printed on the key) to enter the euro sign...

So, in this case and, again, because the content-type charset was iso-
8859-1, I expected that the euro sign was striiped out and the rest of
the data well transmitted : but it's appently not the case from every
client : it's a problem we can call a bug !

[Back to original message]