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
views/badges etc i18n #15021
views/badges etc i18n #15021
Conversation
|
Thank you for opening this PR! We appreciate you! For all pull requests coming from third-party forks we will need to A Forem Team member will review this contribution and get back to |
|
Hey @yheuhtozr! 👋 Can you please update your branch with the latest code from the repository’s |
app/views/badges/show.html.erb
Outdated
| @@ -1,8 +1,8 @@ | |||
| <% title "#{@badge.title} Badge" %> | |||
| <% title t("views.badges.meta.name"), title: @badge.title %> | |||
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 think .meta. is not necessary here, views.badges.name should be enough. I understand that the second one has emojis on both sides but I'd consider leaving them off from the actual translation and interpolating between them since they are symmetrical that would also work for RTL languages.
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 tempting to unify them, but beware that emoji is not totally synonymous across the world. I prefer letting translators change those symbols in case they make no sense in their locale.
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.
Fair enough. If it were up to me we wouldn't be using any emoji at all in our copy.
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.
Removing emoji would be a base text change, which is a design decision. If you are sure it should be done, please let me know.
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 left a few suggestions on keeping interpolations consistent across the files, otherwise, nice work!
1ec1e61
to
0a96174
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.
I'm pre-emptively approving this but the merge conflicts need to be fixed first.
e22c871
to
0a96174
Compare
app/views/badges/show.html.erb
Outdated
| @@ -1,8 +1,8 @@ | |||
| <% title "#{@badge.title} Badge" %> | |||
| <% title t("views.badges.meta.name"), title: @badge.title %> | |||
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.
Fair enough. If it were up to me we wouldn't be using any emoji at all in our copy.
|
Hi, @yheuhtozr 👋 It looks like there is a failing spec, which can be found here, and some merge conflicts to resolve, but once those two things are taken care of and all of the checks pass, I will happily merge your work! 🚀 |
|
@juliannatetreault I debugged one error hoping it will get rid of the spec failure. Conflicts resolved but it overwrites the same files with #15083, so that one should have conflicts again if this one's got merged. |
Ah, okay and thank you, @yheuhtozr! I'm going to go ahead and merge this one. 🚀 |
* views/badges etc i18n * reformat for PR * remove ja.yml * PR argument error fix?
What type of PR is this? (check all applicable)
Description
Extracts strings for i18n from app/views/badges and related. Attached fr locales for testing purposes. Existing translations up to #15002 reflected (hopefully).
Related Tickets & Documents
Relates to #14888
QA Instructions, Screenshots, Recordings
UI accessibility concerns?
Added/updated tests?
have not been included
[Forem core team only] How will this change be communicated?
Will this PR introduce a change that impacts Forem members or creators, the
development process, or any of our internal teams? If so, please note how you
will share this change with the people who need to know about it.
Storybook (for Crayons components)
updated. I have filled out the
Changes Requested
issue template so Community Success can help update the Admin Docs
appropriately.
CHANGELOG.mdor in a forem.dev post
[optional] Are there any post deployment tasks we need to perform?
N/A
[optional] What gif best describes this PR or how it makes you feel?