vim-patch:9.1.1483: not possible to translation position in buffer (#37099)

Problem:  not possible to translation position in buffer
Solution: use _() macro to mark the output as translatable
          (Emir SARI)

Row/Column indicator separator is currently not customizable. Some
languages have a space after the comma as the usual practice, plus this
would help translators use a custom separator like colons if necessary.

Additionally, after a save, the line and the byte indicator is also
hardcoded, this enables i18n for that as well.

closes: vim/vim#17608

81f9815831

Co-authored-by: Emir SARI <emir_sari@icloud.com>
This commit is contained in:
zeertzjq
2025-12-26 08:30:21 +08:00
committed by GitHub
parent 5a1a92cc7a
commit a565774bfc
2 changed files with 6 additions and 2 deletions

View File

@@ -2146,7 +2146,8 @@ void msg_add_lines(int insert_space, linenr_T lnum, off_T nchars)
size_t len = strlen(IObuff);
if (shortmess(SHM_LINES)) {
snprintf(IObuff + len, IOSIZE - len, "%s%" PRId64 "L, %" PRId64 "B",
snprintf(IObuff + len, IOSIZE - len,
_("%s%" PRId64 "L, %" PRId64 "B"), // l10n: L as in line, B as in byte
insert_space ? " " : "", (int64_t)lnum, (int64_t)nchars);
} else {
len += (size_t)snprintf(IObuff + len, IOSIZE - len,

View File

@@ -491,7 +491,10 @@ void redraw_ruler(void)
#define RULER_BUF_LEN 70
char buffer[RULER_BUF_LEN];
int bufferlen = vim_snprintf(buffer, RULER_BUF_LEN, "%" PRId64 ",",
// row number, column number is appended
// l10n: leave as-is unless a space after the comma is preferred
// l10n: do not add any row/column label, due to the limited space
int bufferlen = vim_snprintf(buffer, RULER_BUF_LEN, _("%" PRId64 ","),
(wp->w_buffer->b_ml.ml_flags & ML_EMPTY)
? 0
: (int64_t)wp->w_cursor.lnum);