[vim/vim] Translation into Russian (#6734)

49 views
Skip to first unread message

Restorer

unread,
Aug 18, 2020, 6:16:56 PM8/18/20
to vim/vim, Subscribed

Updated and corrected translation of program messages

Дополненный и исправленный перевод сообщений программы


You can view, comment on, or merge this pull request online at:

  https://github.com/vim/vim/pull/6734

Commit Summary

  • Add files via upload
  • Merge pull request #1 from RestorerZ/RestorerZ-patch-1

File Changes

Patch Links:


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Emir Sarı

unread,
Aug 19, 2020, 8:15:36 AM8/19/20
to vim/vim, Subscribed

Just FYI, there might have been some changes after your PO generation date.

Bram Moolenaar

unread,
Aug 19, 2020, 1:27:01 PM8/19/20
to vim/vim, Subscribed

The diff shows the two .po files as new files, not as patches. Not sure what happened.
Perhaps drop the pull request for ru.cp1251.po and only change ru.po, the other will be generated using iconv.

K.Takata

unread,
Aug 19, 2020, 5:49:42 PM8/19/20
to vim/vim, Subscribed

It seems that the files are added into the top directory. Should be added in src/po/.

Restorer

unread,
Aug 21, 2020, 4:50:08 AM8/21/20
to vim/vim, Push

@RestorerZ pushed 2 commits.

  • 5e6195f Add files via upload
  • 90ab402 Merge pull request #2 from RestorerZ/RestorerZ-patch-1


You are receiving this because you are subscribed to this thread.

View it on GitHub or unsubscribe.

Restorer

unread,
Aug 21, 2020, 5:28:42 AM8/21/20
to vim/vim, Push

@RestorerZ pushed 2 commits.

  • b2d63b3 Translation of messages into Russian
  • de19da5 Merge pull request #3 from RestorerZ/RestorerZ-patch-2


You are receiving this because you are subscribed to this thread.

Restorer

unread,
Aug 21, 2020, 5:44:13 AM8/21/20
to vim/vim, Push

@RestorerZ pushed 2 commits.

  • 3787ce7 Vim Keymap file for Russian characters
  • 810cb73 Merge pull request #4 from RestorerZ/RestorerZ-patch-3


You are receiving this because you are subscribed to this thread.

K.Takata

unread,
Aug 21, 2020, 5:58:00 AM8/21/20
to vim/vim, Subscribed

@k-takata commented on this pull request.


In src/po/ru.po:

>  msgid "E163: There is only one file to edit"

-msgstr "E163: Для редактирования доступен только один файл"

+msgstr "E163. Для редактирования доступен только один файл"

I don't know about Russian language, but I'm afraid that this kind of changes may break existing scripts.
Here is an example in :help :catch:

		:catch /^Vim\%((\a\+)\)\=:E123:/ " catch error E123

Have you contacted the previous translator?

Restorer

unread,
Aug 21, 2020, 6:04:40 AM8/21/20
to vim/vim, Push

@RestorerZ pushed 2 commits.

  • c071b9d updating the menu in Russian
  • fa5a2d9 Merge pull request #5 from RestorerZ/RestorerZ-patch-5


You are receiving this because you are subscribed to this thread.

Restorer

unread,
Aug 21, 2020, 6:31:58 AM8/21/20
to vim/vim, Subscribed

@RestorerZ commented on this pull request.


In src/po/ru.po:

>  msgid "E163: There is only one file to edit"
-msgstr "E163: Для редактирования доступен только один файл"
+msgstr "E163. Для редактирования доступен только один файл"

Yes, in this form it will make a mistake.
According to the spelling rules of the Russian language the colon is not correct.
:catch /^Vim%((\a+))=:E123[:.]/ " catch error E123
Will it work?
I can replace the dots with a colon, but, as I said, that's not correct.

Да, в таком виде это будет давать ошибку.
По правилам правописания русского языка двоеточие не корректно.
:catch /^Vim%((\a+))=:E123[:.]/ " catch error E123
Так будет работать?
Я могу заменить точки на двоеточие, но, как я уже сказал, это не корректно.

Sergey Alyoshin

unread,
Aug 21, 2020, 11:31:54 AM8/21/20
to vim_dev, reply+ACY5DGHFMKANHDEKYL...@reply.github.com, vim/vim, Subscribed

> Have you contacted the previous translator?


No, I was not contacted and I am against this changes as they currently are.


--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/vim/vim/pull/6734/review/472362188%40github.com.

vim-dev ML

unread,
Aug 21, 2020, 11:32:18 AM8/21/20
to vim/vim, vim-dev ML, Your activity

> Have you contacted the previous translator?

No, I was not contacted and I am against this changes as they currently are.


On Fri, Aug 21, 2020 at 12:57 PM K.Takata <vim-dev...@256bit.org> wrote:

> *@k-takata* commented on this pull request.
> ------------------------------
>
> In src/po/ru.po
> <https://github.com/vim/vim/pull/6734#discussion_r474598996>:

>
> > msgid "E163: There is only one file to edit"
>
> -msgstr "E163: Для редактирования доступен только один файл"
>
> +msgstr "E163. Для редактирования доступен только один файл"
>
>
> I don't know about Russian language, but I'm afraid that this kind of
> changes may break existing scripts.
> Here is an example in :help :catch:
>
> :catch /^Vim\%((\a\+)\)\=:E123:/ " catch error E123
>
>
> Have you contacted the previous translator?
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/vim/vim/pull/6734#pullrequestreview-472362188>, or
> unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ACY5DGGY7WHON2FIEFAQVVTSBZAKFANCNFSM4QEGJI7Q>
> .

>
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_dev+u...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_dev/vim/vim/pull/6734/review/472362188%40github.com
> <https://groups.google.com/d/msgid/vim_dev/vim/vim/pull/6734/review/472362188%40github.com?utm_medium=email&utm_source=footer>
> .

K.Takata

unread,
Aug 21, 2020, 11:51:33 AM8/21/20
to vim/vim, vim-dev ML, Comment

@RestorerZ Please discuss with Sergey first.


You are receiving this because you commented.

Restorer

unread,
Aug 21, 2020, 12:19:07 PM8/21/20
to vim/vim, vim-dev ML, Comment

@RestorerZ Please discuss with Sergey first.

Well. I'll get in contact with Sergey.
This may break compatibility with scripts, but it is correct in terms of spelling.
Walk :substitute/(E\d{2,4})./\1:/ not long.

Хорошо. Я свяжусь с Сергеем.
Возможно это ломает совместимость со скриптами, но это правильно с точки зрения правописания.
Пройтись :substitute/(E\d{2,4})./\1:/ не долго.


You are receiving this because you commented.

vim-dev ML

unread,
Aug 21, 2020, 2:44:32 PM8/21/20
to vim/vim, vim-dev ML, Your activity


Sergey Alyoshin wrote:

> > Have you contacted the previous translator?
>
> No, I was not contacted and I am against this changes as they currently are.

Are you referring to change in the ru.po file or something else?


--
hundred-and-one symptoms of being an internet addict:
255. You work for a newspaper and your editor asks you to write an
article about Internet addiction...in the "first person."

/// Bram Moolenaar -- Br...@Moolenaar.net -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///

Bram Moolenaar

unread,
Aug 21, 2020, 2:44:59 PM8/21/20
to vim...@googlegroups.com, Sergey Alyoshin, reply+ACY5DGHFMKANHDEKYL...@reply.github.com

Sergey Alyoshin wrote:

> > Have you contacted the previous translator?
>
> No, I was not contacted and I am against this changes as they currently are.

Restorer

unread,
Aug 21, 2020, 2:54:03 PM8/21/20
to vim/vim, vim-dev ML, Comment

I wrote to Sergey asking him to discuss this translation.
He promised to view and comment.

Я написал Сергею с просьбой обсудить этот перевод.
Он обещал посмотреть, и дать свои комментарии.


You are receiving this because you commented.

Sergey Alyoshin

unread,
Aug 22, 2020, 4:53:57 PM8/22/20
to Bram Moolenaar, vim_dev, reply+ACY5DGHFMKANHDEKYL...@reply.github.com
On Fri, Aug 21, 2020 at 9:44 PM Bram Moolenaar <Br...@moolenaar.net> wrote:
>
>
> Sergey Alyoshin wrote:
>
> > > Have you contacted the previous translator?
> >
> > No, I was not contacted and I am against this changes as they currently are.
>
> Are you referring to change in the ru.po file or something else?

ru.po and menu translation (to Russian), which are heavily reworked by Restorer.
I do not agree with these changes: translation does change message
semantics, some terms are changed with a similar meaning, translation
stylistics also changed.

vim-dev ML

unread,
Aug 22, 2020, 4:54:18 PM8/22/20
to vim/vim, vim-dev ML, Your activity

Maxim Kim

unread,
Sep 14, 2020, 10:40:48 AM9/14/20
to vim/vim, vim-dev ML, Comment

It has translation issues, so I wouldn't accept it as is.

Moreover, I am not sure if there should be "non-working" mapping examples mentioned in runtime/keymap/russian-typograph.vim:

" Переключение языка ввода со стандартного сочетания <CTRL+^> на указанные ниже
" Для режимов вставки и замены
""или SHIFT+SPACE
"        inoremap <S-Space> <C-^>
""или CTRL+SPACE"
"        inoremap <C-Space> <C-^>
" Для режима командной строки
""или SHIFT+SPACE
"        cnoremap <S-Space> <C-^>
""или CTRL+SPACE"
"        cnoremap <C-Space> <C-^>
" Одной командой для режимов вставки, замены и командной строки
"        noremap! <S-Space> <C-^>
"        noremap! <C-Space> <C-^>
"
" Стандартное переключение по CTRL+^ после этих переназначений также сохраняется

PS, I don't use vim with russian locale as it is really inconvenient, especially if you have set confirm and have to confirm with russian д/н.


You are receiving this because you commented.

Restorer

unread,
Sep 15, 2020, 5:15:51 AM9/15/20
to vim/vim, vim-dev ML, Comment

@habamax

Moreover, I am not sure if there should be "non-working" mapping examples mentioned in runtime/keymap/russian-typograph.vim:

What doesn't work for you? The keyboard command is made as described in the
documentation, and right now this is how I switch the layout. Do you have a
layout file enabled?

А что у вас не работает? Клавиатурная команда сделана так как описано в
документации, да и прямо сейчас я именно так переключаю раскладку. У вас
подключен какой-нибудь файл раскладки?

t has translation issues, so I wouldn't accept it as is.

Yes, it is possible that there are some inaccuracies. Can you tell us what you
think needs to be improved? I would appreciate a more detailed answer.

Да, возможно, что есть какие-то неточности. Можете сказать, что на ваш взгляд
требует доработать? Был бы признателен за более развёрнутый ответ.

PS, I don't use vim with russian locale as it is really inconvenient, especially if you have set confirm and have to confirm with russian д/н.

This is a good solution, but in any of the Russian translations for Vim, you
don't need to switch the layout to Latin to confirm the selection in the dialog
box. Y/n will be processed correctly.

Хорошее решение, но в любом из русских переводов для Vim не требуется
переключение раскладки на латинский чтобы подтвердить выбор в диалоговом окне.
Будет корректно обработано y/n.


You are receiving this because you commented.

Maxim Kim

unread,
Sep 15, 2020, 5:21:31 AM9/15/20
to vim/vim, vim-dev ML, Comment

Moreover, I am not sure if there should be "non-working" mapping examples mentioned in runtime/keymap/russian-typograph.vim:

What doesn't work for you? The keyboard command is made as described in the
documentation, and right now this is how I switch the layout. Do you have a
layout file enabled?

It doesn't matter. Most of the terminals can't handle Shift+Space mapping

t has translation issues, so I wouldn't accept it as is.

Yes, it is possible that there are some inaccuracies. Can you tell us what you
think needs to be improved? I would appreciate a more detailed answer.

Well, turn on vim's builtin spell checker.

PS, I don't use vim with russian locale as it is really inconvenient, especially if you have set confirm and have to confirm with russian д/н.

This is a good solution, but in any of the Russian translations for Vim, you
don't need to switch the layout to Latin to confirm the selection in the dialog
box. Y/n will be processed correctly.

It doesn't process it correctly. I have to switch to russian layout to confirm:

image


You are receiving this because you commented.

Restorer

unread,
Sep 15, 2020, 5:55:18 AM9/15/20
to vim/vim, vim-dev ML, Comment

Moreover, I am not sure if there should be "non-working" mapping examples mentioned in runtime/keymap/russian-typograph.vim:

What doesn't work for you? The keyboard command is made as described in the
documentation, and right now this is how I switch the layout. Do you have a
layout file enabled?

It doesn't matter. Most of the terminals can't handle Shift+Space mapping

Yes? Thank you for the information. The terminal emulator that I have (ConEmu)
handles this. I'll check again. But there is also an alternative with
CTRL+SPACE.

Да? Спасибо за информацию. Эмулятор терминала который у меня (ConEmu) с этим
справляется. Я проверю ещё раз. Но там есть и вариант с CTRL+SPACE.

t has translation issues, so I wouldn't accept it as is.

Yes, it is possible that there are some inaccuracies. Can you tell us what you
think needs to be improved? I would appreciate a more detailed answer.

Well, turn on vim's builtin spell checker.

Understood. The spelling was checked, of course. I'll run it again. Thanks.

Понял. Орфография проверялась, само собой. Прогоню ещё раз. Спасибо.

PS, I don't use vim with russian locale as it is really inconvenient, especially if you have set confirm and have to confirm with russian д/н.

This is a good solution, but in any of the Russian translations for Vim, you
don't need to switch the layout to Latin to confirm the selection in the dialog
box. Y/n will be processed correctly.

It doesn't process it correctly. I am in english layout and have to switch to russian layout to confirm:

I myself always work with the Latin layout. Therefore, of course, I took this
into account when preparing this version of the translation.

Я сам постоянно работаю с латинской раскладкой. Поэтому конечно учитывал это при
подготовке этой редакции перевода.
confim1


You are receiving this because you commented.

Christian Brabandt

unread,
Sep 15, 2020, 6:35:18 AM9/15/20
to vim/vim, vim-dev ML, Comment

Ctrl-Space might also not work universally. Please see this: https://vimhelp.org/vim_faq.txt.html#faq-20.5


You are receiving this because you commented.

Restorer

unread,
Sep 15, 2020, 7:00:19 AM9/15/20
to vim/vim, vim-dev ML, Comment

@chrisbra

Ctrl-Space might also not work universally. Please see this: https://vimhelp.org/vim_faq.txt.html#faq-20.5

Understood, thanks. I will definitely write this in the accompanying part to
this layout.
I often see complaints on forums and in discussions that switching via CTRL-^ is
not very convenient. So it's more like a template for how it can be changed.
Although... anyone who can alter this template for themselves, will probably be
able to do it without such a template.
Yes, I will need to tell that these combinations may not work. Thanks.

Понял, спасибо. Я это обязательно напишу в сопроводительной части к этой
раскладке.
Очень часто вижу жалобы на форумах и в обсуждении, что переключение через CTRL-^
не очень удобно. Так что это скорее как шаблон как это можно изменить.
Хотя... тот кто сможет переделать этот шаблон под себя, наверняка
сможет сделать это и без такого шаблона.
Да, мне надо будет указать, что такие комбинации могут не работать. Спасибо.


You are receiving this because you commented.

Maxim Kim

unread,
Sep 15, 2020, 7:01:43 AM9/15/20
to vim/vim, vim-dev ML, Comment

On 15.09.2020 14:00, Restorer wrote:
>
> @chrisbra <https://github.com/chrisbra>

>
> Ctrl-Space might also not work universally. Please see this:
> https://vimhelp.org/vim_faq.txt.html#faq-20.5
> <https://vimhelp.org/vim_faq.txt.html#faq-20.5>
>
> Understood, thanks. I will definitely write this in the accompanying
> part to
> this layout.
> I often see complaints on forums and in discussions that switching via
> CTRL-^ is
> not very convenient. So it's more like a template for how it can be
> changed.
> Although... anyone who can alter this template for themselves, will
> probably be
> able to do it without such a template.
> Yes, I will need to tell that these combinations may not work. Thanks.
>
I would just remove that comment from the file at all.


> —
>
> You are receiving this because you were mentioned.

> Reply to this email directly, view it on GitHub
> <https://github.com/vim/vim/pull/6734#issuecomment-692641443>, or
> unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AABZKFQ6URP4OOHY35JZ76LSF5CLXANCNFSM4QEGJI7Q>.
>


You are receiving this because you commented.

Restorer

unread,
Sep 15, 2020, 7:16:30 AM9/15/20
to vim/vim, vim-dev ML, Comment

@habamax

I would just remove that comment from the file at all.

Well yes, can do that.
Then don't have to explain that something might not work. It is better to just link to the documentation as you can reassign switching layouts.
It's probably better to remove it from the file. I'll think about it, thank you.

Ну да, можно и так сделать.
Тогда не придется расписывать, что что-то может не работать. Лучше просто дать ссылку на документацию как можно переназначить переключение раскладки.
Наверное это лучше убрать из файла. Я подумаю, спасибо.

Restorer

unread,
Sep 18, 2020, 11:10:06 AM9/18/20
to vim/vim, vim-dev ML, Comment

due to errors made by the author when creating this pull request

из-за ошибок сделанных автором при создании этого запроса на принятие

Restorer

unread,
Sep 18, 2020, 11:10:08 AM9/18/20
to vim/vim, vim-dev ML, Comment

Closed #6734.

Reply all
Reply to author
Forward
0 new messages