Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Traduction de faq/design.po #1459

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

Merged
merged 2 commits into from
Nov 18, 2020
Merged

Traduction de faq/design.po #1459

merged 2 commits into from
Nov 18, 2020

Conversation

Mindiell
Copy link
Contributor

Closes #1458

Copy link
Member

@JulienPalard JulienPalard left a comment

Choose a reason for hiding this comment

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

Je te conseille d'avoir un git log côté cpython sur le fichier sur lequel tu corrige les fuzzy, c'est trop facile de rater des trucs sinon.

faq/design.po Outdated
@@ -60,11 +59,10 @@ msgid ""
msgstr ""
"Seule l'instruction ``x++`` sera exécutée si la condition est vraie, mais "
"l'indentation pourrait vous faire penser le contraire. Mêmes des "
Copy link
Member

Choose a reason for hiding this comment

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

Le diff causant la fuzzy:

-indentation leads you to believe otherwise.  Even experienced C programmers will
-sometimes stare at it a long time wondering why ``y`` is being decremented even
+indentation leads many to believe otherwise.  Even experienced C programmers will
+sometimes stare at it a long time wondering as to why ``y`` is being decremented even

Je pense que l'intention est bonne, de ne pas "attaquer" le lecteur, on pourrait répercuter ça aussi dans la traduction.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

J'ai utilisé le diff !

faq/design.po Outdated
"Pour Python, la plupart des avantages des spécifications d'interface peuvent "
"être obtenus par une discipline de test appropriée pour les composants. Il "
"Pour Python, la plupart des avantages des spécifications d'interface peut "
"être obtenue par une discipline de test appropriée pour les composants. Il "
"existe aussi un outil, PyChecker, qui peut être utilisé pour trouver des "
Copy link
Member

Choose a reason for hiding this comment

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

Le diff qui a causé cette fuzzy :

-by an appropriate test discipline for components.  There is also a tool,
-PyChecker, which can be used to find problems due to subclassing.
+by an appropriate test discipline for components.

Pas répercuté dans ta traduction :(

Copy link
Contributor Author

Choose a reason for hiding this comment

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

J'ai utilisé le diff !

@christopheNan
Copy link
Contributor

Je te conseille d'avoir un git log côté cpython sur le fichier sur lequel tu corrige les fuzzy, c'est trop facile de rater des trucs sinon.

Je plussoie et j'écrirais même plus : git log --patch

@JulienPalard JulienPalard merged commit 77353e7 into python:3.9 Nov 18, 2020
@JulienPalard
Copy link
Member

Top :)

@christopheNan
Copy link
Contributor

Merci @Mindiell 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Je travaille sur faq/design.po
3 participants