libretro / libretro/RetroArch

Retroarch is unusable without assets and default language

Open
#13,060 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
14.1k
Forks
2.2k
Avg merge
7h 35m
Merged PRs (30d)
51

Description

First and foremost consider this:

  • Only RetroArch bugs should be filed here. Not core bugs or game bugs
  • This is not a forum or a help section, this is strictly developer oriented

Description

Retroarch is unusable without assets and default language. All letters replaced by "?". Update assets? but how? I just can't find such menu option by blind.

Expected behavior

If asset font is missing, language should switch to English.

Actual behavior

All letters replaced by "?", and it breaks Retroarch UI at all.

Steps to reproduce the bug
  1. Compile Retroarch on Windows with non-English locale (for example, Russian).
  2. Launch it from MinGW CLI.
  3. Profit.
Bisect Results

[Try to bisect and tell us when this started happening]

Version/Commit

You can find this information under Information/System Information

  • RetroArch: [version/commit]
Environment information
  • OS: [The operating system you're running]
  • Compiler: [In case you are running local builds]

Contributor guide

Open the contributing guide

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

No source file or test is named. First reproduce the issue by compiling RetroArch on Windows with a non-English locale and launching it from a MinGW CLI, then trace how the UI selects language and font assets. Done means the UI falls back to English when the asset font is missing instead of displaying question marks.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
frontend, internationalization
Issue type
Bug
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.