preview needs gettext

[timse201]

​https://translate.wordpress.org/projects/wp/dev/admin/de/formal/?filters%5Bstatus%5D=either&filters%5Boriginal_id%5D=705&filters%5Btranslation_id%5D=121310825

its used as a area label and as a heading. noun / verb

[audrasjb]

To be clear, what is needed here is a context for translators, using the _x() function.
See ​https://developer.wordpress.org/plugins/internationalization/how-to-internationalize-your-plugin/#disambiguation-by-context

Adds context for translators to disambiguate 'Preview' as a verb (action button) rather than a noun.

Fixes #64986

Trac ticket:

## Use of AI Tools

## Summary
Fixes the ambiguous translation of the string 'Preview' used in multiple contexts. In some languages (e.g., German), different forms may be needed depending on whether 'Preview' is used as a button label, an action link, or an editor control. Without translator context, GlotPress cannot distinguish between these uses, leading to potential mistranslations.

Replaces all __( 'Preview' ) occurrences with _x( 'Preview', 'context' ) to provide explicit context for translators, consistent with the existing pattern used for other disambiguated strings in the codebase.

## Changes
src/wp-includes/class-wp-editor.php — Use _x() with 'editor button' context for the TinyMCE Preview button.
src/wp-admin/includes/class-wp-theme-install-list-table.php — Use _x() with 'theme preview action' context for the theme preview link in the install themes list table.
src/wp-admin/includes/class-wp-posts-list-table.php — Use _x() with 'post preview action' context for the preview action link in the posts list table.
src/wp-admin/includes/meta-boxes.php — Use _x() with 'button' context for the preview button text in the post submit meta box.

## Testing

• Verify that the posts list table (/wp-admin/edit.php) still shows "Preview" action links correctly.
• Verify that the themes install screen (/wp-admin/theme-install.php) still shows "Preview" links correctly.
• Verify that the post edit screen preview button renders correctly.
• Verify that the TinyMCE editor preview button is still accessible and functional.
• Optionally: confirm the new context appears in GlotPress under the wp/dev project strings for 'Preview'.

---

Trac ticket: https://core.trac.wordpress.org/ticket/64986

---

## Use of AI Tools
AI assistance: Yes
Tool(s): GitHub Copilot
Model(s): Claude Haiku 4.5
Used for: Identifying all affected locations and implementing the _x() replacements; changes were reviewed before submission.

Trac ticket: https://core.trac.wordpress.org/ticket/64986

## Description
Adds context for translators to disambiguate 'Preview' as a verb (action button) rather than a noun.

This helps translators in languages like German where the translation differs based on whether "Preview" is used as a noun or verb.

## Changes

• Changed __( 'Preview' ) to _x( 'Preview', 'verb, action button to preview the post' ) in src/wp-admin/includes/meta-boxes.php

## Testing

1. The string will now appear with context in translate.wordpress.org
2. No functional changes to the button behavior

[motylanogha]

Refreshed patch for current trunk. Adds translator context to all 4 instances of ( 'Preview' ) using _x() with descriptive context strings.

[audrasjb]

As per today's bug scrub.
Thanks for the patch.
However I think the initial request was only to distinguish verbs from nouns. We could avoid having 4 different strings by just having _x( 'Preview', 'noun' ) and _x( 'Preview', 'verb' ).

At the very least, I think we could have the same string (button context, or even better verb) for both src/wp-admin/includes/meta-boxes.php and wp-includes/class-wp-editor.php.

Preview is a single English token that lands in translations as a verb (button labels), a noun (preview panes, table headers), or an iframe title. Without translator context, all 14 in-tree occurrences collapsed onto one entry in default.po, forcing translators to choose a single rendering that fit poorly somewhere.

This PR gives each occurrence a context that names both the part of speech and the surface it appears on:

• Post row action and post-lock dialog button (verb, ...)
• Submit meta box preview button (verb, action button to preview the post)
• Theme install list-table action and theme-install template buttons (verb, ...)
• Theme preview iframe title (noun, ...)
• Customizer toggle and takeover dialog (verb/noun, ...)
• Header image and background image preview rows (noun, ...)
• Classic-editor (TinyMCE) toolbar button (verb, ...)

Extends the scope of GH-11407 and GH-11408, which only covered four of these spots and used less specific context strings.

[rafaeldella]

I tested PR #11700 in my local environment (WordPress 7.0-alpha/trunk via wp-env).

I've verified the changes in the source code (e.g., in the post list table) and confirmed that the _x() function is now correctly implementing context for the "Preview" strings. I also navigated through the dashboard (Posts, Editor, and Themes) and everything is working perfectly. No regressions were found.

My environment:

• OS: Windows 10 (WSL2)
• Browser: Chrome
• Setup: Docker / wp-en

Thanks for the PR! There might be some confusion here, we don't really need a separate context for each of these strings, that would be redundant and increase the workload for translators.

As noted on the ticket already, just _x( 'Preview', 'noun' ) or _x( 'Preview', 'verb' ) would be enough here.

[jorbin]

Add suggestions to the pr to simplify the context.

Adds translator context to all in-tree occurrences of the 'Preview' string using a simplified _x( 'Preview', 'noun' ) or _x( 'Preview', 'verb' ), so translators can correctly disambiguate it across languages (e.g. German) where the noun and verb forms differ.

• Buttons and action links use 'verb'.
• Preview pane labels, table row headers, and the iframe title use 'noun'.

Closing this as a duplicate of #11700

[audrasjb]

In 62353:

I18N: Add translator context to disambiguate translation strings for "Preview".

This changeset disambiguates translation strings for "Preview" by adding a verb|noun context to its occurrences.

Props timse201, audrasjb, anupkankale, mohamedahamed, rafaeldella, motylanogha, wildworks, jorbin, khokansardar, sergeybiryukov.
Fixes #64986.

[audrasjb]

Reopening for second committer sign-off and backport to branch 7.0.

[wildworks]

This is the second committer sign-off for [62353].

[audrasjb]

In 62355:

I18N: Add translator context to disambiguate translation strings for "Preview".

This changeset disambiguates translation strings for "Preview" by adding a verb|noun context to its occurrences.

Reviewed by audrasjb, wildworks.
Merges [62353] to the 7.0 branch.
Props timse201, audrasjb, anupkankale, mohamedahamed, rafaeldella, motylanogha, wildworks, jorbin, khokansardar, sergeybiryukov.
Fixes #64986.

[timse201]

Thanks for your work.
But the initial ticket was about preview "%s". We need a fix for this, too.

[audrasjb]

We're a bit too close from RC4.
Let's delay this change to 7.0.1, unless a patch is provided in the next few hours we have before RC4. In that case, feel free to replace it to milestone 7.0 and we should be able to commit it.

[audrasjb]

Removing trunk version as this is not going to be shipped with WP 7.0 but in the next releases.

### Description
This PR addresses Trac ticket #64986 by updating the Youtube_by_mid() function in wp-includes/meta.php to return null instead of false when validation fails or a metadata row is not found.

Currently, the function's DocBlock documentation specifies @return stdClass|null, but the actual implementation incorrectly returns false in early return statements and when the database query comes up empty. This change ensures that the function's behavior perfectly aligns with its documented return type and matches expected core standard behavior.

### Trac Ticket
Trac ticket: https://core.trac.wordpress.org/ticket/64986

### Use of AI Tools
AI assistance: No

Hi @arifrahmanbb, this PR seems completely unrelated to Track ticket 64986. Could you clarify which ticket you are actually working on?

[wildworks]

But the initial ticket was about preview "%s". We need a fix for this, too.

The translator comments for "Preview %s" are already in place. What is the reason for needing context?

​https://github.com/t-hamano/wordpress-develop/blob/8a9d768c98ee80c010949a6f529b33807185cf9c/src/wp-admin/includes/class-wp-theme-install-list-table.php#L285-L286

​https://github.com/WordPress/wordpress-develop/blob/8a9d768c98ee80c010949a6f529b33807185cf9c/src/wp-admin/includes/class-wp-posts-list-table.php#L1549-L1550

[timse201]

The first one is a heading (noun) and the second one an area label (verb). Comments do not separate the strings.

in addition to and fixes: https://core.trac.wordpress.org/ticket/64986

You're right. It seems I was confused with a different string. Both strings are now fixed in de_de.
Thank you.

[wildworks]

I don't think there's anything else to address in this ticket, so I'm going to close it.

[sabernhardt]

([62355] was committed for inclusion in 7.0.)