Home » Mail » Mail_Mime » Bug #8297
Content type charset does not need to be in quotes
Details
| Request #8297 | Content type charset does not need to be in quotes |
|---|---|
| Submitted | 2006-07-26 11:29 UTC |
| From | alexei at net24 dot co dot nz |
| Assigned | cipri |
| Status | Bogus |
| Package | Mail_Mime |
| PHP Version | 5.1.3 |
| Roadmaps | (Not assigned) |
Comments
[2006-07-26 11:29 UTC] alexei at net24 dot co dot nz
Description:
------------
RFC2045 does not tell that charset value should be in quotes.
Currently library formats charset like
text/plain; charset="UTF-8"
- value is in quotes.
The mail agent we use does not understand such format. It only accepts values like
text/plain; charset=UTF-8
I coundnt find any documents dictating that charset value must be enclosed in quotes, is there a reason why you do it that way?
My proposal is that special param is added to switch quotes on or off.
I'm aware that it is possible to overwrite headers but it makes it way uglier no matter if i do it before or after headers are generated