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.
2009/10/19 erik quanstrom quans...@quanstro.net:
why try that hard? just call it utf-8. i can't think of
any browsers that would have a problem with that today.
the instance of the problem that i had was when
adding an attachment to a upas mail.
file -m is useful when the attachment
Thus, hard coding charset=utf-8 in http header will bring other
problem
because that coding disables a line in html header such as:
meta http-equiv=Content-Type content=text/html; charset=Shift_JIS
that should not be a problem on a plan 9 system;
plan 9's character set is utf-8.
-
