From: Vincent Lefevre <vincent@vinc17.net>
To: zsh-workers@zsh.org
Subject: Re: Subversion completion don't work with UTF8 (and other) file names
Date: Tue, 14 May 2013 15:28:40 +0200 [thread overview]
Message-ID: <20130514132840.GA3544@ypig.lip.ens-lyon.fr> (raw)
In-Reply-To: <20130507102115.59d18d55@pwslap01u.europe.root.pri>
On 2013-05-07 10:21:15 +0100, Peter Stephenson wrote:
> I suppose I was asking the more general question: given a utility we
> need output from, is it OK to keep LC_CTYPE and set everything else
> to C or is there something else going on?
It depends on the utility. With some utilities, you may want to
set LC_CTYPE to C in order to avoid non-ASCII characters and/or
get charset-independent output.
For instance, with the US-ASCII charmap,
$ LANG=C LC_CTYPE=C cp foo
cp: missing destination file operand after 'foo'
Try 'cp --help' for more information.
but with the UTF-8 charmap,
$ LANG=C LC_CTYPE=C.UTF-8 cp foo
cp: missing destination file operand after ‘foo’
Try 'cp --help' for more information.
The quotes of foo are non-ASCII ones in the latter case.
But if the filename can have non-ASCII characters...
$ LANG=C LC_CTYPE=C cp aéb
cp: missing destination file operand after 'a\303\251b'
Try 'cp --help' for more information.
while one gets the accented character in UTF-8:
$ LANG=C LC_CTYPE=C.UTF-8 cp aéb
cp: missing destination file operand after ‘aéb’
Try 'cp --help' for more information.
but things get complex if the filename has special characters
(even ASCII ones)...
--
Vincent Lefèvre <vincent@vinc17.net> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
prev parent reply other threads:[~2013-05-14 13:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 11:51 Paul Romanchenko
2013-04-26 12:39 ` Vincent Lefevre
2013-04-26 14:44 ` Peter Stephenson
2013-04-26 15:35 ` Vincent Lefevre
2013-04-29 8:57 ` Peter Stephenson
2013-04-29 13:58 ` Bart Schaefer
2013-05-04 2:15 ` Oliver Kiddle
2013-05-04 13:23 ` Peter Stephenson
2013-05-07 7:38 ` Oliver Kiddle
2013-05-07 9:21 ` Peter Stephenson
2013-05-14 13:28 ` Vincent Lefevre [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=20130514132840.GA3544@ypig.lip.ens-lyon.fr \
--to=vincent@vinc17.net \
--cc=zsh-workers@zsh.org \
/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.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).