From: Jean-Marc Desperrier (jean-marc.desperrier@certplus.com)
Date: Fri Jan 10 2003 - 11:23:52 CST
Claus Färber a dit :
>Russ Allbery <rra@stanford.edu> schrieb/wrote:
>
>
>>It's really not particularly hard to keep track of what strings were
>>originally encoded and to see if they were actually changed by the user
>>before re-encoding them instead of just using the original strings.
>>
>>
>Further, not all user agents do present the full message, including
>headers, to the user for editing.
>Most non-textmode user agents have seperate input methods for that data.
>
>
It's not a difficult, hard task to do, but it's one that's overlooked by
95% of news client developers.
Push to add it something relative to it to the GNKSA if you want.
But even if this problem were solved, which is unlikely to happen, they
is not only also the fact that for some specific cases it's really
difficult to properly interpret the full RFC2047 text, but also that
many programmers routinely miss very basic points of RFC2047.
Everybody seems to believe it's easy to implement and writes his own
routine, which is full of defects.
Some much harder task than RFC2047 do not meet the same problem, but
that's because they are some free librairies to do, and nobody believe
he will be able to recode it in 5 minute, so they use one of the
available library for a fast coding.
I didn't answer the message about the fact that encoding in UTF-8 is not
always unique.
The problem of uniqueness in these kind of case is not due to the
encoding, but to the language.
If you want to support a language whose complexity leads to such this
kind of problem, then you will run into them, whatever the encoding, so
it's a nonsense to say they're due to the specific use of unicode.
It is not up to the application to solve them, but to the IME to
generate the proper form that will be the most compatible/accepted.
Any user that has a problem here when creating content for usenet will
have exactly the same problem in any other application in which he tries
to enter the same data.
This will not be a problem he will associate or need to resolve at the
specific usenet application level.
We've had this kind of discussion over and over already, haven't we ?