## [Bug] Missing or Incomplete Translations in x86 Playground Interface #201

New Issue

2026-05-24T16:57:06Z

enjin2310 commented

2026-05-24 16:57:06 +00:00

🧩 Summary

In the x86 Playground environment, several interface elements and comments remain in English despite the platform being set to Spanish. This inconsistency affects usability and comprehension for Spanish-speaking users, especially in educational contexts.

🧪 Steps to Reproduce

Navigate to learn.spikersoft.com/tools/x86-playground.
Observe the interface panels: Editor, Desensamblado, Memoria de pila, Registros, and Terminal.
Note that while some labels are localized (e.g., “Memoria de pila”), other elements such as comments, initialization messages, and tooltips remain in English.

✅ Expected Behavior

All interface elements and system messages should be fully translated into Spanish, maintaining consistency across the playground.
Example:

“Initializing blink emulator…” → “Inicializando emulador blink…”
“Registers” → “Registros” (already correct)
“Stack Memory” → “Memoria de pila” (already correct)

❌ Actual Behavior

Terminal messages and tooltips remain in English.
Comments in the default assembly template are in English.
Some UI labels and system feedback are untranslated.

📸 Evidence

The attached screenshot shows the x86 Playground interface with mixed English and Spanish text, including:

“Initializing blink emulator … bLink ready!”

🧠 Possible Root Cause

Missing localization keys for emulator messages and code templates.
Static English strings embedded in the assembly environment.
Partial implementation of language switching for technical modules.

### 🧩 Summary In the **x86 Playground** environment, several interface elements and comments remain in English despite the platform being set to Spanish. This inconsistency affects usability and comprehension for Spanish-speaking users, especially in educational contexts. ### 🧪 Steps to Reproduce 1. Navigate to `learn.spikersoft.com/tools/x86-playground`. 2. Observe the interface panels: **Editor**, **Desensamblado**, **Memoria de pila**, **Registros**, and **Terminal**. 3. Note that while some labels are localized (e.g., “Memoria de pila”), other elements such as comments, initialization messages, and tooltips remain in English. ### ✅ Expected Behavior All interface elements and system messages should be fully translated into Spanish, maintaining consistency across the playground. Example: - “Initializing blink emulator…” → **“Inicializando emulador blink…”** - “Registers” → **“Registros”** (already correct) - “Stack Memory” → **“Memoria de pila”** (already correct) ### ❌ Actual Behavior - Terminal messages and tooltips remain in English. - Comments in the default assembly template are in English. - Some UI labels and system feedback are untranslated. ### 📸 Evidence The attached screenshot shows the **x86 Playground** interface with mixed English and Spanish text, including: > “Initializing blink emulator … bLink ready!” ### 🧠 Possible Root Cause - Missing localization keys for emulator messages and code templates. - Static English strings embedded in the assembly environment. - Partial implementation of language switching for technical modules.

Screenshot 2026-05-24 125619.png

198 KiB

spikerj referenced this issue

2026-07-11 23:26:26 +00:00

Serve blog media via nginx static path instead of the API + prod config fixes #473

spikerj commented

2026-07-11 23:52:18 +00:00

Resolved in spikersoft-angular PR #160 (merged to master). The panel labels/status messages from the report were already keyed by the interim i18n overhaul (151 x86Playground keys, en+es complete); the remaining English leaks were the example/default assembly template comments and the snippet menu labels+tooltips. Those are now localized at display time (the SNIPPETS constants stay byte-identical to upstream x64.halb.it for share-payload compatibility): comments swap on snippet insert and on the boot-time default once translations load, and the menu translates with English fallback. Spanish strings are queued under _review in devTools/es.json for a native-speaker pass per the i18n workflow; syscall jargon (sys_write, fd: stdout) deliberately stays English in all locales. Verify visually: switch to es at /tools/x86-playground → File → Examples. Closing.

spikerj closed this issue

2026-07-11 23:52:19 +00:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: spikerj/spikersoft-issues#201