-
-
Notifications
You must be signed in to change notification settings - Fork 8.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[JENKINS-72141] French translation #8577
[JENKINS-72141] French translation #8577
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Small and mainly optional suggestions.
ICYDK you can batch suggestions when you're on the "files" tab to commit them all at once. |
Co-authored-by: Hervé Le Meur <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I missed the main file as it wasn't displayed by default due to its large size ^^
AbstractItem.BeingDeleted={0} en cours de suppression | ||
AbstractItem.FailureToStopBuilds=Echec de l''interruption et de l''arrêt de {0,choice,1#{0,number,integer} build|1<{0,number,integer} \ | ||
builds} de {1} | ||
AbstractItem.NewNameInUse=Le nom “{0}” est déjà utilisé. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AbstractItem.NewNameInUse=Le nom “{0}” est déjà utilisé. | |
AbstractItem.NewNameInUse=Le nom "{0}" est déjà utilisé. |
Standard quotes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lemeurherve
Mmmh, not sure about this one, as the default Messages.properties uses specific quotes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure why there are two sort of double quotes characters in the beginning, I think keeping only the standard ones would be better.
Question for the usual maintainers, what is the consensus (if any) about that?
Same about the use of special single quotes like L43 & L44 (‘{0}’
) instead of double quotes?
Is it intentional or some sort of crust?
Note: these conversions could also be done in another PR, absolutely not blocking for this one.
Jenkins.CheckDisplayName.NameNotUniqueWarning=Le nom affiché, "{0}", est utilisé comme nom de job et peut causer des résultats de recherche erronés. | ||
Jenkins.CheckDisplayName.DisplayNameNotUniqueWarning=Le nom affiché, "{0}", est déjà utilisé par un autre job et peut engender des erreurs et des délais. | ||
|
||
Jenkins.NotAllowedName=“{0}” n''est pas un nom autorisé |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Jenkins.NotAllowedName=“{0}” n''est pas un nom autorisé | |
Jenkins.NotAllowedName="{0}" n''est pas un nom autorisé |
Standard quotes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are a few required changes in my last suggestions.
NB: I think the tasklist rendering issue comes from the fact there isn't any space between the two squared brackets of its third item ( |
Co-authored-by: Hervé Le Meur <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great job by the way 👏
AbstractItem.BeingDeleted={0} en cours de suppression | ||
AbstractItem.FailureToStopBuilds=Echec de l''interruption et de l''arrêt de {0,choice,1#{0,number,integer} build|1<{0,number,integer} \ | ||
builds} de {1} | ||
AbstractItem.NewNameInUse=Le nom “{0}” est déjà utilisé. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure why there are two sort of double quotes characters in the beginning, I think keeping only the standard ones would be better.
Question for the usual maintainers, what is the consensus (if any) about that?
Same about the use of special single quotes like L43 & L44 (‘{0}’
) instead of double quotes?
Is it intentional or some sort of crust?
Note: these conversions could also be done in another PR, absolutely not blocking for this one.
Item.CONFIGURE.description=Modifie la configuration d''un job. | ||
Item.READ.description=Lire un job. (Vous pouvez interdire ce droit, mais autoriser Découvrir pour forcer un utilisateur anonyme à s''identifier et voir le job.) | ||
Item.RENAME.description=Renommer un job. | ||
ItemGroupMixIn.may_not_copy_as_it_contains_secrets_and_=Copie impossible de {0} car il contient des secrets et {1} possède {2}/{3} mais pas /{4} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indeed, strange... I lack the context of this message to understand why it's that way, can anyone share it?
Co-authored-by: Hervé Le Meur <[email protected]>
Co-authored-by: Hervé Le Meur <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, 🚢
Congratulations on getting your very first Jenkins core pull request merged 🎉🥳 |
See JENKINS-72141.
Reported missing keys from hudson/model/Messages.properties and jenkins/model/Messages.properties to related Messages_fr.properties.
Testing done
Proposed changelog entries
Proposed upgrade guidelines
N/A
Submitter checklist
Desired reviewers
@mention
Before the changes are marked as
ready-for-merge
:Maintainer checklist