emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: M <Elwood151@web.de>
To: emacs orgmode-mailinglist <emacs-orgmode@gnu.org>
Subject: Re: Problem with special characters in dired and attachment paths
Date: Mon, 02 Sep 2013 23:09:16 +0200	[thread overview]
Message-ID: <CE4ACB1C.18269%Elwood151@web.de> (raw)
In-Reply-To: <trinity-9f59bf80-9eb3-489f-a949-544150fc1311-1377099779092@3capp-webde-bs17>

it seems that this is a bug (or missing feature) of Emacs on MS Windows:

see http://debbugs.gnu.org/cgi/bugreport.cgi?bug=15236

Did noone else using Emacs on Windows encounter those problems?

Kind regards


> Datum: Wed, 21 Aug 2013 17:42:59 +0200 (CEST)
> An: emacs orgmode-mailinglist <emacs-orgmode@gnu.org>
> Betreff: [O] Problem with special characters in dired and attachment paths
> I'm having problems with special characters like äöü in dired mode and in
> attachment paths:
> 1) When I'm trying to access a directory with M-x dired, the displayed path
> contains strange characters like e.g. "\374" for "ü" or "\366" for "ö".
> Same is true for directory and file listings displayed by dired.
> Is there a setting which can make dired display the characters with the
> correct encoding?
> 2) my other problem seems to be related:
> I currently added a long server path as attachment directory in org-mode, like
> //servername/dir1/dir2/dir2/dir4/etcetera/Zubehör/
> (I usually copy the UNC path in Windows 7 Explorer with the PathCopy context
> menu)
> The path is shown like that in :ATTACH_DIR: in the properties with the "ö"
> correctly displayed.
> When I type C-c C-a C-f to open the directory in Windows Explorer, it creates
> a new directory at the same path called Zubehör which is opened instead of
> the right one.
> How can I solve those 2 problems?
> Kind regards
> Martin

      reply	other threads:[~2013-09-02 21:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-21 15:42 Problem with special characters in dired and attachment paths Martin Beck
2013-09-02 21:09 ` M [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:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CE4ACB1C.18269%Elwood151@web.de \
    --to=elwood151@web.de \
    --cc=emacs-orgmode@gnu.org \


* 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


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).