Abilities that generate content that will be exposed on the front end should use the Site Language locale

[afercia]

Description

Similar to #349

All the abilities that generate content that will end up being used on the front end should generate the content in the Site language locale.

Instead, content generated and meant to be used only in the admin interface, should be generated in the User language locale.

I quicly tested a few abilities:

• Content Summarization: always generates text in English.
• Excerpt Generation: seems inconsistent, sometimes it's in English, sometimes it's in the language used in the post content.
• Title Generation: seems to respect the language in the post content.
• Review Notes: If the notes are going to be used only in the admin UI, I'd think the generated content should be in the user locale.

A few screenshots to illustrate cases where the Site Language locale is in Italian but the Summary and Excerpt were generated in English:

Summary:

Excerpt:

Step-by-step reproduction instructions

Test the text generation of the various abilities with:

• Site Language set to a language other than English.
• User language set to another language.
• Posts written in the same language as the Site Language.
• Posts written in another language.
• Posts with content with mixed languages e.g. longs sections of quoted text or Quote blocks in another language.

Screenshots, screen recording, code snippet

No response

Environment info

No response

Please confirm that you have searched existing issues in the repo.

• Yes

Please confirm that you have tested with all plugins deactivated except the AI plugin.

• Yes

Please confirm which theme type you used for testing.

• Block
• Classic
• Hybrid (e.g. classic with theme.json)
• Not sure

[dkotter]

Thanks for the report @afercia. I've opened #357 to try addressing this.

Content Summarization: always generates text in English.
Excerpt Generation: seems inconsistent, sometimes it's in English, sometimes it's in the language used in the post content.
Title Generation: seems to respect the language in the post content.

In my testing, all of these would return in the correct language, matching the language of the content they were given (YMMV depending on the model you use). That said, I do think it's still a good idea to try and guide the LLM to match the language of the content. I decided not to pass in the site locale as there's things like multi-lingual sites that this may not work for and seems safer to have the LLM analyze the content given and match it.

Review Notes: If the notes are going to be used only in the admin UI, I'd think the generated content should be in the user locale

I've left this alone for now as this is admin-facing only and there's a world where multiple users may be working on the same post and each have their own language they want, so passing in a specific user locale may not be ideal. That's probably edge-case but can come back to this later if we get more reports of wanting the language here to be different

[afercia]

@dkotter thanks for your feedback.

YMMV depending on the model you use

Yes it may be that. I forgot to mention I used the Gemini free tier for testing.

passing in a specific user locale may not be ideal.

I'd agree.