Re: utf-16le encode generic view object_list

@Tim: render_to_string! Forgot about that, somehow. That could clean it up a bit. Thanks! @Stephen: Thanks for the feedback. This app's running internally and is on insecure and ancient 1.4, but the mimetype parameter reminder is a good one! Thank you. -- You received this message because you

Re: utf-16le encode generic view object_list

I think that looks fine. I would change the mimetype to "text/plain; charset=UTF-16LE" just to play nice, but it probably will never matter with your Content-Disposition. Also, HttpResponse's mimetype parameter has been deprecated since 1.5; use content_type instead. On Thu, May 21, 2015 at 3:04 P

Re: utf-16le encode generic view object_list

On 2015-05-21 13:04, JHeasly wrote: > I've got a function-based generic view that I want to return a > utf-16le encoded response (for use as an InDesign tagged text file; > the utf-16le is what InDesign wants). I've got it working here > , but

utf-16le encode generic view object_list

Hello all, I've got a function-based generic view that I want to return a utf-16le encoded response (for use as an InDesign tagged text file; the utf-16le is what InDesign wants). I've got it working here , but am wondering if there's an mo