Flag sequences
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- rust
- Domain
- internationalization
Research direction
Start by reading the issue's Unicode TR51 references and locating the existing flag notation and validation behavior in the repository. Define support for valid regional-indicator pairs and the recommended UK tag sequences, then resolve whether additional subregions belong in scope; done means invalid sequences are rejected and the listed examples are accepted.
Written by the indexing model from the issue text.
Description
Unicode has two mechanisms for encoding regional flags
- A pair of regional indicators (https://unicode.org/reports/tr51/#Flags). Only a subset of these pairs, determined by the CLDR, are valid. Valid pairs can never become invalid, only deprecated, so there's backwards compatibility.
- Emoji tag sequences (https://unicode.org/reports/tr51/#valid-emoji-tag-sequences) for subregions. In principle this can be used for thousands of subregions, but due to lack of font support the only three marked as "recommended for general interchange" are the ones for the three countries making up the UK.
We should add support for these, for instance through flag.de, flag.gb, flag.un, flag.eu ((macro)regions) and flag.gb.eng (subregion). Only valid sequences should be accepted.
One question is whether support for other subregions than the UK ones should be added. I did find at least one font that supports more subregions (https://www.babelstone.co.uk/Fonts/Flags.html).
- Dominant language
- Rust
- Stars
- 53
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Contributor guide
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.
More from typst/codex
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
-
proposal
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Lack of ⊻ U+22BB Openproposal
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
stratum-mining/stratum#2404 ·
-
bug ci good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
documentation easy help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
lacs-project/sysknife#483 · 1 comment ·
-
area:evidence documentation
Difficulty 1/5 Under an hour Newbie friendliness 90/100
registrystack/registry-stack#1302 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100