Skip to content

Review Spanish frontend translations#67

Open
Waterbrain wants to merge 3 commits into
DAB-LABS:mainfrom
Waterbrain:spanish-review-v2
Open

Review Spanish frontend translations#67
Waterbrain wants to merge 3 commits into
DAB-LABS:mainfrom
Waterbrain:spanish-review-v2

Conversation

@Waterbrain

Copy link
Copy Markdown
Contributor

Native Spanish review of the HAIR frontend translation. I also reviewed the Spanish wording for clarity, consistency, and natural Home Assistant terminology rather than doing a literal translation.

If you still need help with any of the other language drafts and no native reviewer is available, I’d be happy to help review them as well, using the same structured process.

What

Reviewed the Spanish frontend translation and polished the user-facing wording across the HAIR interface.

Why

The existing Spanish dictionary was an assistant-generated draft and needed a native-speaker review for natural phrasing, terminology consistency, and clarity.

How

Reviewed the full frontend dictionary entry by entry, preserving the existing keys and placeholders while improving the Spanish text.

Type of Change

  • Bug fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update
  • Refactor (no functional changes)

Checklist

  • I have read the CONTRIBUTING guide
  • pytest passes locally
  • ruff check . passes locally
  • Frontend builds cleanly (npm run build in frontend/)
  • New code has tests where applicable
  • Tested manually on a Home Assistant instance (if applicable)
  • Documentation updated (README, docstrings, etc.)
  • If this PR changes user-facing features, README, or documentation, I have updated llms.txt accordingly.

Screenshots

Not applicable — translation-only change.

Related Issues

Closes #

Native Spanish review of the HAIR frontend translation.
I also reviewed the Spanish wording for clarity, consistency, and natural Home Assistant terminology rather than doing a literal translation.

If you still need help with any of the other language drafts and no native reviewer is available, I’d be happy to help review them as well, using the same structured process.
Restore the Plucker product name in the Spanish locale so the frontend parity test passes.

In Spanish, "Plucker" is not self-explanatory and "Extractor" would be much clearer to users, but the current localization rules treat Plucker as a fixed product name that must remain untranslated.

Leaving the product name unchanged while keeping the surrounding UI text translated as "extraer", "extracción", etc.
Restore the Plucker product name in the Spanish locale so the frontend parity test passes.

In Spanish, "Plucker" is not self-explanatory and "Extractor" would be much clearer to users, but the current localization rules treat Plucker as a fixed product name that must remain untranslated.

Leaving the product name unchanged while keeping the surrounding UI text translated as "extraer", "extracción", etc.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant