I agree that there is apparently not much of a problem. However, I also stand by "no more dialogs" unless they are in a clearly-identified class/method/state that is known to interact with the user. Squeak has *far* too much forced and unexpected interaction, and we must not go back down that road.
Those things said, there might be room to grow, as someone suggested the possibility of automatically detecting the coding. ________________________________________ From: [email protected] [[email protected]] On Behalf Of Henrik Johansen [[email protected]] Sent: Friday, July 23, 2010 12:41 PM To: [email protected] Subject: Re: [Pharo-project] Invalid utf8 input detected: now what? Den 23. juli 2010 kl. 15:15 skrev "Schwab,Wilhelm K" <[email protected]>: > No dialogs, please :) Actually, it would be fine if there were a different > stream class or simply a different method/state (encoding =#userInteraction > or something??) that is understood to negotiate such details with "the user." I have no idea what you are suggesting... > In general, exception is the correct way to handle this: the stream "knows" > what is wrong; the application will know what to make of it. If the encoding > can be detected automatically, that would be great. > Then I fail to see what the problem is. You got an error stating it was not UTF8, which implies a choice of the correct encoding needs to be done by the application. (by setting the streams encoding to something else) As you noticed with gedit/firefox, any "automatic" detection is at best an educated guess, and can not be relied upon to make the correct choice. Cheers, Henry _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
