From: Ville Herva <vherva@niksula.hut.fi>
To: cygwin@cygwin.com
Subject: Re: Accessing filenames with different charsets
Date: Wed, 03 Jul 2002 03:30:00 -0000 [thread overview]
Message-ID: <20020703101822.GJ9092@niksula.cs.hut.fi> (raw)
In-Reply-To: <004e01c22278$346ec610$0100a8c0@advent02>
On Wed, Jul 03, 2002 at 10:58:38AM +0100, you [Chris January] wrote:
>
> I wrote a patch for Cygwin yesterday that converts Unicode filenames to UTF8
> and back for some file operations.
Nice!
> This should do what you want and allow you to restore the names correctly
> later. I will post it to cygwin-patches sometime today, but I'm not sure
> whether the patch will appear in a Cygwin snapshot anytime soon, if not I
> can send you the modified binary and the patch directly for you to try.
> The only disadvantage with this method is it still makes the filenames
> impossible to type. However, if you have your terminal set up correctly,
> it is certainly possible to read them as they should be (e.g. in xterm
> with UTF8 support turned on). If you are using a graphical file browser
> like konqueror then that makes things even easier.
Yes, UTF8 approach is propably preferable in all ways. As for typing, I
imagine you can get the 8.3 name with
for i in *; do echo $i: `cygpath -w -s $i`; done
so you'll be able to type some name for the file as well.
I'm really glad to see this fixed.
What about filenames longer than MAX_PATH? Those can only be accessed with
"\\.\<path>" and unicode file functions...
-- v --
v@iki.fi
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2002-07-03 10:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-01 1:59 Ville Herva
2002-07-02 14:50 ` Ville Herva
2002-07-02 14:59 ` Chris January
2002-07-02 15:05 ` Ville Herva
2002-07-03 2:48 ` Ville Herva
2002-07-03 3:18 ` Chris January
2002-07-03 3:30 ` Ville Herva [this message]
2002-07-03 3:38 ` Chris January
2002-07-03 4:00 ` Ville Herva
2002-07-03 5:20 ` Re[2]: " Nicholas Wourms
2002-07-03 5:29 ` Chris January
2002-07-03 6:24 ` Bernard A Badger
2002-07-03 6:31 ` Chris January
2002-07-03 9:08 ` dir \\.\c:\ Bernard A Badger
2002-07-03 12:51 ` Ville Herva
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=20020703101822.GJ9092@niksula.cs.hut.fi \
--to=vherva@niksula.hut.fi \
--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).