From: Eli Zaretskii <eliz@gnu.org>
To: "Laimonas Vėbra" <laimonas.vebra@gmail.com>
Cc: lekktu@gmail.com, 6546@debbugs.gnu.org
Subject: bug#6546: win32 grep/shell utf-8 encoding
Date: Thu, 22 Jul 2010 22:53:34 +0300 [thread overview]
Message-ID: <83k4oncmyp.fsf@gnu.org> (raw)
In-Reply-To: <4C488CCC.6080107@gmail.com>
> Date: Thu, 22 Jul 2010 21:24:12 +0300
> From: Laimonas Vėbra <laimonas.vebra@gmail.com>
> Cc: 6546@debbugs.gnu.org
>
> The problem is not here. I can change the encoding of the command string
> (which is passed to external cygwin apps) using
> coding-system-for-write. It works (converted correctly utf-8->cp1257,
> cp1251, etc), but it doesn't help, because of the way the args (command
> line) are passed/transcoded through the winapi (CreateProcessA) and
> cygwin layer.
Did you try to add a suitably-valued LANG variable to
process-environment? That would at least force Cygwin executables to
work in the Windows codepage.
> This bug is related to bug#6705 (there are detailed description of
> what's happening)
Then please merge them.
next prev parent reply other threads:[~2010-07-22 19:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-01 8:46 bug#6546: win32 grep/shell utf-8 encoding Laimonas Vėbra
2010-07-01 17:26 ` Eli Zaretskii
2010-07-01 18:05 ` Laimonas Vėbra
2010-07-22 12:50 ` Juanma Barranquero
2010-07-22 14:11 ` Laimonas Vėbra
2010-07-22 15:02 ` Juanma Barranquero
2010-07-22 18:24 ` Laimonas Vėbra
2010-07-22 19:53 ` Eli Zaretskii [this message]
2010-07-22 21:48 ` Laimonas Vėbra
2010-07-22 23:00 ` Juanma Barranquero
2010-07-23 10:24 ` Eli Zaretskii
2010-07-23 12:54 ` Laimonas Vėbra
2010-07-23 14:23 ` Eli Zaretskii
2010-07-23 15:50 ` Laimonas Vėbra
2010-07-23 18:09 ` Eli Zaretskii
2010-07-23 19:07 ` Laimonas Vėbra
2022-04-24 12:01 ` bug#6546: bug#6705: w32 cmdproxy.c pass args to cygwin; erroneous charset conversion (problem description, solution/suggestion) Lars Ingebrigtsen
2022-04-24 12:31 ` Eli Zaretskii
2022-04-24 13:25 ` Lars Ingebrigtsen
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=83k4oncmyp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=6546@debbugs.gnu.org \
--cc=laimonas.vebra@gmail.com \
--cc=lekktu@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).