mathiasbynens / mathiasbynens/q-encoding
overlong output
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 20
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
no provision is made to allow the output to be split between input characters as RFC 2047 requires for long strings 5(3) "Each 'encoded-word' MUST represent an integral number of characters.
A multi-octet character may not be split across adjacent 'encoded-
word's."
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Start by locating the Q-encoding implementation and any existing tests, then compare long-string behavior with RFC 2047 section 5(3). Done means long output can be split without dividing a multi-octet character across adjacent encoded-words.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100