Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add the ability to generate a response with a different encoding #698

Open
GoogleCodeExporter opened this issue Mar 25, 2015 · 2 comments
Open

Comments

@GoogleCodeExporter
Copy link

Currently when a response is encoded it is always encoded with the encoding the 
the server adapter. This is very useful except in the one off case where you 
need a different encoding eg. for answering a CSV document. See [1] for an 
example.

In general something like this should be enough to switch the encoding of the 
response:

aResponse contentType: ((WAMimeType main: 'text' sub: 'csv')
    charset: 'utf-16';
    yourself)

 [1] http://lists.squeakfoundation.org/pipermail/seaside/2011-November/028041.html

Original issue reported on code.google.com by philippe...@gmail.com on 26 Nov 2011 at 11:36

@GoogleCodeExporter
Copy link
Author

Issue 766 has been merged into this issue.

Original comment by jo...@yesplan.be on 6 Feb 2014 at 12:27

  • Added labels: ****
  • Removed labels: ****

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants
@GoogleCodeExporter and others