Change basic settings language text

[ussaama]

• added translations

Summary by CodeRabbit

• New Features

  • Added and updated translations for German, Spanish, French, and Dutch, providing more comprehensive localization coverage across the application.

• Bug Fixes

  • Updated the description for the language selection field to clarify that the selected language is used only for the Participant's Portal, not for transcription.

• Documentation

  • Improved translation metadata, comments, and placeholder descriptions in localization files for better clarity and maintainability.

[coderabbitai]

Walkthrough

This update revises the description for the language selection in the ProjectPortalEditor, clarifying it applies only to the Participant's Portal, not transcription. Corresponding localization files in German, Spanish, French, Dutch, and English are updated to match, with new translations, metadata tweaks, and obsolete string removal. No logic or control flow changes.

Changes

File(s)	Change Summary
ProjectPortalEditor.tsx	Updated language field description to reference only the Participant's Portal.
locales/en-US.po, locales/fr-FR.po, locales/de-DE.po,	Updated translation metadata, added new entry for the revised language description,
locales/es-ES.po, locales/nl-NL.po	marked obsolete the previous string, and adjusted source references.
locales/en-US.ts, locales/fr-FR.ts, locales/de-DE.ts,	Replaced JSON string for messages; added/updated translation for the new language description.
locales/es-ES.ts, locales/nl-NL.ts

Sequence Diagram(s)

LGTM—no new features or control flow changes, so no sequence diagram needed.

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a14575d and a6fe45e.

📒 Files selected for processing (11)

• echo/frontend/src/components/project/ProjectPortalEditor.tsx (1 hunks)
• echo/frontend/src/locales/de-DE.po (20 hunks)
• echo/frontend/src/locales/de-DE.ts (1 hunks)
• echo/frontend/src/locales/en-US.po (19 hunks)
• echo/frontend/src/locales/en-US.ts (1 hunks)
• echo/frontend/src/locales/es-ES.po (25 hunks)
• echo/frontend/src/locales/es-ES.ts (1 hunks)
• echo/frontend/src/locales/fr-FR.po (25 hunks)
• echo/frontend/src/locales/fr-FR.ts (1 hunks)
• echo/frontend/src/locales/nl-NL.po (19 hunks)
• echo/frontend/src/locales/nl-NL.ts (1 hunks)

🧰 Additional context used

🧬 Code Graph Analysis (4)

echo/frontend/src/locales/es-ES.ts (1)

echo/frontend/src/locales/en-US.ts (1)

• messages (1-1)

echo/frontend/src/locales/de-DE.ts (1)

echo/frontend/src/locales/en-US.ts (1)

• messages (1-1)

echo/frontend/src/locales/nl-NL.ts (1)

echo/frontend/src/locales/en-US.ts (1)

• messages (1-1)

echo/frontend/src/locales/fr-FR.ts (1)

echo/frontend/src/locales/en-US.ts (1)

• messages (1-1)

🔇 Additional comments (57)

echo/frontend/src/components/project/ProjectPortalEditor.tsx (1)

265-265: LGTM! Clean localization update

This change tightens up the language description to be more precise about scope. Removing the transcription reference makes the UX clearer for users. The lingui implementation is solid and this kind of focused copy improvement is exactly what you want to see.

echo/frontend/src/locales/en-US.ts (1)

1-1:

Details

❓ Verification inconclusive

Verify translation tooling handled this correctly

Wholesale replacement of locale files makes it impossible to review individual translation changes. While the technical implementation is solid (proper TS types, JSON parsing), this approach is risky without proper tooling verification.

Can you confirm this was generated by your i18n extraction/compilation process rather than manual editing? For future changes, consider showing diffs of the extracted translations before compilation.

---

🏁 Script executed:

#!/bin/bash
# Verify the new translation key exists and old ones were properly migrated
echo "Checking for the new portal-only language description..."
if grep -q "Gbd5HD" echo/frontend/src/locales/en-US.ts; then
    echo "✅ New translation key found"
else
    echo "❌ New translation key missing"
fi

