Connectors: Several strings are not translated

[manishdhorepatil-art]

I tested this issue again on the latest WordPress trunk and found that some strings in the Connectors screen are still not translated when switching to a non-English language.

issues Affected strings:

• Text and image generation with Gemini and Imagen.
• If the connector you need is not listed
• All of your API keys and credentials are stored here and shared across plugins. Configure once and use everywhere.
• Set up

Other buttons like "Install" and "Cancel" are translated correctly.

Issue cause:

• Some PHP strings are not wrapped in __()
• Some JavaScript strings are not using @wordpress/i18n

Changes done :

• Wrapped PHP strings using __( 'string', 'text-domain' )
• Updated JS strings using import { __ } from '@wordpress/i18n';

Patch: https://core.trac.wordpress.org/ticket/65015

Testing:

1. Install latest WordPress trunk
2. Change site language to a non-English language (e.g., Japanese)
3. Open Connectors screen
4. Before patch: Strings are in English
5. After patch: Strings are translated

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Unlinked Accounts

The following contributors have not linked their GitHub and WordPress.org accounts: @ManishDhorepatil.

Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[desrosj]

I worked with @manishdhorepatil-art today at WordCamp Asia Contributor Day.

The GitHub Actions workflows are failing because there are changes being made to the files included from the built Gutenberg repository. Those template files will need to be updated over there.

However, it does not seem like this is the right solution. The translations are not available because they are not being localized properly and made available for wp-i18n. This seems to be due to the fact that there's no equivalent to wp_set_script_translations() for script modules. This will likely need updates to both gutenberg and wordpress-develop to resolve.

[desrosj]

I'm going to close this out since a different approach entirely is necessary.