unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: 75379@debbugs.gnu.org, orontee@gmail.com
Subject: bug#75379: 30.0.93; project-find-regexp expects "C" or "en" locale
Date: Tue, 07 Jan 2025 16:50:34 +0200	[thread overview]
Message-ID: <86plky4r0l.fsf@gnu.org> (raw)
In-Reply-To: <c04ef9f0-780f-4939-8483-61bc3e4ffcff@gutov.dev> (message from Dmitry Gutov on Tue, 7 Jan 2025 16:26:46 +0200)

> Date: Tue, 7 Jan 2025 16:26:46 +0200
> Cc: orontee@gmail.com, 75379@debbugs.gnu.org
> From: Dmitry Gutov <dmitry@gutov.dev>
> 
> On 07/01/2025 16:23, Eli Zaretskii wrote:
> >> 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.
> > If that's the environment variables, they don't work reliably on
> > Windows, as I explained.
> 
> Please correct me if I'm wrong, but it sounds like either gettext is 
> supported, and these vars can be used to set the locale to English, or 
> gettext is unsupported, and the output is in English anyway. Both 
> scenarios are what we want to have in the end.

For programs compiled with gettext, I think you are right.





  reply	other threads:[~2025-01-07 14:50 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
2025-01-07 14:23           ` Eli Zaretskii
2025-01-07 14:26             ` Dmitry Gutov
2025-01-07 14:50               ` Eli Zaretskii [this message]
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86plky4r0l.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=75379@debbugs.gnu.org \
    --cc=dmitry@gutov.dev \
    --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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).