Skip to content

Conversation

@HiDeoo
Copy link
Member

@HiDeoo HiDeoo commented Feb 16, 2025

Description

This PR updates the French version of the reference/plugins & guides/i18n pages with the changes from #2390 and #2578.

@changeset-bot
Copy link

changeset-bot bot commented Feb 16, 2025

⚠️ No Changeset found

Latest commit: db70ec7

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@github-actions github-actions bot added i18n Anything to do with internationalization & translation efforts 📚 docs Documentation website changes labels Feb 16, 2025
@netlify
Copy link

netlify bot commented Feb 16, 2025

Deploy Preview for astro-starlight ready!

Name Link
🔨 Latest commit db70ec7
🔍 Latest deploy log https://app.netlify.com/sites/astro-starlight/deploys/67b233edecbd8b0008fa2c35
😎 Deploy Preview https://deploy-preview-2886--astro-starlight.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 99 (🔴 down 1 from production)
Accessibility: 100 (no change from production)
Best Practices: 100 (no change from production)
SEO: 100 (no change from production)
PWA: -
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify site configuration.

@astrobot-houston
Copy link
Contributor

astrobot-houston commented Feb 16, 2025

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

Locale File Note
fr guides/i18n.mdx Localization changed, will be marked as complete.
fr reference/plugins.md 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
Contributor

@trueberryless trueberryless left a comment

Choose a reason for hiding this comment

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

Very good translations! I really like how you interchanged the en and fr locals at the end of plugin reference to demonstrate it exactly like the English version, but for all the French people ❤️

Left some thoughts about some parts where I - as a non-native - can't conclude whether something was overlooked or intentional.

// module-extension.ts
export default {
name: 'plugin-avec-traductions',
name: 'plugin-use-translations',
Copy link
Contributor

Choose a reason for hiding this comment

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

same here, I think it is just a coincidence that it translates to the same (although traductions seems like a valid translation for translations too)... Probably best if the native speakers resolve these comments.

Copy link
Member

Choose a reason for hiding this comment

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

Probably an oversight, thanks trueberryless!

However it seems plugin-use-translations is used in multiple places across the file, so if we update the plugin name we might need to update the other occurrences as well.

Copy link
Member Author

Choose a reason for hiding this comment

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

This one is tricky (in my head ^^), I initially translated it, then thought the name was not about using translations but the useTranslations() function being documented in this section, so I partially translated it to module-extension-use-translation, ended up not liking it and reverting back to the English version.

😅

Copy link
Member

Choose a reason for hiding this comment

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

Oh, I didn't make the connection with useTranslations! 😆 For me, it was just to show the contrast with the other snippet l85: plugin-with-translations/plugin-avec-traductions. So, here I would use plugin-use-translations/plugin-utilisant-traductions. But, yeah, we could use module-extension to be consistent (l85 as well).

Copy link
Member Author

Choose a reason for hiding this comment

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

Yeah, it was probably my brain seeing hidden things that weren't there like I said 😅 Went ahead and used your suggestion, thanks a lot 🙌

Copy link
Member

@ArmandPhilippot ArmandPhilippot left a comment

Choose a reason for hiding this comment

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

Three little suggestions, otherwise LGTM!

// module-extension.ts
export default {
name: 'plugin-avec-traductions',
name: 'plugin-use-translations',
Copy link
Member

Choose a reason for hiding this comment

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

Probably an oversight, thanks trueberryless!

However it seems plugin-use-translations is used in multiple places across the file, so if we update the plugin name we might need to update the other occurrences as well.

Co-authored-by: Armand Philippot <[email protected]>
@HiDeoo
Copy link
Member Author

HiDeoo commented Feb 16, 2025

Thanks for the great catches. Still not sure about this use-translations ^^ I'll sleep on it and decide something if someone doesn't have a strong opinion on it before.

@trueberryless
Copy link
Contributor

One thing which you could do about the use-translations topic:

I have reviewed the Korean and Russian version and written the German one, all have not translated any of the plugin names...
So you could also just not translate it I guess, but as you like, you know French better then I do 😅

```ts {6-11}
// module-extension.ts
export default {
name: 'ajout-twitter-plugin',
Copy link
Contributor

Choose a reason for hiding this comment

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

For consistency you should also not translate these if you chose to..

import react from '@astrojs/react';

export default {
name: 'plugin-utilisant-react',
Copy link
Contributor

Choose a reason for hiding this comment

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

and that

```ts {6}
// module-extension.ts
export default {
name: 'plugin-long-processus',
Copy link
Contributor

Choose a reason for hiding this comment

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

and one over here and so on...

@HiDeoo
Copy link
Member Author

HiDeoo commented Feb 16, 2025

I have reviewed the Korean and Russian version and written the German one, all have not translated any of the plugin names...
So you could also just not translate it I guess, but as you like, you know French better then I do 😅

Yeah, this is something up to translators and that has been consistently done in the French versions where it doesn't change a meaning or make it harder to understand. I personally think it adds a nice touch to the translation and shows that the translator has put some thought into it.

@HiDeoo HiDeoo merged commit a22d4e6 into withastro:main Feb 16, 2025
15 checks passed
HiDeoo added a commit to HiDeoo/starlight that referenced this pull request Feb 19, 2025
* main: (493 commits)
  i18n(de): update `sidebar.mdx` (withastro#2900)
  Adding all samples for badges in sidebar as example (withastro#2881)
  i18n(fr): fix highlighting in `reference/plugins.md` (withastro#2898)
  i18n(fr): update `reference/plugins` & `guides/i18n` (withastro#2886)
  i18n(fr): update `reference/overrides` & `guides/sidebar` (withastro#2887)
  i18n(fr): add `guides/route-data` and `reference/route-data` (withastro#2884)
  i18n(fr): update `guides/overriding-components` (withastro#2885)
  i18n(fr): update `reference/configuration` (withastro#2888)
  i18n(de): update German translation with withastro#2578 (withastro#2882)
  [ci] format
  i18n(ru): update some translations (withastro#2895)
  i18n(de): update `reference/configuration.mdx` (withastro#2883)
  [ci] format
  i18n(ko-KR): update `configuration.mdx` (withastro#2892)
  i18n(ko-KR): update `overrides.md` (withastro#2893)
  i18n(ko-KR): update `overriding-components.mdx` (withastro#2890)
  i18n(ko-KR): update `i18n.mdx` and `plugins.md` (withastro#2889)
  [ci] format
  i18n(ko-KR): create `guides/route-data.mdx` and `reference/route-data.mdx` (withastro#2896)
  i18n(ko-KR): update `/resources/plugins.mdx` (withastro#2894)
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

📚 docs Documentation website changes i18n Anything to do with internationalization & translation efforts

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants