[wp-trac] [WordPress Trac] #60554: Add support for using only PHP translation files

[WordPress Trac]

#60554: Add support for using only PHP translation files
-------------------------+-------------------------
 Reporter:  swissspidy   |       Owner:  swissspidy
     Type:  enhancement  |      Status:  assigned
 Priority:  normal       |   Milestone:  6.6
Component:  I18N         |     Version:  trunk
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:
-------------------------+-------------------------
Description changed by swissspidy:

Old description:

> In WordPress 6.5 we're adding support for PHP translation files. They
> still require accompanying `.mo` and `.po` files. However, it doesn't
> have to be this way!
>
> A few areas that would need changing:
>
> **`wp_get_installed_translations()`**
>
> `wp_get_installed_translations()` is used for getting the list of
> installed translations for plugins/themes/core when updating language
> packs and also when uninstalling plugins/themes (to remove the
> translations again).
>
> **`Language_Pack_Upgrader`**
>
> `\Language_Pack_Upgrader::check_package()` checks whether there are `.mo`
> and `.po` in the language pack. It should also support language packs
> with only a `.l10n.php` file.

New description:

 In WordPress 6.5 we're adding support for PHP translation files. They
 still require accompanying `.mo` and `.po` files. However, it doesn't have
 to be this way!

 It should be possible for projects (plugins, themes, and core) to only use
 `.l10n.php` files.

 A few areas that would need changing:

 **wp_get_installed_translations()**

 `wp_get_installed_translations()` is used for getting the list of
 installed translations for plugins/themes/core when updating language
 packs and also when uninstalling plugins/themes (to remove the
 translations again).

 **Language_Pack_Upgrader**

 `\Language_Pack_Upgrader::check_package()` checks whether there are `.mo`
 and `.po` in the language pack. It should also support language packs with
 only a `.l10n.php` file.

 **load_textdomain() / load_default_textdomain()**

 Not sure about this one.

 Right now you can pass an `.mo` file path, even though the file doesn't
 exist, and WordPress will load the `.l10n.php` counterpart. So technically
 no change is required. However, what if you want to directly pass an
 `.l10n.php` file path instead?

--

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/60554#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform