Update French translation

[surfdude29]

After updating the German translation with the huge help of two native speakers (the PR is now finished and awaiting review), I decided to also have a go at updating the French translation.

Thanks to the great efforts of @ansh and translators (including most notably @Signez and @fenarinarsa, from looking at previous PRs), the French translation is already a lot more complete which meant that there was much less for me to do to bring it up-to-date.

I again used DeepL, I tried to follow the conventions and existing translations for terms and because, unlike German, I do actually speak French (although definitely not to the level of a native speaker), I also combined that with my own French knowledge to come up with the suggested changes in this PR.

I did check it carefully, but as I'm not a native speaker and my French could most certainly be categorised as "rusty", there are doubtless quite a few errors, awkward phrasings, etc.

So if there are any native French speakers who feel like giving it a look and suggesting changes, that would be greatly appreciated 🙏

[Signez]

Hey there! Thanks a lot for such an awesome translation.

As you took all the time to translate those strings (a thing that I postponed for months, literaly), I wanted to both thank you again for this work, and not only review this translation, but also add a lot of guidance/explanations for all the changes I suggest you to do to it.

Please don't feel it as a negative way: you did a spectacular job on this translation, and the vast majority of the new strings are very well translated and edited. But as you may have noticed, French is such a rusty language (it's not you, it's us®) that there are a lot of subtilités to it that are very hard to grasp.

[Signez]

Oh, and I am sorry, but I think I disagree with the translation of tag by étiquette.

In other similar softwares, tag is translated to hashtag (in Mastodon), tag (in Threads), and other software prefer to use the word mot-clé (mots-clés as plural, literally keyword). Let's note that France Termes tried to push for mot-dièse but it was never really used by users beside jokes about how lame it was.

I have a preference for mot-clé, so if you're up to the task, I would suggest a quick find-and-replace of étiquettes into mots-clés and étiquette into mot-clé. Beware, while étiquette is feminine, mot-clé is masculine!

[surfdude29]

Thank you so much for your carefully-considered, patiently explained and very clear feedback and suggestions, I really appreciate it @Signez! 🙏😊

I have accepted all but two one of your suggestions, which I'd like to clarify further.

[surfdude29]

Oh, and I am sorry, but I think I disagree with the translation of tag by étiquette.

In other similar softwares, tag is translated to hashtag (in Mastodon), tag (in Threads), and other software prefer to use the word mot-clé (mots-clés as plural, literally keyword). Let's note that France Termes tried to push for mot-dièse but it was never really used by users beside jokes about how lame it was.

I have a preference for mot-clé, so if you're up to the task, I would suggest a quick find-and-replace of étiquettes into mots-clés and étiquette into mot-clé. Beware, while étiquette is feminine, mot-clé is masculine!

I have to confess that I chose étiquette simply because it seemed the more likely of the two options between étiquette and balise that were listed as the translations for tag (in the computing sense) in the dictionary entry I looked at:

Anyway, I have no strong feelings on the matter and I'm happy to use mot-clé. I've done the find-and-replace and (I hope) adjusted the surrounding words correctly, but if you could double-check that all is in order that would be brilliant, thanks.

[surfdude29]

Also, should the (for now) single usage of Hashtag be left as-is or translated as Mot-clé?

social-app/src/locale/locales/fr/messages.po

Line 1666 in 1096c8a

msgstr "Hashtag : {tag}"

For context, it's an accessibilityLabel:

social-app/src/components/RichText.tsx

Lines 190 to 191 in 8b0e575

	accessibilityLabel: _(msg`Hashtag: #${tag}`),
	accessibilityHint: _(msg`Click here to open tag menu for #${tag}`),

There are other strings including hashtag that have recently been added to the codebase but the .po files have not yet been updated with them.

[surfdude29]

I've made some other minor changes which I hope should be self-explanatory, but if they look iffy to you please let me know.

There should always be a space before a colon in fr-FR, either a regular one (if you don't know how to input a non-breaking space one, or don't care to) or a non-breaking space one.

💡 Tip! If there are two parts for the typographic sign, there should a non-breaking space next to it in fr-FR. Works with !, ?, : and ;!

I've also done a find-and-replace to add non-breaking spaces before !, ? and : (there aren't any ;) and immediately inside the guillemets, but not between words in the guillemets. For example, in « For You » there is a non-breaking space before For and after You but not between For and You. Is that correct?

[surfdude29]

