Translations for login

[oktapp-bacon-worker-okta]

Description

Auto copy of latest translations by okta-i18n script.

Bacon task details

• Task ID: 996b918fdc6c48d79cefa84830de1541
• Requested by: peng.yao@okta.com
• Resolves: OKTA-CHANGE-ME

Notification sent to

@lesterchoi-okta @jaredperreault-okta @glenfannin-okta @shawyu-okta @shuowu-okta @trevoring-okta @denysoblohin-okta

[oktapp-bacon-worker-okta]

Note

Please follow the guidelines on this wiki to resolve or ignore the following results.

englishLeakCheck (the keys below have English words within the sentence, which is potentially an English leak. Check if those are terms that should remain in English or if they should be translated):

• packages/@okta/i18n/src/properties/login_ja.properties:
  errors.E0000001 = Api
  oie.verify.webauthn.cant.verify.enrollment.step1 = yourcompany..com

• packages/@okta/i18n/src/properties/login_uk.properties:
  password.complexity.no_first_name = i

[denysoblohin-okta]

After running yarn verify-translations script from #3606 I still see some discrepancies between SIW and core translations for password requirements:
https://oktainc.atlassian.net/browse/OKTA-412696?focusedCommentId=5235456
(but there were much more before this PR)

[glenfannin-okta]

After running yarn verify-translations script from #3606 I still see some discrepancies between SIW and core translations for password requirements: https://oktainc.atlassian.net/browse/OKTA-412696?focusedCommentId=5235456 (but there were much more before this PR)

cc: @mauriciocastillosilva-okta

Should we hold off on merging this?

[mauriciocastillosilva-okta]

We need to merge it for sure, since this PR has some of the fixes from last month (not all yet, as you pointed out).
Please give me a day to look into it before merging. I'll approve the PR once its good to go

[Fabri31295]

Hello!
We're eagerly awaiting the resolution of this PR as it's critical for our current tasks. Any updates on its status would be highly appreciated.

Thank you!

[glenfannin-okta]

Hello! We're eagerly awaiting the resolution of this PR as it's critical for our current tasks. Any updates on its status would be highly appreciated.

Thank you!

cc: @mauriciocastillosilva-okta (I am so sorry, I don't mean to bother)

[mauriciocastillosilva-okta]

Sorry for the delay!! This is good to go.

Here is the plan: next major release the changes in this PR + the new translations coming should then be matching what we have in the backend. So yes, this is ready to merge to main branch and released in the next major release date

[glenfannin-okta]

Sorry for the delay!! This is good to go.

Here is the plan: next major release the changes in this PR + the new translations coming should then be matching what we have in the backend. So yes, this is ready to merge to main branch and released in the next major release date

Awesome! Thank you so much!