Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork264
Traduction de library/datetime.po#1578
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Conversation
christopheNan left a comment
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.
Merci pour cette mise à jour.
Je pense qu'il faut corriger « heure standard » par « heure d'hiver » et remplacer « fold » par pli là où c'est possible.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
JulienPalard commentedJun 22, 2021
Attention j'ai rebasé ta branche sur la branche 3.10. |
deronnax commentedMay 18, 2022 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
je la reprends |
Co-authored-by: Christophe Nanteuil <35002064+christopheNan@users.noreply.github.com>
deronnax commentedMay 18, 2022
j'ai mergé la 3.10 mais la branche est tellement vieille que la moitié des chaines traduites de la PR sont devenues des fuzzies. Ça sera le travail d'une prochaine PR de remédier à ça. |
deronnax commentedMay 20, 2022
@christopheNan approval plz :) |
| "``None``, :attr:`tm_isdst` est mise à ``-1`` ; sinon, si :meth:`dst` renvoie " | ||
| "une valeur non-nulle, :attr:`tm_isdst` est mise à ``1`` ; sinon :attr:" | ||
| "`tm_isdst` est mise à ``0``." | ||
| "où ``yday = d.toordinal() - date(d.year, 1, 1).toordinal() + 1`` est le " |
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.
Tu laisse le flag fuzzy ?
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.
je l'ai expliqué dans mon dernier commentaire ;)
#1578 (comment)
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.
je veux juste merger le travail déjà effectué, j'ai tenté de reprendre les fuzzies : la PR est tellement vieille que plus de la moitié des strings sont passées en fuzzy, c'est beaucoup trop de travail.
Merger cette PR avec les chaines en fuzzy est une bonne chose : ces chaines, bien que fuzzy, sont déjà plus proches de l'upstream que si on en mergeait pas.
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.
ahhhhhhhhhh ok :)
| "est équivalent à ``time.ctime(time.mktime(d.timetuple()))`` sur les " | ||
| "plateformes où la fonction C native :c:func:`ctime` (que :func:`time.ctime` " | ||
| "invoque, mais pas :meth:`date.ctime`) est conforme au standard C." | ||
| "sur les plateformes où la fonction C native :c:func:`ctime` (que :func:`time." |
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.
Pareil, pourquoi laisser lefuzzy ?
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.
Pareil pour tout plein d'autres.
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.
même réponse
christopheNan left a comment
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.
Je suis d'avis de@deronnax , fusionnons.
PyDocTeur commentedMay 20, 2022
ON Y EST PRESQUE ! Un p'tit label DisclaimerJe suis un robot fait par l'équipe del'AFPy et de Traduction I'm a bot made by theTranslation and AFPy teams on their free (state: approved) |
JulienPalard commentedMay 20, 2022
Bah par qui ? |
vpoulailleau commentedMay 20, 2022
À mon avis, c'est juste un bug, GitHub est remonté dans le temps, il n'avait probablement pas lu la doc de |
alkimya commentedMay 20, 2022
Goddess ! |
deronnax commentedMay 20, 2022
nan c'est bon t'inquiète ;) |
Co-authored-by: Mathieu Dupuy <deronnax@gmail.com>Co-authored-by: Christophe Nanteuil <35002064+christopheNan@users.noreply.github.com>Co-authored-by: Mathieu Dupuy <mathieu.dupuy@critizr.com>
Co-authored-by: Mathieu Dupuy <deronnax@gmail.com>Co-authored-by: Christophe Nanteuil <35002064+christopheNan@users.noreply.github.com>Co-authored-by: Mathieu Dupuy <mathieu.dupuy@critizr.com>
Closes#1357
Révision des dernières fuzzies de library/datetime.po