-
Notifications
You must be signed in to change notification settings - Fork 61
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
French indicator metadata cleanup #930
Conversation
Pull Request Test Coverage Report for Build 1505909016
💛 - Coveralls |
"title": "Moyenne de la température journalière moyenne", | ||
"comment": "", | ||
"abstract": "Moyenne de la température journalière moyenne." | ||
"long_name": "Moyenne de la température journalière", |
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.
Is there a reason sometimes it is "quoditienne" et sometimes "journalière" ?
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.
From what I understand, it has something to do with the context and the repetitive nature of the event. I won't pretend to understand the intricacies, but journalière appears to be the favoured word.
More on the differences: https://french.stackexchange.com/questions/34168/quotidiennement-ou-journalier#34169
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.
Intéressante source @Zeitsperre !
Donc la température serait journalière, parce qu'on précise ici le pas de temps d'une variable (qui varie).
Et boboy, il faudrait donc changer ça partout pour harmoniser.
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.
ah bon! Je ne connaissais pas cette subtilité. Je pense qu'il faudrait mettre journalière partout alors ( pour précipitation aussi)!
}, | ||
"TN_MIN": { | ||
"long_name": "Minimum de la température journalière minimale", | ||
"long_name": "Minimum de la température journalière", |
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 would leave it as it were, since this new name loses the notion that Tmin specifically was used.
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.
@EmilieBresson je te lance dans la mêlée.
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.
@RondeauG C'était pour éviter la répétition qui n'a pas de sens puisque le minimum du minimum c'est le minimum... (même principe avec la moyenne de la moyenne). Si ça ne passe pas au conseil OK.
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.
Mais dans cette version-ci, à part pour le champs "description", il n'y a rien qui distingue TX_MIN (min du max), TG_MIN (min de la moyenne) et TN_MIN (min du min), alors que ce sont trois indicateurs différents ?
Ça peut sembler répétitif, mais je crois que c'est un endroit où on peut se le permettre. Mais en même temps, ce n'est pas critique non plus.
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.
Au contraire, non? On aurait : « Minimum de la température journalière maximale », « Minimum de la température journalière moyenne » et « Minimum de la température journalière ».
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.
@aulemahal Mais c'est justement ici ce qui est voué à être retiré, non?
"Minimum de la température journalière minimale" --> "Minimum de la température journalière"
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.
Oui, mais le "minimal" ne serait retiré que pour tn_min
puisque c'est le seul endroit où il est redondant? tx_min
et tg_min
ne sont pas touchés.
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.
Ouais... J'ai peur que ça puisse quand même porter à confusion, mais OK.
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.
En fait est-ce que :
"long_name": "Minimum de la température journalière", | |
"long_name": "Minimum de la température", |
serait encore moins confus? Tsé, le "journalier" n'a plus rien à voir à ce stade.
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.
Mauvaise idée à mon avis. Parce que ça pourrait être de la température horaire initialement et tu pourrais avoir des résultats différents.
Faut discuter de ça avec un plus gros échantillon d'utilisateurs...
"title": "Minimum de la température minimale", | ||
"comment": "", | ||
"abstract": "Minimum de la température journalière minimale." | ||
"title": "Température journalière minimale", |
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.
Same here. "Minimum de la température journalière minimale" describes TN_min better, I think.
"comment": "", | ||
"abstract": "Maximum de la température journalière maximale." | ||
"title": "Température journalière maximale", | ||
"abstract": "Température journalière maximale." |
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.
Same as above
@Ouranosinc/xclim-core I wanted to make this clear that we can take some time with this PR (not too much; I would like to get this into v0.32) and also clarify that these changes arose from another project that currently patches most of these problems, so there's no rush related to a project. The changes here don't have to be extensive; As this is a first pass at fixing many of these inconsistencies, this PR is to get the ball rolling. Please feel free to commit directly to the branch if there are any clear issues. Your comments are appreciated! |
Ça serait bien de faire une rencontre (en janvier, pas possible avant) avec vous plus Dominique Paquin pour discuter des points qui ne tiennent pas juste de la grammaire (en dessous, au-dessous) ou les fautes de frappes (dessus/dessous). Les points du genre de la Moyenne de la température moyenne. |
Co-authored-by: RondeauG <[email protected]> Co-authored-by: juliettelavoie <[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.
Quelques suggestions et quelques commentaires.
"long_name": "Cycles de gel-dégel", | ||
"description": "Nombre {freq:m} de jours avec un gel-dégel quotidien : Tmax > {thresh_tasmax} et Tmin <= {thresh_tasmin}.", |
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 trouve que le "quotidien" est superflu si on parle déjà de "jours". Mais je trouve qu'il manque justement cette information dans le long_name
...
Est-ce que "Cycles de gel-dégel diurne" serait approprié?
La plateforme de l'ONU est pratique pour ce genre de traductions : https://unterm.un.org/unterm/portal/welcome |
Co-authored-by: Pascal Bourgault <[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.
All previous comments have been resolved.
Thanks, @RondeauG! I'll open another issue to deal with the trickier comments before merging this. |
This PR is complete. It just requires #935 to go in before merging. Thanks for all the great comments! |
Pull Request Checklist:
number
) and pull request (:pull:number
) has been added.bumpversion patch
has been called on this branch.zenodo.json
What kind of change does this PR introduce?
Does this PR introduce a breaking change?
Yes. Many indicators translated to French will no longer have the same spelling/phrasing in their metadata fields.
Other information: