Skip to content
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

i18n: Translate core Create and Manage #15112

Closed
wants to merge 1 commit into from
Closed

i18n: Translate core Create and Manage #15112

wants to merge 1 commit into from

Conversation

KrystalJean
Copy link
Contributor

What type of PR is this? (check all applicable)

  • Refactor
  • Feature
  • Bug Fix
  • Optimization
  • Documentation Update

Description

I followed existing patterns of internationalization from my previous merged commits. Please let me know if this should be under views instead of core, and I can change this.

Related Tickets & Documents

This PR references issue "Internationalize Hardcoded Display Text #14888".

QA Instructions, Screenshots, Recordings

Please replace this line with instructions on how to test your changes, a note
on the devices and browsers this has been tested on, as well as any relevant
images for UI changes.

UI accessibility concerns?

None
If your PR includes UI changes, please replace this line with details on how
accessibility is impacted and tested. For more info, check out the
Forem Accessibility Docs.

Added/updated tests?

  • Yes
  • No, and this is why:Existing tests should suffice.
  • I need help with writing tests

[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.

  • I've updated the Developer Docs or
    Storybook (for Crayons components)
  • This PR changes the Forem platform and our documentation needs to be
    updated. I have filled out the
    Changes Requested
    issue template so Community Success can help update the Admin Docs
    appropriately.
  • I've updated the README or added inline documentation
  • I've added an entry to
    CHANGELOG.md
  • I will share this change in a Changelog
    or in a forem.dev post
  • I will share this change internally with the appropriate teams
  • I'm not sure how best to communicate this change and need help
  • This change does not need to be communicated, and this is why not: please
    replace this line with details on why this change doesn't need to be
    shared

[optional] Are there any post deployment tasks we need to perform?

[optional] What gif best describes this PR or how it makes you feel?

alt_text

@pr-triage pr-triage bot added the PR: unreviewed bot applied label for PR's with no review label Oct 19, 2021
@github-actions
Copy link
Contributor

Thank you for opening this PR! We appreciate you!

For all pull requests coming from third-party forks we will need to
review the PR before we can process it through our CI pipelines.

A Forem Team member will review this contribution and get back to
you as soon as possible!

@citizen428
Copy link
Contributor

Hi @KrystalJean, thanks for contributing. Yes, it'd be great if you could follow the pattern of breaking out smaller views in config/locales/views/ that we recently started using, thanks!

@rhymes rhymes changed the title I18n setup EN/FR i18n: Translate core Create and Manage Oct 19, 2021
@yheuhtozr
Copy link
Contributor

The two strings are already covered by #15040.

@citizen428
Copy link
Contributor

Ok, thanks for the heads-up @yheuhtozr!

@KrystalJean Thanks a lot for your contribution, unfortunately, it seems like we'll have to close this PR since an earlier one already translated the same strings.

@citizen428 citizen428 closed this Oct 20, 2021
@yheuhtozr
Copy link
Contributor

To be accurate, the actual French translation is not included in #15040, so a later amendment is welcome.

@KrystalJean
Copy link
Contributor Author

KrystalJean commented Oct 20, 2021

Okay, no problem @citizen428 and @yheuhtozr . I am sorry about that. I had found this to work on by searching bin/untranslated_erb. Could y'all recommend any other I18n that I might could help with that will not overlap? I am still needing two more pull request for Hacktoberfest. I know my contributions have been small, but I am really enjoying working on this code, and learning so much.

@yheuhtozr
Copy link
Contributor

Oh I wasn't aware of that event being an outsider. Most strings I provided are merely extracted but not translated. So replacing them with real French might be acceptable as contributions? @citizen428

@KrystalJean
Copy link
Contributor Author

Ok, cool thanks @yheuhtozr. Do you know if I have to wait until they are merged before I work on translating, or do I just add them as suggestions in your current pull request, and mine will be merged along with yours?

@citizen428
Copy link
Contributor

@KrystalJean You can add them as suggestions in the other PR.

@KrystalJean
Copy link
Contributor Author

Ok sounds good. Thanks @citizen428 and @yheuhtozr for helping me out.

@yheuhtozr
Copy link
Contributor

yheuhtozr commented Oct 21, 2021

@KrystalJean Due to technical reasons (my GitHub repo is just a mirror), anything we add to my PR via GH won't be likely to last long. If you are planning to add something based on my contributions, I think opening independent PRs that overwrite my locale files (under config/locales/views) would be better.

@KrystalJean KrystalJean deleted the KrystalJean/I18n-feature-#14888 branch October 21, 2021 01:37
@KrystalJean
Copy link
Contributor Author

Ok @yheuhtozr thanks for letting me know. So, I will make my own pull request. Should I reference your pull request in mine?

@yheuhtozr
Copy link
Contributor

@KrystalJean Thank you, that would be great for later traceability.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PR: unreviewed bot applied label for PR's with no review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants