Review of French translation

I massively worked on French translation of Plone Core (

You are welcome to comment these translations.



I massively worked on French translation of Plone Core (

You are welcome to comment these translations.

Would this be an opportunity to discuss why the "Page" content-type is
translated by "Document" which is so polysemantic in french that it actually
could apply to "Files", "Images" as well as "Pages"?

When doing training for our new Plone users, they regularly are hesitant as
to how the (french) word "Document" should be understood in Plone context. I
always have to emphasize that what we usually call "une page web" in french
is called "Document" in the "Add" menu, despite the fact that a "File" is
a document!

If this is not the correct place to discuss this subject please tell me
where I should ask.


I fully agree with you: "Page Web" would be much more understandable than "Document". "Page" only, as in English, would be too vague IMHO.

If we'd decide to change this, it would need to review all the strings where the strings "(D|d)ocument(s)" appear in order to be consistent. Currently:

╭─bitouze@drums ~/Public/Repositories/  â€čmasterâ€ș 
╰─➀  rg -w -i 'document|documents' | rg msgstr  
cmfplacefulworkflow.po:msgstr "Vous pouvez ici crĂ©er et configurer vos politiques documentaires. Une politique modifie les processus de vos documents dans ou en dessous d'un dossier. Pour appliquer une politique, vous devez ajouter dans un dossier une configuration locale des processus en choisissant l'entrĂ©e « politique » du menu dĂ©roulant « État »."
atcontenttypes.po:msgstr "Pas de modification pour ce document"
plone.po:msgstr "Ajoute les types Dossier et Document basés sur Dexterity à fins de test"
plone.po:msgstr "Si activé, le portlet n'affichera pas les icÎnes de types de documents"
plone.po:msgstr "Si activé, le portlet n'affichera pas les icÎnes de types de documents."
plone.po:msgstr "Les images peuvent ĂȘtre rĂ©fĂ©rencĂ©es dans les documents ou ĂȘtre affichĂ©es dans un album."
plone.po:msgstr "Charger les fichiers JavaScript de façon différée aprÚs que le document aura été analysé, mais avant « DOMContentLoaded » en ajoutant l'attribut « defer » à la balise « script »."
plone.po:msgstr "Document Microsoft Word"
plone.po:msgstr "Document ODT"
plone.po:msgstr "Document OpenOffice Writer"
plone.po:msgstr "Document PDF"
plone.po:msgstr "Document PS"
plone.po:msgstr "Document"
plone.po:msgstr "Recherche littérale dans le contenu des documents"
plone.po:msgstr "Recherche littérale dans le titre des documents"
plone.po:msgstr "Vue Document"
plone.po:msgstr "Ce site utilise le Gestionnaire Électronique de Documents (GED/CMS) OpenSource ${plone}. Il respecte les recommandations d'accessibilitĂ© descontenus web (Web Content Accessibility Guidelines − ${wcag} au niveau « AA » pour les personnes handicapĂ©es, incluant le manque ou l'absence de vue,la surditĂ© ou un dĂ©faut d'audition, problĂšmes d'apprentissage, limitationscognitives, limitations de mouvements, problĂšmes de langage,photosensibilitĂ©, et les combinaisons de ceux-ci."
plone.po:msgstr "affiche une file de documents en attente de révision."
plone.po:msgstr "Actions sur le document"
plone.po:msgstr "Activer/désactiver le contrÎle de version pour ce document."

I'm not sure about this: as comments on the main commit on plone.po?

Thanks Denis! I am only now (after how many years!?) playing with Plone's multilingual capabilities. I've noticed a few French issues with Plone 5.2rc3...

You're welcome, Tim! :slight_smile:

Kim is good not only at Plone, but also at French! :slight_smile: Could you tell us which ones, maybe as comments on the main commit on plone.po?

Merci @dbitouze !!
J'ai fait une review de tes changements, cf mon commentaire

Je viens de resynchroniser les fichiers po plone (14 added, 1 removed) pour la version Plone 5.2 final.
@dbitouze tu veux bien regarder pour mettre Ă  jour la traduction ? Merci.

I just did some minor changes and created a pull request. Is it what you mean by "mettre Ă  jour la traduction"?

In the following:

#. Default: "By default, permissions from the container of this item are inherited. If you disable this, only the explicitly defined sharing permissions will be valid. In the overview, the symbol ${image_confirm_icon} indicates an inherited value. Similarly, the symbol ${image_link_icon} indicates a global role, which is managed by the site administrator." #: msgid "help_inherit_local_roles" msgstr "Par dĂ©faut, les rĂŽles dĂ©finis sur les dossiers parents sont hĂ©ritĂ©s. Si vous dĂ©sactivez l'hĂ©ritage des rĂŽles, seuls les rĂŽles dĂ©finis explicitement ici seront valides. Dans l'aperçu, le symbole ${image_confirm_icon} indique un rĂŽle hĂ©ritĂ©. De mĂȘme, le symbole ${image_link_icon} indique un rĂŽle global, gĂ©rĂ© par l'administrateur du site."

current translation of "permission" (in English) by "rĂŽle" in French is suboptimal IMHO. Why not use "permission" in French as well?

Same remark for:

#. Default: "Inherit permissions from higher levels"
msgid "label_inherit_local_roles"
msgstr "HĂ©riter les rĂŽles des dossiers parents"

Yes, you can change it to "permission" in French. In the old days (Plone 2.5?) the columns was Reader, Reviewer etc, this is why we have "rĂŽles" here, the translation was never updated I guess. Now it's "Can view", "Can review" etc. Please note that internally you really are giving roles, and not permissions to a user/group.

OK. Maybe the old columns headers were more appropriate, but less explicit. And what about both of them, for instance "Reader (can view)", "Reviewer (can review)", etc.? Or "can view", etc. as tooltip?

Something like "Reader (can view)" may be more confusing for the simple user actually. XD
But it may help the site administrator because they can see the same columns that in the User/Groups control panel. "Can view" with "Reader" as tooltip may be better in this case. I don't know.

OK, wait 'n see. Changes applied by PR.

Plone Foundation Code of Conduct