echo "Verifying critical translation keys are preserved..."
grep -E "(You are not authenticated|Something went wrong|Language)" echo/frontend/src/locales/en-US.ts | head -3

Length of output: 30676

---

Translation File Verified: Keys Present

✅ Confirmed the new Gbd5HD key is in echo/frontend/src/locales/en-US.ts
✅ Critical translations like “You are not authenticated”, “Something went wrong” and “Language” remain unchanged

• echo/frontend/src/locales/en-US.ts: all expected keys are present

Can you still confirm this file was produced by your standard i18n extraction/compilation process (not hand-edited)? For future updates, it’d help to review the pre-compiled diffs from your tooling to track only the intended changes.

echo/frontend/src/locales/nl-NL.ts (1)

1-1:

Details

❓ Verification inconclusive

Same wholesale replacement concerns as en-US.ts

Identical technical implementation to the English locale file - clean TypeScript and proper JSON parsing. But same review challenges apply: can't verify individual translation accuracy or ensure nothing was lost in the replacement.

Should contain the Dutch translation for the new portal language description. Let's verify consistency across locale files:

---

🏁 Script executed:

#!/bin/bash
# Check that Dutch locale has the corresponding translation key
echo "Verifying Dutch translation consistency..."
if grep -q "Gbd5HD" echo/frontend/src/locales/nl-NL.ts; then
    echo "✅ Dutch translation key found"
    # Extract the Dutch translation to verify it makes sense
    grep -o '"Gbd5HD":\[[^]]*\]' echo/frontend/src/locales/nl-NL.ts
else
    echo "❌ Dutch translation key missing"
fi

echo "Checking a few key Dutch translations are preserved..."
grep -E "(niet ingelogd|Er is iets fout|Taal)" echo/frontend/src/locales/nl-NL.ts | head -3

Length of output: 35935

---

Dutch locale has the portal translation key in place LGTM.
Technical implementation is spot‐on (clean TS import + JSON parse) and we’ve confirmed:

• “Gbd5HD” exists with the Dutch portal description.
• Core messages (“niet ingelogd”, “Serverfout”, “Taal”) are intact.

Still, complete file swaps make it hard to audit every line. Recommend a quick manual spot-check on critical entries—especially the new portal language message—to ensure no nuance was lost.

echo/frontend/src/locales/fr-FR.ts (1)

1-1: LGTM on the localization update!

Standard lingui format with complete JSON replacement - this is how these translation files typically get updated. The structure is solid and follows the expected pattern.

echo/frontend/src/locales/fr-FR.po (2)

1847-1849: Solid translation update for the key change!

The new French translation "Cette langue sera utilisée pour le Portail du participant." correctly removes the transcription reference and aligns perfectly with the PR objective. Clean implementation.

---

58-65: All the translation additions and updates look clean!

Standard PO file maintenance with proper French translations. The line number updates and new message additions follow gettext best practices. Translations are grammatically solid.

Also applies to: 272-274, 288-290, 292-294, 637-640, 668-671, 961-965, 1002-1010, 1033-1036, 1053-1056, 1126-1129, 1155-1159, 1311-1320, 1427-1430, 1472-1475, 1541-1544, 1627-1630, 1643-1646, 1683-1686, 1726-1729

echo/frontend/src/locales/es-ES.ts (2)

1-1: LGTM – Spanish translations align with English update
The updated messages correctly reflect the new wording for “Language” in the Participant’s Portal (e.g., key Gbd5HD). All other UI strings appear properly translated and match the English source.

---

1-1:

Details

✅ Verification successful

Verify translation key parity with English locale
Ensure no missing or stale keys (e.g., old transcription entries) slipped through.

---

🏁 Script executed:

#!/bin/bash
# Compare locale keys between Spanish and English
grep -Po '"\K[^"]+(?=":\[)' echo/frontend/src/locales/es-ES.ts > es_keys.txt
grep -Po '"\K[^"]+(?=":\[)' echo/frontend/src/locales/en-US.ts > en_keys.txt
echo "Missing in Spanish:"
comm -23 <(sort en_keys.txt) <(sort es_keys.txt)
echo "Obsolete in Spanish:"
comm -13 <(sort en_keys.txt) <(sort es_keys.txt)

