-
```[tasklist]
### Plugin itself
- [x] No german translation
- [ ] Needs JS on the frontend to render an address
- [x] Uses fixed non-translatable rewrite slugs for post_type and taxonomy
- [x] Ma…
-
## Issue Overview
Historically, translations in JavaScript have not existed in WordPress, with the localized strings typically being passed to the scripts from PHP, via `wp_localize_script()`. With…
-
## Description
The sidebar inspector seems to implement TextControls that get progressively wider
This issue seems visually worst in Chrome, is slightly better in Safari and hardly noticeable in F…
-
#### Rule type:
Error
#### Rule:
From what I can see, there are actually 5 distinct i18n related rules which may need sniffs - this issue covers the **third item** on the list.
1. All theme text str…
jrfnl updated
5 years ago
-
### What
Currently, when a user selects "Log in with WordPress.com" we send them to the English WordPress.com login screen no matter what device language they are using. (For example, on Android an…
-
### Issue
### Incorrect localeSlug on atomic sites
Currently in the ETK, when we want to get the `localeSlug` (for example to localize a url) we get it from the wordpress [`determine_locale` fu…
-
Hello
Nice plugin thank you.
I see you are shipping the plugin with translations.
The i18n process could be easier and collaborative with translate.wordpress.org like explained on:
https://make.wor…
-
Using the context i18n feature "_x" is for fixing ambiguous strings:
https://developer.wordpress.org/plugins/internationalization/how-to-internationalize-your-plugin/#disambiguation-by-context
If…
-
Feature Request from https://github.com/palasthotel/grid-wordpress/issues/2 - currently the wordpress version of grid is only partially localizable (and the new core editor classes don't support i18n …
-
> Mismatched text domain. Expected 'kala' but got 'meom-blocks'.
| | (WordPress.WP.I18n.TextDomainMismatch)
Above is outputted when using command `./vendor/bin/phpcs htdocs/wp-conte…