node-unicode / node-unicode/node-unicode-data

`Not_Assigned` category?

Open
#33 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

upstream
Dominant language
JavaScript
Stars
154
Forks
18
Avg merge
9h 48m
Merged PRs (30d)
3

Description

I’ve submitted this through http://www.unicode.org/reporting.html, but track it here since it affects this repository.


Both http://www.unicode.org/reports/tr18/#Categories as the latest draft of that document i.e. http://www.unicode.org/reports/tr18/proposed.html#Categories list the following example:

\p{General_Category = Not_Assigned}

However, Not_Assigned is not a valid General_Category name as per the table here: http://unicode.org/reports/tr44/#GC_Values_Table

Suggested fix: use Unassigned instead in the example.

\p{General_Category = Unassigned}

It would be easy enough to add a Not_Assigned alias but I’d rather not if this is indeed a mistake.

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

Compare the General_Category examples in Unicode TR18 with the valid names in the TR44 General_Category Values Table, using the linked sections as the starting point. Done means the example consistently uses the valid category name, or the Unicode report confirms that no repository change is needed.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.