One other thing I wanted to double-check is the translation of repository, in the context of downloading your account data. DeepL suggested dépôt and I thought I'd go with that; do you think that will be understandable to most users in these contexts?

social-app/src/locale/locales/fr/messages.po

Lines 1133 to 1135 in 1096c8a

	#: src/view/screens/Settings/index.tsx:755
	msgid "Download Bluesky account data (repository)"
	msgstr "Télécharger les données du compte Bluesky (dépôt)"

social-app/src/locale/locales/fr/messages.po

Lines 3959 to 3961 in 1096c8a

	#: src/view/screens/Settings/ExportCarDialog.tsx:75
	msgid "This feature is in beta. You can read more about repository exports in <0>this blogpost.</0>"
	msgstr "Cette fonctionnalité est en version bêta. Vous pouvez en savoir plus sur les exportations de dépôts dans <0>ce blogpost.</0>"

social-app/src/locale/locales/fr/messages.po

Lines 4548 to 4550 in 1096c8a

	#: src/view/screens/Settings/ExportCarDialog.tsx:47
	msgid "Your account repository, containing all public data records, can be downloaded as a \"CAR\" file. This file does not include media embeds, such as images, or your private data, which must be fetched separately."
	msgstr "Le dépôt de votre compte, qui contient toutes les données publiques, peut être téléchargé sous la forme d’un fichier « CAR ». Ce fichier n’inclut pas les éléments multimédias, tels que les images, ni vos données privées, qui doivent être récupérées séparément."

[Signez]

Also, should the (for now) single usage of Hashtag be left as-is or translated as Mot-clé?

I think we should always use mot-clé, to make sure it’s always consistent thorough the product (including accessibility labels).

I've also done a find-and-replace to add non-breaking spaces before !, ? and : (there aren't any ;) and immediately inside the guillemets, but not between words in the guillemets.

You did well! I just checked the diff and it looks perfect.

For example, in « For You » there is a non-breaking space before For and after You but not between For and You. Is that correct?

It's correct! 👍

One other thing I wanted to double-check is the translation of repository, in the context of downloading your account data. DeepL suggested dépôt and I thought I'd go with that; do you think that will be understandable to most users in these contexts?

I spotted the usage of dépôt and I think it's a good translation; it's already the one used by some Git-related software for repository—we even say it orally sometimes (I've already suggested to a colleague to check something directly on GitHub by saying Tu peux directement vérifier ça dans le dépôt GitHub, tu verras bien), which is one of the best proof of a good translation choice imho :)

[Signez]

Beside this last comment change (which is very minor) and the atténué one, I think this is good to merge.

Pinging @ansh about it; if it means anything, please consider this localization update approved by myself :D

[surfdude29]

Also, should the (for now) single usage of Hashtag be left as-is or translated as Mot-clé?

I think we should always use mot-clé, to make sure it’s always consistent thorough the product (including accessibility labels).

Makes sense to me 👍

I've also done a find-and-replace to add non-breaking spaces before !, ? and : (there aren't any ;) and immediately inside the guillemets, but not between words in the guillemets.

You did well! I just checked the diff and it looks perfect.

Great 👍

For example, in « For You » there is a non-breaking space before For and after You but not between For and You. Is that correct?

It's correct! 👍

👍

One other thing I wanted to double-check is the translation of repository, in the context of downloading your account data. DeepL suggested dépôt and I thought I'd go with that; do you think that will be understandable to most users in these contexts?

I spotted the usage of dépôt and I think it's a good translation; it's already the one used by some Git-related software for repository—we even say it orally sometimes (I've already suggested to a colleague to check something directly on GitHub by saying Tu peux directement vérifier ça dans le dépôt GitHub, tu verras bien), which is one of the best proof of a good translation choice imho :)

Hehe nice :)

[surfdude29]

Beside this last comment change (which is very minor) and the atténué one, I think this is good to merge.

Pinging @ansh about it; if it means anything, please consider this localization update approved by myself :D

Excellent, thank you so much @Signez! 😊

[surfdude29]

The .po files have just been updated, so I've merged in the changes and resolved the conflicts. I've also added translations for the handful of new strings, trying to follow previous translations, so hopefully they won't need too much fixing 🤞

@Signez: If you have a chance to take a look sometime that would be great 🙏

[Signez]

Looks good to me! 👍

[surfdude29]

Merci beaucoup @Signez ! :)

[pfrazee]

Thank you everyone!!

[surfdude29]

Thanks! 💫