Length of output: 565

---

Let’s pivot to a grep-based diff since comm isn’t available. This will list keys in one file not found in the other:

---

🏁 Script executed:

#!/bin/bash
# Extract and sort unique keys
grep -Po '"\K[^"]+(?=":\[)' echo/frontend/src/locales/en-US.ts | sort -u > en_keys.txt
grep -Po '"\K[^"]+(?=":\[)' echo/frontend/src/locales/es-ES.ts | sort -u > es_keys.txt

echo "Missing in Spanish:"
grep -Fxv -f es_keys.txt en_keys.txt || echo "(none)"

echo "Obsolete in Spanish:"
grep -Fxv -f en_keys.txt es_keys.txt || echo "(none)"

Length of output: 373

---

Translation keys in sync between en-US and es-ES
All locale keys match—no missing or obsolete entries detected. LGTM.

• echo/frontend/src/locales/en-US.ts
• echo/frontend/src/locales/es-ES.ts

echo/frontend/src/locales/de-DE.po (10)

58-58: Placeholder comment for conversation count added
Adds an explicit placeholder reference for the project’s conversation count expression, improving context and maintainability. LGTM!

---

999-999: Updated source reference for “Name A–Z”
The component path/line number was bumped to match the latest code. Translation remains accurate.

---

1003-1003: Updated source reference for “Name Z–A”
Syncs the reference with the updated component location; no changes to the German text.

---

1008-1009: German translation for “New” added
Converts the previously fuzzy entry into a concrete translation ("Neu"). Perfect!

---

1029-1029: Updated source reference for “Newest First”
Aligns the reference comment with the new code location; translation is already correct.

---

1122-1122: Updated source reference for “Oldest First”
Reference lines adjusted to match current component; German string remains valid.

---

1468-1468: Updated source reference for “Reset All Options”
Moves the reference to the latest line in the ConversationAccordion. No translation impact.

---

1623-1623: Updated source reference for “Shortest First”
Ensures the comment points to the correct file/line. Translation unchanged and correct.

---

1639-1639: Updated source reference for “Show duration”
Reference updated to the new component location; msgstr remains accurate.

---

1847-1849: Simplified portal-language msgid and translation
The msgid was shortened to “This language will be used for the Participant’s Portal.” and the German translation updated to match. Text is now consistent with the UI context.

echo/frontend/src/locales/es-ES.po (21)

58-61: Placeholder reference updated
The placeholder comment now reflects the correct project conversation count logic. LGTM.

---

271-273: Accurate Spanish translation
"Audio Processing In Progress" translated as "Procesamiento de audio en progreso" is clear and idiomatic. LGTM.

---

287-289: Translation preserved meaning
The translation for "Automatically includes relevant conversations for analysis without manual selection" is faithful and well-structured. LGTM.

---

291-293: Simple string translation
"Available" → "Disponible" is correct and concise. LGTM.

---

427-430: Reference update & translation
The new file reference is accurate and "Conversations" → "Conversaciones" is correct. LGTM.

---

608-610: Added reference & translation check
The added component reference is spot-on and "Empty" → "Vacío" is correct. LGTM.

---

1003-1006: Reference adjustment & translation
Reference line updated and "Name A-Z" → "Nombre A-Z" maintains clarity. LGTM.

---

1007-1010: Reference adjustment & translation
Reference line updated and "Name Z-A" → "Nombre Z-A" is consistent. LGTM.

---

1011-1014: New translation added
"New" → "Nuevo" is correctly added. LGTM.

---

1033-1036: Reference update & translation
"Newest First" → "Más nuevos primero" reads naturally. LGTM.

---

1053-1056: Comprehensive translation update
Long string translation is accurate and context-aware. LGTM.

---

1126-1129: Reference update & translation
"Oldest First" → "Más antiguos primero" is correct. LGTM.

---

1155-1159: Multiple reference updates
Added two references for "Options" → "Opciones" correctly. LGTM.

---

1627-1630: Reference update & translation
"Shortest First" → "Más corto primero" looks clean. LGTM.

---

1643-1646: New option translation
"Show duration" → "Mostrar duración" is precise. LGTM.

---

1661-1663: Updated translation for status message
Complex sentence matches original intent. LGTM.

---

1683-1686: Reference update & translation
"Sort" → "Ordenar" is correct. LGTM.

---

1817-1821: Obsolete reference removal and translation refresh
The updated reference and translation for processing status is accurate. LGTM.

---

2026-2029: Feature label translation
"Upgrade" → "Actualizar" is spot-on. LGTM.

---

2031-2033: Extended feature description translation
The long descriptive translation matches perfectly. LGTM.

---

2035-2037: Button label translation
"Upload" → "Subir" is correct. LGTM.

echo/frontend/src/locales/de-DE.ts (1)

1-1: LGTM! Clean localization update, ship it! 🚀

The German translation is spot-on and the clarification about language scope for the Participant's Portal is solid engineering. Perfect JSON structure, proper TypeScript export pattern - this is how you do i18n right.

echo/frontend/src/locales/en-US.po (5)

63-63: Clarify placeholder source for conversation count.
The added placeholder comment precisely documents the fallback logic (project?.conversations_count ?? project?.conversations?.length ?? 0), improving clarity for future maintainers. LGTM.

---

444-444: Update source reference for “Conversations”.
The updated reference (ConversationAccordion.tsx:739) keeps metadata in sync after code shifts. LGTM.

---

632-632: Update source reference for “Empty”.
The new location (ConversationAccordion.tsx:446) accurately reflects the current code layout. LGTM.

---

1901-1902: Mark obsolete translation for transcription mention.
Commenting out the old "Participant's Portal and transcription" entry cleans up deprecated text. LGTM.

---

1912-1915: Introduce updated translation for Participant’s Portal.
The new string "This language will be used for the Participant's Portal." aligns with the UI change and removes transcription reference. LGTM.

echo/frontend/src/locales/nl-NL.po (12)

58-58: LGTM: placeholder meta updated.
The new placeholder comment for the conversation count expression is correctly added and matches the code reference.

---

500-502: LGTM: added translation for “Conversations”.
The new entry aligns with other locales and follows the established pattern.

---

722-724: LGTM: added translation for “Empty”.
The msgid/msgstr pair is accurate and consistent with UI terminology.

---

1120-1122: LGTM: added “Longest First” sorting label.
Translation is clear and consistent with other sort options.

---

1161-1163: LGTM: added “Name A-Z” label.
Correct Dutch translation for the alphabetical sort option.

---

1165-1167: LGTM: added “Name Z-A” label.
Translation is precise and follows project terminology.

---

1191-1193: LGTM: added “Newest First” label.
Matches the English msgid and fits the sorting context.

---

1211-1213: LGTM: inserted “No conversations found” instruction.
The Dutch phrasing clearly guides users and mirrors the source.

---

1291-1293: LGTM: added “Oldest First” label.
Translation properly reflects the reverse-sort option.

---

1503-1505: LGTM: updated “Processing failed” message.
The new msgid/msgstr pair accurately describes the failure state.

---

1843-1845: LGTM: added “Shortest First” label.
Consistent with other sorting labels and correctly translated.

---

2072-2073: LGTM: updated portal language description.
The original combined translation is correctly marked obsolete and replaced with the shorter, accurate msgid/msgstr pair.

Also applies to: 2083-2085

[coderabbitai]

🧹 Nitpick (assertive)

Optional: Externalize the large JSON payload
Inlining a massive JSON.parse blob can bloat bundles and hurt readability/maintainability. Consider moving this into a standalone .json (or using Lingui’s defineMessages) and importing it instead.

🤖 Prompt for AI Agents

In echo/frontend/src/locales/es-ES.ts at line 1, the large JSON string is
inlined using JSON.parse, which can bloat the bundle and reduce readability. To
fix this, extract the JSON content into a separate .json file and import it
here, or alternatively use Lingui's defineMessages function to manage the
messages more cleanly. This will improve maintainability and reduce bundle size.