From: <tomas@tuxteam.de>
To: Kepa <gnu.cognition199@slmails.com>
Cc: Ihor Radchenko <yantar92@posteo.net>, emacs-orgmode@gnu.org
Subject: Re: Issue opening files with accented words, using org-attach-open
Date: Tue, 6 Aug 2024 06:28:50 +0200 [thread overview]
Message-ID: <ZrGmgv3L3qdXxFDr@tuxteam.de> (raw)
In-Reply-To: <172289067755.6.9513778135573811442.398221968@slmails.com>
[-- Attachment #1: Type: text/plain, Size: 814 bytes --]
On Mon, Aug 05, 2024 at 08:44:29PM +0000, Kepa wrote:
> Funny: the path was p:/170 Buzon/oq.pdf, where the "o" was accentuated: https://en.m.wikipedia.org/wiki/%C3%93
Perhaps relevant:
- what file systems are on each of those drives? NTFS? some Linux?
(Background: most Unix/Linux file systems consider file names
as strings of bytes. What encoding /characters/ have there is
up to the application [1]; NTFS has UTF-16 encoded Unicode, although
if you access it with POSIX fopen(), it gets translated to UTF-8).
- what applications do you access "normally" the "drive" which is
showing the problem? What did you create the file with?
Cheers
[1] typically to the process's locale's encoding which creates/accesses
it. Lots of fun when they're not consistent :-)
--
t
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2024-08-06 4:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-04 20:37 Issue opening files with accented words, using org-attach-open Kepa
2024-08-05 4:33 ` tomas
2024-08-05 9:04 ` Kepa
2024-08-05 9:28 ` tomas
2024-08-05 18:53 ` Ihor Radchenko
2024-08-05 20:24 ` Kepa
2024-08-05 20:44 ` Kepa
2024-08-06 4:28 ` tomas [this message]
2024-08-06 17:23 ` Ihor Radchenko
2024-08-06 19:37 ` Kepa
2024-08-10 13:53 ` Ihor Radchenko
2024-08-10 17:51 ` Kepa
2024-08-11 16:31 ` Ihor Radchenko
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZrGmgv3L3qdXxFDr@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=emacs-orgmode@gnu.org \
--cc=gnu.cognition199@slmails.com \
--cc=yantar92@posteo.net \
/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.savannah.gnu.org/cgit/emacs/org-mode.git
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).