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 pt_BR translation of invalid email message #5953

Merged
merged 1 commit into from
Apr 12, 2024
Merged

Fix pt_BR translation of invalid email message #5953

merged 1 commit into from
Apr 12, 2024

Conversation

wesleybl
Copy link
Member

@wesleybl wesleybl commented Apr 9, 2024

No description provided.

@wesleybl wesleybl requested a review from sneridagh April 9, 2024 15:07
Copy link

netlify bot commented Apr 9, 2024

Deploy Preview for volto canceled.

Name Link
🔨 Latest commit 131b63e
🔍 Latest deploy log https://app.netlify.com/sites/volto/deploys/661559b4f1125b0008d2d61b

Copy link

netlify bot commented Apr 9, 2024

Deploy Preview for plone-components canceled.

Name Link
🔨 Latest commit 131b63e
🔍 Latest deploy log https://app.netlify.com/sites/plone-components/deploys/661559b4cc51240008f0c1ba

@wesleybl wesleybl requested review from ericof and davisagli April 9, 2024 15:07
@wesleybl
Copy link
Member Author

wesleybl commented Apr 9, 2024

I'm wondering if the "email" key shouldn't be changed to something with "invalid email".

@stevepiercy
Copy link
Collaborator

I also would use "Email" instead of the hyphenated and archaic "e-mail". This comment from SO from 2010 is interesting: https://english.stackexchange.com/a/1928

@wesleybl
Copy link
Member Author

@stevepiercy In Brazil, the use of the hyphen is still more common. So I think it's better to leave it like that. In English it is already without a hyphen.

@davisagli
Copy link
Member

I'm wondering if the "email" key shouldn't be changed to something with "invalid email".

That would make sense to me -- but then we should update all the existing translations.

I'll merge this as is, and that can be done in a separate PR.

@davisagli davisagli merged commit a863b45 into main Apr 12, 2024
73 checks passed
@davisagli davisagli deleted the pt_br branch April 12, 2024 19:14
sneridagh added a commit that referenced this pull request Apr 16, 2024
* main: (28 commits)
  Bump vite from 5.1.5 to 5.1.7 (#5946)
  Fix pt_BR translation of invalid email message (#5953)
  Fix markup shortcuts for bold, italic and strikethough fix (#5606)
  Release 18.0.0-alpha.27
  Release @plone/types 1.0.0-alpha.10
  Improve color widget picker and types (#5948)
  Enhanced navigation reducer in Volto (#5817)
  Release 18.0.0-alpha.26
  Rename news item
  Release @plone/slate 18.0.0-alpha.11
  Release @plone/registry 1.5.5
  Release @plone/types 1.0.0-alpha.9
  docs: Cleanup obsolete EEA projects and update info about EEA main website (#5943)
  Bump vite from 5.1.4 to 5.1.5 (#5942)
  Add a new label `needs: triage` to new bug reports (#5940)
  Fix redirect of `https://sustainability.eionet.europa.eu` to `https:/… (#5941)
  Does not show borders in addon block inputs (#5898)
  Fix edge case in search options mangling when the options are false-ish (#5869)
  Add additional parameters to ContentsUploadModal to be reusable in different scenarios (#5881)
  fix(slate): fix insert/remove element edgecase bug in slate (#5926)
  ...
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.

3 participants