Skip to content
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

Merged
merged 8 commits into from
Oct 10, 2023

Conversation

jgreffe
Copy link
Contributor

@jgreffe jgreffe commented Oct 7, 2023

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

  • Translate hudson/model/Messages.properties and jenkins/model/Messages.properties into French.

Proposed upgrade guidelines

N/A

Submitter checklist

Desired reviewers

@mention

Before the changes are marked as ready-for-merge:

Maintainer checklist

Copy link
Member

@lemeurherve lemeurherve left a 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.

@lemeurherve
Copy link
Member

ICYDK you can batch suggestions when you're on the "files" tab to commit them all at once.

Copy link
Member

@lemeurherve lemeurherve left a 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é.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
AbstractItem.NewNameInUse=Le nom {0} est déjà utilisé.
AbstractItem.NewNameInUse=Le nom "{0}" est déjà utilisé.

Standard quotes

Copy link
Contributor Author

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.

Copy link
Member

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é
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
Jenkins.NotAllowedName={0} n''est pas un nom autorisé
Jenkins.NotAllowedName="{0}" n''est pas un nom autorisé

Standard quotes

Copy link
Contributor Author

@jgreffe jgreffe Oct 8, 2023

Choose a reason for hiding this comment

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

Copy link
Member

@lemeurherve lemeurherve left a 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.

@lemeurherve
Copy link
Member

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 (- [] There is automated testing (...))

@jgreffe jgreffe requested a review from lemeurherve October 8, 2023 17:54
Copy link
Member

@lemeurherve lemeurherve left a 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é.
Copy link
Member

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}
Copy link
Member

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?

@jgreffe jgreffe requested a review from lemeurherve October 9, 2023 05:49
Copy link
Member

@lemeurherve lemeurherve left a comment

Choose a reason for hiding this comment

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

LGTM, 🚢

@NotMyFault NotMyFault added the ready-for-merge The PR is ready to go, and it will be merged soon if there is no negative feedback label Oct 9, 2023
@NotMyFault NotMyFault merged commit f7bcc00 into jenkinsci:master Oct 10, 2023
16 checks passed
@welcome
Copy link

welcome bot commented Oct 10, 2023

Congratulations on getting your very first Jenkins core pull request merged 🎉🥳

This is a fantastic achievement, and we're thrilled to have you as part of our community! Thank you for your valuable input, and we look forward to seeing more of your contributions in the future!

We would like to invite you to join the community chats and forums to meet other Jenkins contributors 😊
Don't forget to check out the participation page to learn more about how to contribute to Jenkins.


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
localization ready-for-merge The PR is ready to go, and it will be merged soon if there is no negative feedback
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants