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/tags etc i18n #15039
views/tags etc i18n #15039
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 |
ea29ae5
to
da36440
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.
Left a few non-blocking suggestions for keeping quotes consistent across the en.yml and fr.yml files, otherwise this looks great so far!
ba63995
to
da36440
Compare
|
It looks like there are a handful of merge conflicts that need to be resolved. Once those are resolved and once all of the checks pass, this should be good-to-go! |
|
@juliannatetreault I have resolved the conflicts, waiting for merge. |
Awesome, thanks so much for doing that, @yheuhtozr! ✨ I'll keep an eye on the build so that once all of the required checks are green, we can merge your work! |
* views/tags etc i18n * remove ja.yml * YAML reformatting
What type of PR is this? (check all applicable)
Description
Extracts strings for i18n from app/views/tags 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?