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

fix(localization): Update Japanese verification email send button label. #484

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

dlr0w
Copy link

@dlr0w dlr0w commented Mar 16, 2025

Description

This PR fixes the translation of "sendVerificationEmailLabel" in firebase_ui_ja.arb.
Currently, it is in English as "Send verification email", but it has been changed to "確認メールを送信" (Send verification email) in Japanese.
This will allow users to consistently see the Japanese display.

Related Issues

This change is only a localization fix and is not related to any specific issue.
If translation issues arise in the future, please refer to this PR.

Checklist

This PR fixes the translation of "sendVerificationEmailLabel" in firebase_ui_ja.arb.
Currently, it is in English as "Send verification email", but it has been changed to "確認メールを送信" (Send verification email) in Japanese.
This will allow users to consistently see the Japanese display.

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
  • All existing and new tests are passing.
  • I updated/added relevant documentation (doc comments with ///).
  • The analyzer (melos run analyze) does not report any problems on my PR.
  • All unit tests pass (melos run test:unit:all doesn't fail).
  • I read and followed the Flutter Style Guide.
  • I signed the CLA.
  • I am willing to follow-up on review comments in a timely manner.

Breaking Change

This change is only a localization fix and is not related to any specific issue.
If translation issues arise in the future, please refer to this PR.

  • Yes, this is a breaking change.
  • No, this is not a breaking change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant