-
Notifications
You must be signed in to change notification settings - Fork 5
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
padpo doesn't like *n*-uplet
on msgstr start
#58
Comments
https://github.com/AFPy/padpo/blob/master/padpo/checkers/glossary.py needs to be updated, "n-uplet" was added to https://github.com/python/python-docs-fr/blob/3.9/CONTRIBUTING.rst The entire file needs to be updated according to the sources in comment in the Python code. |
Could you make a scrapper that auto does it ? |
I thought I could do it, but it was not feasible, because the glossary is not exhaustive (plural form…). This is a manual work, but in comment in the code, there is the exact commit from which comes the data, so that we can |
ah nice ! |
Seen while fixing AFPy/padpo#58
Automerge of PR #1533 by @vpoulailleau Seen while fixing AFPy/padpo#58
@Seluj78 C'est quoi l'astuce pour afficher les résultats padpo directement dans la pull request ? |
@vpoulailleau aucune idée, ca l'a fait tout seul, je suppose que ton formatting l'a fait? ou alors c'est mes extensions (genre refined github) ? |
@Seluj78 Suite à une remarque de @JulienPalard, je respecte le formattage de GCC. Je vois aussi les remarques de padpo dans la pull request. J'imagine qu'il a fallu configurer quelque chose dans le dépôt. Cela doit avoir un rapport avec https://github.com/actions/toolkit/blob/master/docs/problem-matchers.md, non ? |
Je n'ai aucune mémoire de configuration spécifique dans le répo, donc ça doit être par défaut et c'est déjà très stylé! |
As you can see,
*n*-uplet
is a valid word but padpo throws an error when it sees that word at the beginning of a translationThe text was updated successfully, but these errors were encountered: