Viltrumlik opened a new pull request, #76581:
URL: https://github.com/apache/airflow/pull/76581
`admin.pools.pool_many` and `pool_other` were both `"Пул"`, the nominative
singular. Russian takes the genitive plural from five upwards, so both should
be `"Пулов"`.
```diff
"pool_few": "Пула",
- "pool_many": "Пул",
+ "pool_many": "Пулов",
"pool_one": "Пул",
- "pool_other": "Пул",
+ "pool_other": "Пулов",
```
The same block already uses that form — `"searchPlaceholder": "Поиск пулов"`
—
and the other countable nouns in `admin.json` follow the same pattern:
| key | `_one` | `_few` | `_many` |
|---|---|---|---|
| `connections.connection` | Соединение | Соединения | Соединений |
| `variables.variable` | Переменная | Переменные | Переменных |
| `plugins.importError` | Ошибка импорта плагина | Ошибки импорта плагинов |
Ошибок импорта плагинов |
| `pools.pool` (before) | Пул | Пула | **Пул** |
The forms are user-visible: `Pools.tsx` passes
`modelName="admin:pools.pool"`,
so the plural is resolved from the count.
`pool_other` follows `pool_many` here because every plural set in
`admin.json`
does; the `_other` convention across the locale is discussed in #76579.
Scope is deliberately this one key. Four other sets in the locale have
`_few` identical to `_many`, but in each of those the string carries no
numeral (for example `"Вы собираетесь удалить следующие соединения:"`), where
a single plural form is correct, so they are left alone.
related: #61984
cc @jscheffl (code owner), @puzzle-rpa-team, @renat-sagut
---
##### Was generative AI tooling used to co-author this PR?
- [X] Yes (please specify the tool below)
Generated-by: Claude Code following [the
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
🤖 Generated with [Claude Code](https://claude.com/claude-code)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
