public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ilya Basin <basinilya@gmail.com>
To: corinna-cygwin@cygwin.com
Cc: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: env var or mount option for multibyte<->unicode filenames conversion
Date: Mon, 22 Aug 2011 06:36:00 -0000	[thread overview]
Message-ID: <1332896747.20110822103551@gmail.com> (raw)
In-Reply-To: <103846589.20110818141934@gmail.com>

Corinna Vinschen <corinna-cygwin <at> cygwin.com> writes:

> 
> On Aug 18 14:19, Ilya Basin wrote:
> > Hi. Currently, the code page for internal convertion of file names to
> > unicode depends on programs's locale.
> > I want to keep UTF-8 as current locale, but use CP1251 for this
> > conversion. Is it possible?
> 
> Maybe if you describe your problem slightly more detailed?  Why would
> you want CP1251 in a Cygwin application if all other apps are using UTF-8?
> 
> Corinna
> 
Hi! I've just found your reply in web archives; didn't receive a copy
for some reason.

It's for git. Let me repost the question to git list:

Most of our developers use msysgit which stores filenames in CP1251
encoding. Two of us use cygwin and linux.

When checkout on both linux and cygwin, Russian filenames are garbled.

On Cygwin it even worse, because the conversion of invalid UTF-8 chars
to Unicode, made by Cygwin is irreversible, causing git to miss
the files it've just checked out. Workaround for Cygwin is to change
LANG from "C.UTF-8" to "ru_RU.CP1251". It fixes filenames, but brakes
everything else: log (fixed by i18n.logOutputEncoding), status, show,
diff.

-- 


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

      parent reply	other threads:[~2011-08-22  6:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-18 10:19 Ilya Basin
2011-08-18 10:46 ` Corinna Vinschen
2011-08-22  6:36 ` Ilya Basin [this message]

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=1332896747.20110822103551@gmail.com \
    --to=basinilya@gmail.com \
    --cc=corinna-cygwin@cygwin.com \
    --cc=cygwin@cygwin.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.
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).