| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Fixes/comments for guessBestEncoding (#304) | Jan Engelhardt | 2024-05-21 | 1 | -0/+9 |
| | | | | | | | | | | | | * tests: add case for getRecommendedEncoding * vmime: avoid integer multiply wraparound in wordEncoder::guessBestEncoding If the input string is 42949673 characters long or larger, there will be integer overflow on 32-bit platforms when multiplying by 100. Switch that one computation to floating point. * vmime: update comment in wordEncoder::guessBestEncoding | ||||
| * | Code style and clarity. | Vincent Richard | 2018-09-05 | 1 | -43/+88 |
| | | |||||
| * | Added support for language specification in RFC-2047 encoded words and ↵ | Vincent Richard | 2014-06-30 | 1 | -5/+12 |
| | | | | | RFC-2231 parameter values. | ||||
| * | Refactored unit tests. | Vincent Richard | 2013-03-08 | 1 | -5/+1 |
| | | |||||
| * | Unit tests for wordEncoder. | Vincent Richard | 2013-02-25 | 1 | -0/+126 |
 |
index : vmime | |
| VMime Mail Library |
| aboutsummaryrefslogtreecommitdiffstats |