In SpikerSoft Profile → Travel section, when the interface language is set to Spanish, several text boxes display untranslated placeholder tags such as _review. These tags appear instead of the proper localized text, breaking consistency with the English version.
Issue Description
While navigating the Travel section with Spanish selected, multiple UI elements show raw localization keys (e.g., _review Países visitados, _review Estados visitados, _review Mapa de viajes). These placeholders indicate missing or incorrectly mapped translation strings in the Spanish language pack.
Environment
Property
Value
Application
SpikerSoft
Module
Profile → Travel
Environment
Production
Browser
Firefox / Chrome
Operating System
Windows 11
Version
v2026.09.28d
Device
Desktop
Preconditions
User must have Spanish selected as the display language.
Steps to Reproduce
Log in to SpikerSoft.
Navigate to Perfil → Viajes.
Observe the text in the travel statistics boxes and map labels.
Notice that several fields display _review tags instead of translated text.
Expected Result
All text elements should appear correctly localized in Spanish, maintaining the same structure and clarity as the English version.
Actual Result
Several UI elements show untranslated _review tags.
The English version displays proper labels (e.g., “Countries visited”, “States visited”, “Travel Map”).
The Spanish version breaks visual and linguistic consistency.
Evidence
The screenshots show the Travel section with _review tags visible in multiple boxes and labels.
Impact
Reduces readability and professionalism of the Spanish interface.
Confuses users who expect complete localization.
Minor but noticeable quality issue in multilingual support.
Frequency
Always
Reproducibility
100%
Severity
Medium
Suggested Fix
Verify Spanish localization keys for the Travel module.
Ensure all _review placeholders are replaced with proper translations.
Conduct a full audit of the Spanish language pack to confirm consistency across modules.
## Summary
In **SpikerSoft Profile → Travel section**, when the interface language is set to **Spanish**, several text boxes display untranslated placeholder tags such as `_review`. These tags appear instead of the proper localized text, breaking consistency with the English version.
## Issue Description
While navigating the **Travel** section with Spanish selected, multiple UI elements show raw localization keys (e.g., `_review Países visitados`, `_review Estados visitados`, `_review Mapa de viajes`). These placeholders indicate missing or incorrectly mapped translation strings in the Spanish language pack.
## Environment
| Property | Value |
|-----------|--------|
| Application | SpikerSoft |
| Module | Profile → Travel |
| Environment | Production |
| Browser | Firefox / Chrome |
| Operating System | Windows 11 |
| Version | v2026.09.28d |
| Device | Desktop |
## Preconditions
User must have **Spanish** selected as the display language.
## Steps to Reproduce
1. Log in to **SpikerSoft**.
2. Navigate to **Perfil → Viajes**.
3. Observe the text in the travel statistics boxes and map labels.
4. Notice that several fields display `_review` tags instead of translated text.
## Expected Result
All text elements should appear correctly localized in Spanish, maintaining the same structure and clarity as the English version.
## Actual Result
- Several UI elements show untranslated `_review` tags.
- The English version displays proper labels (e.g., “Countries visited”, “States visited”, “Travel Map”).
- The Spanish version breaks visual and linguistic consistency.
## Evidence
- The screenshots show the **Travel** section with `_review` tags visible in multiple boxes and labels.
## Impact
- Reduces readability and professionalism of the Spanish interface.
- Confuses users who expect complete localization.
- Minor but noticeable quality issue in multilingual support.
## Frequency
Always
## Reproducibility
100%
## Severity
Medium
## Suggested Fix
- Verify Spanish localization keys for the **Travel** module.
- Ensure all `_review` placeholders are replaced with proper translations.
- Conduct a full audit of the Spanish language pack to confirm consistency across modules.
Confirmed and fixed — and your report turned out to cover much more than the Travel tab. Thank you!
What was wrong: our Spanish text lives in es.json. When a translation still needs a native speaker to check it, the convention is to list its key in a separate _review checklist inside the file — the app never shows that list. In a few recent changes, the marker was typed into the visible text itself (e.g. "_review Países visitados"). Nothing tested for that, so it slipped through.
How big it was: 104 Spanish strings, not just the three you saw:
65 starting with _review — the Travel tab, the travel map, and the Careers page;
39 more ending in _review — Art Studio's concept regions and two viewer buttons, plus one Space Game error message.
Removed the marker from all 104 strings. The Spanish underneath was already fine.
Kept them queued for native review the correct way, as _review checklist entries.
Added an automated test that fails if _review ever appears inside a visible string again, in any language file.
It will be live with the next deploy. Reopen this if you still see _review anywhere in the Spanish UI.
Confirmed and **fixed** — and your report turned out to cover much more than the Travel tab. Thank you!
**What was wrong:** our Spanish text lives in `es.json`. When a translation still needs a native speaker to check it, the convention is to *list its key* in a separate `_review` checklist inside the file — the app never shows that list. In a few recent changes, the marker was typed *into the visible text itself* (e.g. `"_review Países visitados"`). Nothing tested for that, so it slipped through.
**How big it was:** 104 Spanish strings, not just the three you saw:
- 65 starting with `_review` — the Travel tab, the travel map, and the Careers page;
- 39 more ending in `_review` — Art Studio's concept regions and two viewer buttons, plus one Space Game error message.
**What changed** (spikerj/spikersoft-angular#1407, merged)
- Removed the marker from all 104 strings. The Spanish underneath was already fine.
- Kept them queued for native review the correct way, as `_review` checklist entries.
- Added an automated test that fails if `_review` ever appears inside a visible string again, in any language file.
It will be live with the next deploy. **Reopen this** if you still see `_review` anywhere in the Spanish UI.
spikerj
added the bug label 2026-10-02 03:42:05 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
In SpikerSoft Profile → Travel section, when the interface language is set to Spanish, several text boxes display untranslated placeholder tags such as
_review. These tags appear instead of the proper localized text, breaking consistency with the English version.Issue Description
While navigating the Travel section with Spanish selected, multiple UI elements show raw localization keys (e.g.,
_review Países visitados,_review Estados visitados,_review Mapa de viajes). These placeholders indicate missing or incorrectly mapped translation strings in the Spanish language pack.Environment
Preconditions
User must have Spanish selected as the display language.
Steps to Reproduce
_reviewtags instead of translated text.Expected Result
All text elements should appear correctly localized in Spanish, maintaining the same structure and clarity as the English version.
Actual Result
_reviewtags.Evidence
_reviewtags visible in multiple boxes and labels.Impact
Frequency
Always
Reproducibility
100%
Severity
Medium
Suggested Fix
_reviewplaceholders are replaced with proper translations.Confirmed and fixed — and your report turned out to cover much more than the Travel tab. Thank you!
What was wrong: our Spanish text lives in
es.json. When a translation still needs a native speaker to check it, the convention is to list its key in a separate_reviewchecklist inside the file — the app never shows that list. In a few recent changes, the marker was typed into the visible text itself (e.g."_review Países visitados"). Nothing tested for that, so it slipped through.How big it was: 104 Spanish strings, not just the three you saw:
_review— the Travel tab, the travel map, and the Careers page;_review— Art Studio's concept regions and two viewer buttons, plus one Space Game error message.What changed (spikerj/spikersoft-angular#1407, merged)
_reviewchecklist entries._reviewever appears inside a visible string again, in any language file.It will be live with the next deploy. Reopen this if you still see
_reviewanywhere in the Spanish UI.