public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Gionatan Danti <g.danti@assyoma.it>
To: cygwin@cygwin.com
Subject: Re: Can not stat file with utf char U+F020
Date: Tue, 18 Apr 2023 23:09:07 +0200	[thread overview]
Message-ID: <1a7db5a68644e5b66634d5af9b402caf@assyoma.it> (raw)
In-Reply-To: <fc6d3aa5f3ae525a777e65d62ccbd6c2@assyoma.it>

Il 2023-04-17 15:46 Gionatan Danti via Cygwin ha scritto:
> First, I use the "dos" mount option to always trigger conversion of
> space and dot at filename end into F+00xx chars. Now I am able to
> create such strange-looking file (in Explorer) within cygwin itself.
> For example, touch "zzs " now results in "zzs+strangechar" in
> Explorer. Both cygwin and windows are able to read/write such file.
> 
> But if I edit the filename via Explorer adding an extension (ie: from
> "zzs+strangechar" to "zzs+strangechar.txt") now cygwin is suddenly
> unable to read/write the file.
> 
> It seems to me that the appended chars prevent cygwin to translate
> back F0xx to 00xx (as the PUA char is not at the end of the filename
> anymore).
> 
> So, two paths should be available:
> - always translate back F0xx to 00xx even if not at the end of 
> filename;
> - otherwise, if too invasive to do it unconditionally, add an option
> as "always_translate_pua" (default: off) to enable such behavior based
> on user needs.
> 
> I would (naively?) think that option 1 (always translate back PUA)
> should be the preferred approach, as cygwin is at the moment
> effectively unable to access some files.

Hi all,
any thoughts on the matter? Am I missing something?

Thanks.

-- 
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti@assyoma.it - info@assyoma.it
GPG public key ID: FF5F32A8

  reply	other threads:[~2023-04-18 21:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-14 17:53 Gionatan Danti
2023-04-14 19:00 ` Corinna Vinschen
2023-04-14 19:54   ` Brian Inglis
2023-04-14 20:20     ` Corinna Vinschen
2023-04-14 20:21     ` Gionatan Danti
2023-04-14 20:25       ` Corinna Vinschen
2023-04-14 21:01         ` Gionatan Danti
2023-04-17  5:36           ` Gionatan Danti
2023-04-17  9:05             ` Corinna Vinschen
2023-04-17 10:58               ` Andrey Repin
2023-04-17 13:46               ` Gionatan Danti
2023-04-18 21:09                 ` Gionatan Danti [this message]
2023-04-19  1:10                   ` L A Walsh
2023-04-19 11:56                     ` Gionatan Danti
2023-04-14 20:17   ` Gionatan Danti
2023-04-14 20:40     ` Corinna Vinschen
2023-04-14 20:51       ` Gionatan Danti
2023-04-15  5:10     ` Brian Inglis
2023-04-17  9:10       ` Corinna Vinschen

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=1a7db5a68644e5b66634d5af9b402caf@assyoma.it \
    --to=g.danti@assyoma.it \
    --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).