From: Dmitry Gutov <dmitry@gutov.dev>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 75379@debbugs.gnu.org, orontee@gmail.com
Subject: bug#75379: 30.0.93; project-find-regexp expects "C" or "en" locale
Date: Tue, 7 Jan 2025 16:17:24 +0200 [thread overview]
Message-ID: <e2951c8d-e862-4a1c-b7c2-d8f8d6c2687b@gutov.dev> (raw)
In-Reply-To: <86a5c56mpa.fsf@gnu.org>
On 05/01/2025 22:16, Eli Zaretskii wrote:
>>> First, the Windows locale-dependent routines don't heed environment
>>> variables, so setting LANG etc. in the environment will only do what
>>> you expect if the program in question was either explicitly programmed
>>> to pay attention to those variables or was linked with Gnulib
>>> replacements for locale functions.
>>>
>>> And second LC_MESSAGES is not supported by Windows locales at all.
>>
>> Okay, but first of all, do Grep or Ripgrep use different localizations
>> on Windows, not just English?
>
> For Grep, it depends on how it was configured when building. The
> default configuration uses gettext to translate messages, and this
> message is marked as translated.
Okay, but if it's not configured to use gettext, would it just use
English, or are there some other mechanisms?
Looking at
https://stackoverflow.com/questions/9268379/non-localized-version-of-mingw-msys2,
there recommendations are along the standard lines of using either LANG
or LC_ALL.
> For Ripgrep, I don't know.
It seems to me Ripgrep is simply not translated, which is just fine for us.
next prev parent reply other threads:[~2025-01-07 14:17 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-05 10:35 bug#75379: 30.0.93; project-find-regexp expects "C" or "en" locale Matthias Meulien
2025-01-05 18:03 ` Dmitry Gutov
2025-01-05 18:46 ` Eli Zaretskii
2025-01-05 19:35 ` Dmitry Gutov
2025-01-05 20:16 ` Eli Zaretskii
2025-01-07 14:17 ` Dmitry Gutov [this message]
2025-01-07 14:23 ` Eli Zaretskii
2025-01-07 14:26 ` Dmitry Gutov
2025-01-07 14:50 ` Eli Zaretskii
2025-01-05 21:22 ` Matthias Meulien
2025-01-05 21:29 ` Matthias Meulien
2025-01-06 13:03 ` Eli Zaretskii
2025-01-06 1:55 ` Dmitry Gutov
2025-01-06 12:36 ` Matthias Meulien
2025-01-06 12:42 ` Matthias Meulien
2025-01-06 14:13 ` Dmitry Gutov
2025-01-06 14:11 ` Dmitry Gutov
2025-01-07 5:42 ` Matthias Meulien
2025-01-07 12:45 ` Eli Zaretskii
2025-01-07 14:24 ` Dmitry Gutov
2025-01-06 17:36 ` Juri Linkov
2025-01-06 20:33 ` Dmitry Gutov
2025-01-07 17:39 ` Juri Linkov
2025-01-07 19:38 ` Dmitry Gutov
2025-01-08 7:48 ` Juri Linkov
2025-01-06 13:02 ` Eli Zaretskii
2025-01-06 14:13 ` Dmitry Gutov
2025-01-05 21:10 ` Matthias Meulien
2025-01-06 1:32 ` Dmitry Gutov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e2951c8d-e862-4a1c-b7c2-d8f8d6c2687b@gutov.dev \
--to=dmitry@gutov.dev \
--cc=75379@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=orontee@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.