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/podcasts, views/podcast_episodes i18n #15020
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 |
50de47b
to
d5c1324
Compare
d5c1324
to
d512c96
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 think this is looking good, just need to resolve the merge conflicts.
d512c96
to
896818f
Compare
|
@citizen428 Conflicts "resolved" but GitHub still shows some because of this. Please check the latest change and re-resolve conflicts if you are going to merge this PR. |
896818f
to
86158e6
Compare
config/locales/views/podcasts/en.yml
Outdated
| unsupported: Your browser does not support the audio element. | ||
| featured_shows: Featured shows | ||
| latest_episodes: Latest episodes | ||
| suggest_a_podcast: Suggest a podcast |
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.
These lines are transferred from core.podcasts. Duplication with views.podcasts.form.heading above is intentional, as this is a button text (instruction to user) and the other is a heading (page title).
bf07bfa
to
86158e6
Compare
|
@yheuhtozr |
|
@citizen428 Fixed the keys and the spec files that required now gone keys. |
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 just have one (hopefully small) suggestion - let me know what you think.
Other than that it looks like there are a couple of small conflicts to resolve and then we should be good to go 🚀
| one: '1 error while creating a podcast:' | ||
| other: "%{count} errors while creating a podcast:" | ||
| owner: I am the owner of this podcast | ||
| return: "< return to podcasts" |
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 don't think the < should be part of the actual string here, as we're not using it as "text" as such. Same with the close button "X". These are being used like icons/images (and eventually we will want to replace them with actual icons/images to avoid screen reading software announcing these links as "less than symbol return to podcasts".
Can we extricate them from the translated strings?
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 for your input. Do you mean you are going to replace the less than sign with an icon? If so, I'm happy to remove it. But if you only move it out and keep as a part of hardcoded text, I'm not sure it is a good idea. Unlike the close "X", it is not horizontally symmetrical. Some languages are written from right, so that punctuation should be flipped. "<" is not among auto-mirrored symbols and would eventually need to be changed as per locale. At the current stage we only support English and French, but I think the RTL support will be required sooner or later.
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's a really good point. I think in light of that, it's best to carry on with the implementation you have here and I'll speak to our team about how we want to adjust things in future, as eventually we don't want text representations of iconography (as they're not properly providing information to screen reader users). Until we make that future change, best to keep things together in the translated strings, as you say.
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.
(if you're able to resolve those couple of conflicts, I'll approve and get this merged 👍 )
* views/podcasts, views/podcast_episodes i18n * reformat for PR * helper labels * PR sync with main * remove ja.yml * Update en.yml * Update fr.yml * Update _meta.html.erb * Update podcast_episodes_index_spec.rb * Update podcast_create_spec.rb * Update user_visits_podcast_episode_spec.rb * Update en.yml * Update feed.rb * Update index.html.erb

What type of PR is this? (check all applicable)
Description
Extracts strings for i18n from app/views/podcasts 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?