On Thu, Feb 19, 2009 at 12:29 PM, Jesse Vincent <[email protected]>wrote:
> > > > On Thu 19.Feb'09 at 11:55:19 -0500, Todd Chapman wrote: > > It was attached in the web interface on the Create.html page. (Not a > > custom field) > > And what headers is RT serving it out with? Is RT announcing it as utf8? > Is that stored in the database as content-type? > > If you save the raw data from RT to disk and open it in a browser, does > it render correctly? (Use wget, not your browser to save it. The browser > could corrupt it) It displays the same when downloaded with wget. (same md5) Here are the headers via the wget -S option: HTTP/1.1 200 OK Date: Thu, 19 Feb 2009 17:52:57 GMT Server: Apache/2.2.3 (CentOS) Set-Cookie: RT_SID_techrt.80=b6f63c39b4f0992034a41bb57f9bac80; path=/ Connection: close Content-Type: text/html;charset=utf-8 Length: unspecified [text/html] > > > > > > On Thu, Feb 19, 2009 at 11:45 AM, Jesse Vincent > > <[1][email protected]> wrote: > > > > On Thu 19.Feb'09 at 11:42:42 -0500, Todd Chapman wrote: > > > According to FF the original file has an encoding of UTF-16LE. > It > > was > > > generated by Word. (I know, I know) > > > > Now we're getting somewhere. Was it attached to a mail as an > > attachment? If so, what do the headers for the original attachment > look > > like as they hit RT. If not, how did it get into RT? > > > > References > > > > Visible links > > 1. mailto:[email protected] > > -- >
_______________________________________________ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [email protected] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
