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
Update white balance observer tooltip #6970
Comments
@Lawrence37 The corollary problem, also complex, is the evolution of this documentation through that of the software functionalities. This “Observer” case is just one example among others. No changes for the first part: And for the second: Jacques |
If you are OK, I will change the tooltip tomorrow, directly in dev (without PR, if you agree). Jacques |
Hi and thanks for taking care of this! |
For me it's OK In the rare occurrence where a drift of the colors is noticed with “Observer 2°” – generally due to the conversion matrix –, “Observer 10°” must be selected instead. But I am not at all english... Jacques |
I’m French so I’ll let @Lawrence37 be the judge. xD |
@alice-mm Sympathique qu'il y ait des français(e) qui participent. Jacques |
Well, I'm embarrassed. I know the distinction between hyphens and dashes, but I had to look up the difference between an en dash (short dash) and an em dash (long dash). The em dash (—) is correct here. To make it more concise, I suggest
I have one question for Jacques. The original tool-tip reads "probably due to the conversion matrix" while Alice's is "generally due to the conversion matrix". "probably" and "generally" have different meanings. "probably" implies we don't know the cause, but we suspect it has something to do with the conversion matrix. "generally" means most color drifts that have been observed are caused by the conversion matrix. Essentially, the difference between the words is whether we know the conversion matrix causes color drifts. Which one is right? |
For me it's "probably", because we don't know what "Adobe" does ( or else we would have to send the CIA or the FSB...) I will take your last text, with : And to be sure, I will create a PR. Jacques |
Sounds good. |
I just create a Pull-Request with this (small, but important) change Jacques |
Haha sorry for launching you on that topic. Hum yeah they’re sometimes used interchangeably for this, but ultimately the em may be better yeah. Note, however, that it has no spaces on the side, generally, unlike the en. (While in French we use spaces regardless of en or em. 🙃) Wikipedia gives examples such as:
Sorry about this! I indeed wrongly assumed that we kinda knew what was happening. |
in French D'où ma remarque sur la CIA ou le FSB... Bref, pas simple. Jacques |
Je crois que c’est bien au-dessus de mon niveau. xD By the way, do such changes automatically get reflected on files such as |
In french En fait, rien n'est simple, y compris pour la documentation. Depuis que je coopère avec Wayne @Wayne_Sutton50 ou @Wayne_Sutton qui est anglophone de naissance et habite en France depuis longtemps, pour moi, tout va bien...Notre coopération se passe au mieux... Seul problème en termes de convivialité, nous sommes à 1000km de distance. Non seulement il traduit, mais il essaye, critique, souhaite des modifications - souvent de GUI - le plus souvent sur la compréhension de ce que cela fait... Ce qui amène que la version 'anglaise' est mieux (c'est presque un comble) que la française, que ce soit pour la documentation, mais aussi les Labels et Tooltips. C'est un travail considérable, on y passe beaucoup de temps. L'inconvénient c'est que Rawpedia (le support) est antique... Il y a un projet d'amélioration (je ne comprends pas tout ce qui est prévu). En tous cas, je retiens ta proposition, si tu souhaites coopérer comme Wayne (traduire, tester, critiquer...), cela présente tout un tas d'avantages (à part le temps à y passer), tout le monde est gagnant. Mais cette proposition tient aussi pour les autres participants, traduire de anglais à Français ou l'inverse... Et toutes les langues...Japonais, allemand, néerlandais.. Merci. Bon week-end. Jacques |
The tool-tip says the default observer is 10 degrees, but it is actually 2. The rest of the tool-tip should be reviewed for accuracy (is 10 degrees still the better option in most cases?). Here's the current tooltip:
The text was updated successfully, but these errors were encountered: