patch 9.1.1483: not possible to translation position in buffer

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: #17608

Signed-off-by: Emir SARI <emir_sari@icloud.com>
Signed-off-by: Christian Brabandt <cb@256bit.org>
This commit is contained in:
Emir SARI
2025-06-26 20:38:16 +02:00
committed by Christian Brabandt
parent fe803c8c04
commit 81f9815831
3 changed files with 8 additions and 2 deletions

View File

@ -734,7 +734,10 @@ win_redr_ruler(win_T *wp, int always, int ignore_pum)
wp->w_p_list = TRUE;
}
bufferlen = vim_snprintf((char *)buffer, RULER_BUF_LEN, "%ld,",
// 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
bufferlen = vim_snprintf((char *)buffer, RULER_BUF_LEN, _("%ld,"),
(wp->w_buffer->b_ml.ml_flags & ML_EMPTY)
? 0L
: (long)(wp->w_cursor.lnum));

View File

@ -3189,7 +3189,8 @@ msg_add_lines(
if (shortmess(SHM_LINES))
vim_snprintf((char *)IObuff + len, IOSIZE - (size_t)len,
"%s%ldL, %lldB", insert_space ? " " : "", lnum, (varnumber_T)nchars);
// l10n: L as in line, B as in byte
_("%s%ldL, %lldB"), insert_space ? " " : "", lnum, (varnumber_T)nchars);
else
{
len += vim_snprintf((char *)IObuff + len, IOSIZE - (size_t)len,

View File

@ -709,6 +709,8 @@ static char *(features[]) =
static int included_patches[] =
{ /* Add new patch number below this line */
/**/
1483,
/**/
1482,
/**/