From: Patrick Giraudoux <patrick.giraudoux@univ-fcomte.fr>
Cc: Help-gnu-emacs@gnu.org, PG <pgiraudo@univ-fcomte.fr>
Subject: Re: emacs cannot read accent properly in a path
Date: Sat, 23 Dec 2006 17:19:49 +0100 [thread overview]
Message-ID: <458D5725.2050407@univ-fcomte.fr> (raw)
In-Reply-To: <343ECF38-6D5D-43CF-9CAC-BC788BA0104D@Web.DE>
>
> would be correct syntax, if your system would know about "fr_FR.UTF-8"
> as a locale. You should consult you system with locale (man locale for
> some details)
tried it locale -a and fr_FR.UTF-8 is in the list.
Tried to set
export LANG=fr_FR.UTF-8
into ~/.bashrc
Did not work
>
> And if this fails, then check whether you set-language-environment –
> if you do, comment it!
I did it through the menu Options > Mule > Set Language Environment
setting up UTF-8 as well as > European > French.
No result.
>
> Do the Elisp statements change the behaviour? Are the DOS or Windows
> file name "exported" and "imported" in the right encoding? When the
> file names are in DOS or Windows in some Code Page, then you can't
> mount them in Linux as UTF-8 ... (although the excerpt ``A"´´ for è
> makes one believe, but è is in UTF-8 C3 A8, i.e. è)
Actually the bash reads DOS encoding well including the accents, and
even emacs autocompletion is correct in the mini-buffer if emacs is
started from ~/. The è unstead è just come when starting emacs within a
directory which includes letter accents in the path... Very strange.
Anyway, many thanks for your help,
Patrick
>
> --
> Greetings
>
> Pete
>
> Never be led astray onto the path of virtue
>
>
>
>
next prev parent reply other threads:[~2006-12-23 16:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-23 10:41 emacs cannot read accent properly in a path PG
2006-12-23 14:09 ` Peter Dyballa
2006-12-23 14:40 ` PG
2006-12-23 15:46 ` Peter Dyballa
2006-12-23 16:19 ` Patrick Giraudoux [this message]
2006-12-23 17:17 ` Peter Dyballa
2006-12-23 19:11 ` Patrick Giraudoux
2006-12-23 20:05 ` Peter Dyballa
2006-12-23 15:48 ` Peter Dyballa
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=458D5725.2050407@univ-fcomte.fr \
--to=patrick.giraudoux@univ-fcomte.fr \
--cc=Help-gnu-emacs@gnu.org \
--cc=pgiraudo@univ-fcomte.fr \
/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).