i18n(fr): small rewording and fixes in guides

[ArmandPhilippot]

Description

Updates the French translations in guides to:

• revert some unwanted translations (syntaxe frontale, matière première for frontmatter)
• translate docs
• replace the translation for inline (en ligne is usually the wrong translation)
• fix some bad translations (backticks > accents graves, blockquotes > bloc de citation)
• replace supporte with prend en charge (support is an anglicism)
• use French quotes
• fix some Astro docs links because of updates on the French version
• translate plugin to be consistent with the other docs pages
• add missing space before some punctuation
• respect verb agreement (propriété > utilisée instead of utilisé)
• translate package
• replace actifs (financial/crypto word) with ressources for assets
• use non breaking space before punctuation in some places to avoid:

(note the colon on a new line)

---

One thing I haven't updated for consistency: en-tête/titre. In Astro Docs we use titre for headings while in most places, Starlight uses en-tête. I could have replaced the titre occurrences in authoring-content but I'm a bit torn.
While titre de niveau 2 sounds correct to me, en-tête de niveau 2 sounds unusual to me. So I wasn't sure what to do and so I preferred to leave them as they are. For reference, LibreOffice uses titre in French when the English version uses heading:

French	English

Note: This is not necessarily blocking for this PR since I haven't updated that! But we might want to think about it to make things consistent in a future PR!

[changeset-bot]

⚠️ No Changeset found

Latest commit: bf75055

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

[netlify]

✅ Deploy Preview for astro-starlight ready!

Name	Link
🔨 Latest commit	bf75055
🔍 Latest deploy log	https://app.netlify.com/projects/astro-starlight/deploys/68ca95f4766ec30008bce130
😎 Deploy Preview	https://deploy-preview-3431--astro-starlight.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 100 (no change 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 project configuration.

[astrobot-houston]

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/authoring-content.mdx	Localization changed, will be marked as complete.
fr	guides/css-and-tailwind.mdx	Localization changed, will be marked as complete.
fr	guides/customization.mdx	Localization changed, will be marked as complete.
fr	guides/i18n.mdx	Localization changed, will be marked as complete.
fr	guides/overriding-components.mdx	Localization changed, will be marked as complete.
fr	guides/pages.mdx	Localization changed, will be marked as complete.
fr	guides/project-structure.mdx	Localization changed, will be marked as complete.
fr	guides/site-search.mdx	Localization changed, will be marked as complete.
fr	reference/configuration.mdx	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.

[HiDeoo]

Amazing, definitely some old translations that probably predate both of us in there, really neat update 🙌

Regarding "titre" vs "en-tête", while some websites like MDN or even the W3C use both of them, I think I personally like the explicit different word for headings in the Starlight context. In Starlight, we have the project title in the Astro config that impacts the document <title>, we have the page title in content files that also impacts the document <title> and what is displayed in the <PageTitle/> component. I think having a dedicated word for headings, like in English, can avoid some potential confusions (but maybe I'm wrong).

[ArmandPhilippot]

Thanks for the feedback, I know you've explained this in the past but reading "en-tête de niveau 2" made me doubt. 😅

So, before merging this one, I'll add a new update to make the use of en-tête/title consistent, no need for a separate PR for this!

[ArmandPhilippot]

Done! I spotted another one in reference/configuration so I included it here.

[HiDeoo]

Thanks for the follow-up 🌟