iso-8859-1/windows-1252 support?

Hi,

A while ago I developed a web app to replace an old cgi-bin script from the nineties, which means that it had to assume that POST requests with a Content-Type of application/x-www-urlencoded are in iso-8859-1 (and also support “smart quotes” etc., aka. windows-1252). At the same time it had to be possible to switch to utf-8 mode.

I accomplished that by adding support for a defaultCharset option, which can either be utf-8 or iso-8859-1, and for explicitly switching to utf-8 mode by adding utf8=%E2%9C%93 (utf8=✓ as percent-encoded utf-8 octets) to the query string, a trick that I’ve seen others use as well.

Here are the diffs between my forks of body-parser and the qs module:

https://github.com/expressjs/body-parser/compare/master...papandreou:iso-8859-1 https://github.com/ljharb/qs/compare/master...papandreou:interpretNumericEntities

Would anyone be interested in this work? If so, I can clean it up and open PRs.

[Xtrem65]

@dougwilson Any update on this ?

I’m interested in this feature but as @papandreou 's branch is way behind the official master. Seems like it’s going to be hard to pull…

Is there any proper other way to handle ISO-8859-1 encoded data ?

[papandreou]

@Xtrem65, you can help by trying it out 😃

1. Make a clone of https://github.com/papandreou/qs
2. Check out the feature/iso8859-1 branch
3. npm link
4. Make a clone of https://github.com/papandreou/body-parser
5. Check out the feature/iso-8859-1/take2 branch
6. npm link qs
7. npm link
8. cd to your project
9. npm link body-parser

… Then see if you can solve your problem. Depending on the requests that you need to support, you might have to specify the defaultCharset option.