Add text domain to copy in domain-picker and plans-grid packages

[p-jackson]

Changes proposed in this Pull Request

• Define __i18n_text_domain__
• Hard code __i18n_text_domain__ to 'default' in calypso
• Hard code __i18n_text_domain__ to 'full-site-editing' in ETK
• Hard code __i18n_text_domain__ to some value in the unit tests so they don't fail
• Switch @automattic/domain-picker and @automattic/plans-grid over to use @wordpress/18n
• Add the text-domain constant to all calls to __() in the domain-picker and plans-grid packages

Testing instructions

• Check out branch and test using yarn dev --sync
• Switch user to Spanish or something non-English
• Go to /new/domains and see that the "View more results" button and other copy is still translated correctly
• Open the page editor on an unlaunched gutenboarding site
• Click "Complete setup" in the top right
• Click the second step in the launch flow, which is for choosing a domain
  • The text in here is being translated, but will probably still appear as English because translations aren't done for the ETK (the strings are translated for the default text-domain, but not the full-site-editing text-domain)
  • You can confirm the translations are working by switching one of the strings in the domain picker with something that we know is already translated in the full-site-editing text domain
  • e.g. Switch "Search for a domain" with "Complete setup", rebuild, and the domain search placeholder text should be translated.

[matticbot]

Test live: https://calypso.live/?branch=add/text-domain-to-domain-picker-copy

[matticbot]

Caution: This PR affects files in the Editing Toolkit Plugin on WordPress.com
Please ensure your changes work on WordPress.com before merging.

D51378-code has been created so you can easily test it on your sandbox. See this FieldGuide page about developing the Editing Toolkit Plugin for more info: PCYsg-ly5-p2

[matticbot]

Here is how your PR affects size of JS and CSS bundles shipped to the user's browser:

App Entrypoints (~9 bytes added 📈 [gzipped])

name                 parsed_size           gzip_size
entry-gutenboarding       +695 B  (+0.0%)       +9 B  (+0.0%)

Common code that is always downloaded and parsed every time the app is loaded, no matter which route is used.

Legend

What is parsed and gzip size?

Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory.
Gzip Size: Compressed size of the JS and CSS files. This much data needs to be downloaded over network.

Generated by performance advisor bot at iscalypsofastyet.com.

[wp-desktop]

WordPress Desktop CI Failure for job "wp-desktop-mac".

@p-jackson please inspect this job's build steps for breaking changes at this link. For temporal failures, you may try to "Rerun Workflow from Failed".

Please also ensure this branch is rebased off latest Calypso.

wp-desktop ci passing, closing review

[p-jackson]

This approach is probably ready for a review, but added [DO NOT MERGE] because there's an issue with very early domain suggestion searches using the wrong locale. Need to see whether this is introduced by the PR or already an issue in production.

[p-jackson]

there's an issue with very early domain suggestion searches using the wrong locale. Need to see whether this is introduced by the PR or already an issue in production.

This issue already exists in production. Unrelated to this PR but, if user searches for a domain before the translations are loaded then the request to the domains/suggestions will include a locale=en param, even if the locale has been set to something else.

This is fixed by #46473

[lsl]

Does string extraction handle these constant text domains correcty?

---

This issue already exists in production. Unrelated to this PR but, if user searches for a domain before the translations are loaded then the request to the domains/suggestions will include a locale=en param, even if the locale has been set to something else.

This is fixed by #46473

Is this not the hardcoding of en locale here: #44840 (comment)

[deBhal]

LGTM!

It looks like it's fixed our problem - I spun up an ephemeral site, ran yarn run build for calypso and the etk, and then copied the new editor-site-launch.js bundle across to run wp i18n make-pot . there. I also made a pot against master for comparison with the original pot from the provisioning, and the diffs are just what we want to see (pasted below).

I also checked that we haven't messed with the calypso string extraction by running yarn run translate on this and the merge base (git mergebase HEAD master) and diffing them, and saw only some line-number changes in domain-picker and plans-grid - perfect 👍

I'd like to keep looking for a cleaner solution in general, but this here is a working patch - nice work!

[email protected]:~/wp-content/plugins/full-site-editing$ diff full-site-editing.pot.orig full-site-editing.pot.master
< "POT-Creation-Date: 2020-10-21T01:42:14+00:00\n"
---
> "POT-Creation-Date: 2020-10-23T00:40:38+00:00\n"
[email protected]:~/wp-content/plugins/full-site-editing$ diff full-site-editing.pot.orig full-site-editing.pot.patched 
12c12
< "POT-Creation-Date: 2020-10-21T01:42:14+00:00\n"
---
> "POT-Creation-Date: 2020-10-23T00:25:10+00:00\n"
1691a1692,1755
> msgstr ""
> 
> #: editor-site-launch/dist/editor-site-launch.js:33
> msgid "All domains ending with <tld /> require an SSL certificate to host a website. When you host this domain at WordPress.com an SSL certificate is included. <learn_more_link>Learn more</learn_more_link>"
> msgstr ""
> 
> #: editor-site-launch/dist/editor-site-launch.js:33
> msgid "Recommended"
> msgstr ""
> 
> #: editor-site-launch/dist/editor-site-launch.js:33
> msgid "You can change your free subdomain later under Domain Settings."
> msgstr ""
> 
> #: editor-site-launch/dist/editor-site-launch.js:33
> msgid "Unavailable"
> msgstr ""
> 
> #: editor-site-launch/dist/editor-site-launch.js:33
> msgid "Free"
> msgstr ""
> 
> #: editor-site-launch/dist/editor-site-launch.js:33
> msgid "Included in plans"
> msgstr ""
> 
> #: editor-site-launch/dist/editor-site-launch.js:33
> msgid "%s/year"
> msgstr ""
> 
> #: editor-site-launch/dist/editor-site-launch.js:33
> msgid "All Categories"
> msgstr ""
> 
> #: editor-site-launch/dist/editor-site-launch.js:33
> msgid "View all"
> msgstr ""
> 
> #: editor-site-launch/dist/editor-site-launch.js:33
> msgid "example.com"
> msgstr ""
> 
> #: editor-site-launch/dist/editor-site-launch.js:33
> msgid "Search for a domain"
> msgstr ""
> 
> #: editor-site-launch/dist/editor-site-launch.js:33
> msgid "An error has occurred, please check your connection and retry."
> msgstr ""
> 
> #: editor-site-launch/dist/editor-site-launch.js:33
> msgid "Keep sub-domain"
> msgstr ""
> 
> #: editor-site-launch/dist/editor-site-launch.js:33
> msgid "Professional domains"
> msgstr ""
> 
> #: editor-site-launch/dist/editor-site-launch.js:33
> msgid "View more results"
> msgstr ""
> 
> #: editor-site-launch/dist/editor-site-launch.js:33
> msgid "A domain name is the site address people type in their browser to visit your site."

[p-jackson]

Is this not the hardcoding of en locale here: #44840 (comment)

@lsl yes it is. The locale still defaults to 'en'. We attempt to pass in the correct locale using the useI18n() hook, but until the locale data has been loaded, the hook doesn't return the correct locale.

However now that #46473 is merged, the domain picker component doesn't render until after the locale data is available, which means the first time we call useI18n() it returns the correct thing.

So not a very explicit fix to the problem, but something for another PR.

[p-jackson]

I'd like to keep looking for a cleaner solution in general, but this here is a working patch

I agree, our work here is not done. I was hesitant to merge in case we want to have more discussion about other approaches. But I also don't want this PR to languish over the weekend while I'm afk, slowing our momentum. So I'm going to merge. We absolutely still may want to make changes here.