Skip to content

i18n(fr): update UI strings#119

Merged
dreyfus92 merged 1 commit into
withstudiocms:mainfrom
ArmandPhilippot:i18n/fr-update-ui-strings
Apr 21, 2025
Merged

i18n(fr): update UI strings#119
dreyfus92 merged 1 commit into
withstudiocms:mainfrom
ArmandPhilippot:i18n/fr-update-ui-strings

Conversation

@ArmandPhilippot
Copy link
Copy Markdown
Member

@ArmandPhilippot ArmandPhilippot commented Apr 21, 2025

Description

Updates French UI strings (fr.json and starlight-sidebar/fr.json) with changes from #73.

Summary by CodeRabbit

  • New Features
    • Added new French translations for quick update instructions and various documentation topics, including guides, database guides, upgrade, version guides, and latest update guides.

@ArmandPhilippot ArmandPhilippot requested a review from a team as a code owner April 21, 2025 14:25
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Apr 21, 2025

Walkthrough

This update adds new French translation entries to two localization JSON files. The src/content/i18n/fr.json file receives a new key for a "quick-update" message, while src/starlight-sidebar/fr.json gains five new keys related to documentation topics such as guides, upgrades, and versions. Both files also have a minor formatting change with the addition of trailing commas to accommodate the new entries. No existing translations were altered or removed.

Changes

File(s) Change Summary
src/content/i18n/fr.json Added "quick-update" translation entry and a trailing comma after the previous entry.
src/starlight-sidebar/fr.json Added five new documentation-related translation entries; added a trailing comma to the previous entry.

Possibly related PRs

  • i18n(es): update ui strings #105: Adds the same new translation keys and values for "quick-update" and sidebar entries in Spanish, indicating parallel localization updates.

Suggested labels

i18n

Suggested reviewers

  • dreyfus92

Poem

A rabbit hopped through fields of code,
Adding French words to lighten the load.
"Quick update!" it cheered, with a sidebar so neat—
Guides and upgrades, now all in French complete!
With commas in place, translations aligned,
The docs are now ready—so easy to find!
🐇✨

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)
  • We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.

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
🪧 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.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate unit testing code.
    • @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.

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

@studiocms-no-reply
Copy link
Copy Markdown
Member

Lunaria Status Overview

🌕 This pull request will trigger status changes.

Learn more

By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.

You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File Note
src/content/i18n/fr.json Localization changed, will be marked as complete.
src/starlight-sidebar/fr.json Localization changed, will be marked as complete.
Warnings reference
Icon Description
🔄️ The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (1)
src/content/i18n/fr.json (1)

47-48: Ensure key naming & punctuation consistency

  1. The key "quick-update" diverges from the dot‑notation pattern used elsewhere (e.g. "docsearch.noResultsScreen.reportMissingResultsLinkText"). Confirm it aligns with your i18n lookup conventions or consider renaming (e.g. "content.quickUpdate").
  2. The instruction string ends without a colon. Since it introduces a command, you might add one for clarity:
    "Mettez rapidement à jour vers la dernière version en exécutant la commande suivante :"
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between a08f79c and 58f638b.

📒 Files selected for processing (2)
  • src/content/i18n/fr.json (1 hunks)
  • src/starlight-sidebar/fr.json (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Run Starlight Link Check

Comment on lines +15 to +20
"auto-gen": "Génération auto",
"topic-guides": "Guides et tutoriels",
"database": "Guides des bases de données",
"upgrade": "Mise à niveau",
"version": "Guides des versions",
"latest": "Guide de la dernière mise à jour"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

Verify integration of new sidebar translation keys
You’ve added keys ("topic-guides", "database", "upgrade", "version", "latest"). Please ensure the sidebar component actually references these, for example by running:

to catch any missing usages.


🏁 Script executed:

rg -nE '"topic-guides"|"database"|"upgrade"|"version"|"latest"' -C2 src

Length of output: 165


🏁 Script executed:

#!/bin/bash
# Re-run search with correct ripgrep flags to locate uses of the new translation keys
rg -n -e '"topic-guides"' -e '"database"' -e '"upgrade"' -e '"version"' -e '"latest"' -C2 src

Length of output: 2602


Add references to the new sidebar translation keys in the component
The keys ("topic-guides", "database", "upgrade", "version", "latest") are defined in each src/starlight-sidebar/*.json but aren’t referenced anywhere in the codebase. You’ll need to update your sidebar component (e.g. wherever you build the menu items) to use these keys via your i18n lookup.

• Translation files:

  • src/starlight-sidebar/en.json (lines 16–20)
  • src/starlight-sidebar/fr.json (lines 16–20)
  • src/starlight-sidebar/es.json (lines 16–20)
  • src/starlight-sidebar/de.json (lines 16–20)
  • src/starlight-sidebar/ko.json (lines 16–20)

Please integrate these keys into the sidebar configuration or remove them if they’re not needed.

Copy link
Copy Markdown
Member

@dreyfus92 dreyfus92 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @ArmandPhilippot 🫡

@dreyfus92 dreyfus92 merged commit 224ea1d into withstudiocms:main Apr 21, 2025
8 checks passed
@ArmandPhilippot ArmandPhilippot deleted the i18n/fr-update-ui-strings branch April 21, 2025 15:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants