mathiasbynens / mathiasbynens/punycode.js

Doesn't support RFC 5895

Open
#96 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
1.7k
Forks
170
PR merge metrics
No merged PRs in 30d

Description

5895 seems to be the most up-to-date spec, and this doesn't seem to support the deviations listed here: https://unicode.org/reports/tr46/#Deviations .
Was wondering if there were plans to support this, or if I need to figure something else out. (Seems like this is the recommended way to do punycode for node)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the project's stated RFC 3492 and RFC 5891 compliance with RFC 5895 and the Unicode TR46 deviations linked in the issue. Check the existing punycode.js behavior against those deviations and define completion as supporting the applicable deviations with verification for each affected case.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.