Posted by Jukka K. Korpela on 05/20/06 22:41

Yohan N. Leder <ynleder@nspark.org> scripsit:

> As you said yourself, it's raw data and line break are not HTML line
> breaks (ie. <br>).

Rendering raw data without showing line breaks isn't logical.

> However, I could change every line break to <br>
> before displaying, but it doesn't change anything about the problem.

It would make the problem easier to see.

> 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...

Yes, but we already know that error conditions will arise then, so why not
concentrate in preventing such conditions or handling them properly, rather
than asking why some particular browser handles it some particular way.

> 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 :

There was no ground for such expectations. Luckily it didn't happen, since
you might think "it works" and fail to know that it doesn't work on other
browsers.

> but it's appently not the case from every
> client : it's a problem we can call a bug !

No, it is error handling upon which no requirements have been made. I though
this already became clear.

[Back to original message]