-
Notifications
You must be signed in to change notification settings - Fork 33
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
Various wording fixes #1080
Various wording fixes #1080
Conversation
Affected libs:
|
📷 Screenshots are here! |
ec6bc6b
to
709bb4c
Compare
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.
Thank you! I had a question about the rich-text eye icon, but I haven't tested the change.
I think all these changes make sense, although very soon we're going to start showing more than just datasets in the Datahub. I guess we'll need to have separate translation keys for these then..
@@ -12,10 +12,10 @@ | |||
<span | |||
class="material-symbols-outlined gn-ui-icon-small" | |||
[ngClass]="{ 'text-primary': !preview }" | |||
>{{ preview ? 'visibility' : 'visibility_off' }}</span | |||
>{{ preview ? 'visibility_off' : 'visibility' }}</span |
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 that intentional? I haven't noticed that this was inverted
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.
It is intentional. We kind of got used to it this way, but I felt it was wrong the first time I coded it. And now with François fresh view on it, it felt odd too.
> | ||
| ||
{{ preview ? 'WYSIWYG' : 'Markdown' }} | ||
{{ preview ? 'Edit' : 'Preview' }} |
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.
that looks inverted as well? I thought preview
meant the text was rendered properly without being editable
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, it was intentional. The button shows what you can do (action), not the current state.
"editor.record.form.section.classification.description": "The classification has an impact on the access to the data.", | ||
"editor.record.form.section.classification.label": "Classification", | ||
"editor.record.form.section.classification.description": "Appropriate keywords help users find the dataset.", | ||
"editor.record.form.section.classification.label": "Keywords", |
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.
This might be a little too narrow; classification can also be general themes for instance (even though we don't show it yet)
"editor.record.undo.confirmation.cancelText": "Keep the changes", | ||
"editor.record.undo.confirmation.confirmText": "Discard the changes", | ||
"editor.record.undo.confirmation.message": "Are you sure you want to cancel the pending changes on this record?", | ||
"editor.record.undo.confirmation.message": "Are you sure you want to cancel the pending changes on this dataset ?", |
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.
"editor.record.undo.confirmation.message": "Are you sure you want to cancel the pending changes on this dataset ?", | |
"editor.record.undo.confirmation.message": "Are you sure you want to cancel the pending changes on this dataset?", |
c0e4c9c
to
e4a2f4e
Compare
Description
This PR is meant to improve default translation for the editor.