Add missing translations for the Conversation Status

[ussaama]

• Added translations for "Conversation processing", "Conversation Status", and "Conversation Status Details" in German, English, Spanish, French, and Dutch.
• Included new error messages for failed report creation and transcript processing in all supported languages.
• Adjusted line numbers in localization files to ensure accurate mapping to the relevant components.

Summary by CodeRabbit

• New Features

  • Added new localized UI text entries related to conversation status, report creation, and processing across all supported languages.

• Bug Fixes

  • Corrected minor translation errors and improved phrasing in several languages.

• Chores

  • Updated translation files with new keys, adjusted references, and marked obsolete entries to maintain alignment with recent UI changes.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This PR updates all frontend localization files for German, English, Spanish, French, and Dutch. It introduces new translation keys related to conversation and report status, adjusts source code references, marks obsolete entries, and refreshes message content in the corresponding .ts and .po files. No application logic is touched.

Changes

Files	Change Summary
echo/frontend/src/locales/*.po	Updated translation entries: added new keys for conversation/report status, marked obsolete entries, adjusted source references, and minor corrections in translation strings.
echo/frontend/src/locales/*.ts	Replaced message JSON data: added new translation keys/values, refreshed existing translations, no code or export changes.

Possibly related PRs

• Dembrane/echo#196: Adds a new translation entry and updates error handling/UI state for finishing a conversation in the participant portal; overlaps at the localization content level.
• Dembrane/echo#126: Blocks empty conversations from selection and adds related translation keys; some new keys in this PR are directly included in the current localization update.

LGTM. 🚀

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 2b720f6 and 1d9ce8c.

📒 Files selected for processing (10)

• echo/frontend/src/locales/de-DE.po (50 hunks)
• echo/frontend/src/locales/de-DE.ts (1 hunks)
• echo/frontend/src/locales/en-US.po (51 hunks)
• echo/frontend/src/locales/en-US.ts (1 hunks)
• echo/frontend/src/locales/es-ES.po (50 hunks)
• echo/frontend/src/locales/es-ES.ts (1 hunks)
• echo/frontend/src/locales/fr-FR.po (50 hunks)
• echo/frontend/src/locales/fr-FR.ts (1 hunks)
• echo/frontend/src/locales/nl-NL.po (52 hunks)
• echo/frontend/src/locales/nl-NL.ts (1 hunks)

✨ 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.

[cursor]

Bug: Translation Bugs: Incorrect Placeholder Usage

The French and Spanish translations for the message "Only the {0} finished {1} will be included in the report right now." are incorrect.

In French, the word "conversations" is hardcoded, leading to redundant phrases (e.g., "conversations terminées conversations"). In Spanish, "conversaciones" (plural) is hardcoded, causing grammatical errors when the count is singular (e.g., "1 conversaciones finalizadas conversation").

Both translations fail to properly utilize the {1} placeholder for dynamic singular/plural forms of the noun.

echo/frontend/src/locales/fr-FR.po#L1306-L1309

echo/echo/frontend/src/locales/fr-FR.po

Lines 1306 to 1309 in 1d9ce8c

	#: src/components/report/CreateReportForm.tsx:73
	msgid "Only the {0} finished {1} will be included in the report right now. "
	msgstr "Seules les {0} conversations terminées {1} seront incluses dans le rapport en ce moment. "

echo/frontend/src/locales/es-ES.po#L308-L309

echo/echo/frontend/src/locales/es-ES.po

Lines 308 to 309 in 1d9ce8c

	#: src/components/conversation/AutoSelectConversations.tsx:36

Fix in Cursor • Fix in Web

---

Was this report helpful? Give feedback by reacting with 👍 or 👎