Special Character issues
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Description
When loading a content, the path of the content can't have any special character in it.
Expected behavior
-Launching the game properly, handling special characters (or basics special character like "é")
or
-Displaying an error about the path of the rom/ File not found or something to know where the error comes from
Actual behavior
RetroArch display an error "Failed to load content", leading to a lot of possible errors.
Steps to reproduce the bug
- Have the rom in a path that include a special character ("é" char in my case)
- Load a core (Desmume in my case)
- load a content (.nds USA rom in my case)
(Also, having RetroArch in a path that include a special character may cause some other problem maybe. I haven't verified this, my RetroArch isn't in the same folder)
Bisect Results
As soon i installed it
Version/Commit
Git Version : c73daa6a1c
Environment information
- OS: Windows 10 64 Bits
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
Reproduce the failure on Windows 10 with RetroArch and a .nds ROM whose path contains a character such as "é", using the reported core-loading steps. Trace content loading from the reported "Failed to load content" result, then verify that such paths either load successfully or produce an error identifying the ROM path problem.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100