Repository navigation
Conversation
 [Medium impact] The wording change reaches users of the app across 49 language catalogs. The PR appears safe to merge, with a small loss of detail in the Russian file-opening warning. Findings
SummaryUpdates 49 language catalogs to use the translated “Text Editor” name.
Reviews (1) · Last reviewed commit: "Update translations" · Reviewed by Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| "%1 isn't a file Plain can open.": "Plain не может открыть %1: это не обычный файл.", | ||
| "%1 is large or has very long lines. Text Editor is made for config files and may be slow with it.": "Файл %1 большой или в нём очень длинные строки. Текстовый редактор предназначен для конфигурационных файлов и может работать с ним медленно.", | ||
| "%1 isn't a UTF-8 text file, so Text Editor didn't open it.": "Файл %1 не является текстовым файлом в UTF-8, поэтому Текстовый редактор не открыл его.", | ||
| "%1 isn't a file Text Editor can open.": "Текстовый редактор не может открыть файл %1.", |
There was a problem hiding this comment.
The new Russian translation says only “Text Editor cannot open file %1.” This warning appears when the path is a directory, device, or other non-regular file. The previous translation explained that reason; the new one leaves users guessing why opening failed. Keep the explanation, for example: “Текстовый редактор не может открыть %1: это не обычный файл.”
| "%1 isn't a file Text Editor can open.": "Текстовый редактор не может открыть файл %1.", | |
| "%1 isn't a file Text Editor can open.": "Текстовый редактор не может открыть %1: это не обычный файл.", |
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
Automated translation sync: fills pending strings in the 49 language catalogs from src/i18n/en.json. Generated by the Sync translations workflow, which validated these catalogs with the catalog tests and merges this pull request itself.