Add codepage integration tests
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 991
- Forks
- 105
- PR merge metrics
- No merged PRs in 30d
Description
In relation to #262 we should add integration tests that force the codepage to non-UTF CPs like OEM 437, along with setting the system locale to non-ENU so that the display name and/or description contain extended codepoints that would otherwise display or parse incorrectly on non-Unicode codepages.
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.
Research direction
Start by reading issue #262 and the existing integration-test setup in the repository. Define coverage for OEM 437 and a non-ENU system locale, then verify that display names and descriptions containing extended codepoints are handled correctly without incorrect display or parsing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- internationalization, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100