Far-Beyond-Pulsar/Pulsar-Native

Inconsistent locale coverage across editor crates — missing ru and empty locale sets

Open

#483 opened on Jul 29, 2026

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Rust (29 forks)auto 404
difficulty: easyenhancementgood first issuehelp wantedpriority: low

Repository metrics

Stars
 (348 stars)
PR merge metrics
 (PR metrics pending)

Description

Summary

The locale coverage across editor crates is inconsistent. Some crates have the ru (Russian) locale, others don't. Two crates have no locale files at all.

Current locale coverage

Crate en zh-CN zh-HK pt-BR it ru lol
ui_common ✅ ✅ ✅ ✅ ✅ ✅ ✅
ui_level_editor ✅ ✅ ✅ ✅ ✅ ✅ ✅
ui_problems ✅ ✅ ✅ ✅ ✅ ✅ ✅
ui_type_debugger ✅ ✅ ✅ ✅ ✅ ✅ ✅
ui_core ✅ ✅ ✅ ✅ ✅ ❌ ✅
ui_file_manager ✅ ✅ ✅ ✅ ✅ ❌ ✅
ui_flamegraph ✅ ✅ ✅ ✅ ✅ ❌ ✅
ui_log_viewer ❌ ❌ ❌ ❌ ❌ ❌ ❌
ui (wgpui-component) ❌ ❌ ❌ ❌ ❌ ❌ ❌

Missing ru locale: ui_core, ui_file_manager, ui_flamegraph No locale files at all: ui_log_viewer (see #479), ui (wgpui-component, see #478)

Additionally, the lol (LOLCAT) locale exists in most crates as a pseudo-locale for testing — it should probably be consistently present or consistently removed.

Suggested fix

  1. Add ru.yml to ui_core, ui_file_manager, and ui_flamegraph (translations can be sourced from the existing ru.yml in ui_common etc.)
  2. Once #478 and #479 are resolved, ensure the new locale files match the supported locale set
  3. Consider establishing a CI check that verifies all editor crates with rust-i18n have the same set of locale files

Contributor guide

Research direction
Investigate how locale files are structured in existing crates (e.g., ui common), compare with the missing crates ui core, ui file manager, ui flamegraph, and plan adding ru.yml files. Also review CI configuration to propose a check for consistent locale sets.
Tech stack
rust
Domain
frontendlocalization
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitRust
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80