new/sendfd.c:243 c old/sendfd.c:243 < --- > /* new/sendfd.c:246 c old/sendfd.c:246 < --- > */
(context: text/plain -> text/plain; charset=utf-8) Now my text files can be read in the proper encoding by default, and are not interpreted by browsers (as well as certain applications) to be whack ASCII. Is the output of file(1) appropriate for this purpose? Shouldn't your sample file also be sent as UTF-8? Thank you for the input, Mr. Arisawa. I agree with Erik in this case, as you wouldn't be doing much with files of other encodings on Plan 9 (well, prior to a tcs(1)), you really only need to worry about getting across UTF-8. The point about file handling being up to browsers is appropriate. However, I'd like to push as much standard behaviour from the server as I can. If there's an explicit account of the encoding and type of a file, then there ought to be no ambiguity. Thanks, ak
