Jun T. wrote: > On 2016/02/02, at 20:38, Bram Moolenaar <b...@moolenaar.net> wrote: > > > Patch 7.4.1237 > > Problem: Can't translate message without adding a line break. > > Solution: Join the two parts of the message. > > Files: src/memline.c > > Then the *.po files for all the languages must be updated. > If we are really going to that, then I think it would be better > to add \n at the end of the 1st message > " file when making changes." > instead of joining the two messages.
If we want to avoid untranslated messages, we would need to stop making any changes. That's not a good plan. Let's just assume translators will do their work soon enough. > I guess the author of memline.c has just forgotten the \n. > She/he wanted to print "Quit, or ..." on the next line by itself, > because the message was important. > > And adding a \n is easier than joining two messages if we must > update all the *.po files. The missing line break is intentional. The whole message is long, adding another line break increases the chance it doesn't fit on the display. The break in strings was there just to fit it in the source code. That was not the best reason. So let's fix it now. -- hundred-and-one symptoms of being an internet addict: 128. You can access the Net -- via your portable and cellular phone. /// Bram Moolenaar -- b...@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 /// -- -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
