DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 417A2388206F
Date: Thu, 13 Jun 2024 16:00:20 -0700 (PDT)
To: Cygwin <cygwin@cygwin.com>
Subject: Re: unable to remove oddly-named directory
In-Reply-To: <f2641cc4-cfb4-4248-a50c-23e611b0bb9a@SystematicSW.ab.ca>
Message-ID: <dc040319-9b63-ef3f-d1be-96d9bda493c6@jdrake.com>
References: <6f296b1c-ad43-81e3-163b-4bc4d1b8ed4c@jdrake.com>
 <f2641cc4-cfb4-4248-a50c-23e611b0bb9a@SystematicSW.ab.ca>
MIME-Version: 1.0
Precedence: list
From: Jeremy Drake via Cygwin <cygwin@cygwin.com>
Reply-To: Jeremy Drake <cygwin@jdrake.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: cygwin-bounces+archive-cygwin=delorie.com@cygwin.com
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie.com@cygwin.com>

On Thu, 13 Jun 2024, Brian Inglis via Cygwin wrote:

> These reserved surrogate values should probably either be blocked, or encoded
> at
> the file system interface layer so they can be round tripped, like the Windows
> reserved characters, in the BMP or SMP PUAs.
>
> Reserved surrogate ranges are D800-DBFF|DC00-DFFF.

Cygwin already generates these unpaired surrogates in filenames, at least
here:
https://github.com/cygwin/cygwin/blob/84dff09aa0d3ad998551e3f91c61dc0534b0b8bf/winsup/cygwin/syscalls.cc#L342-L350

I was looking into ways to automate cleaning up these files, which would
likely be hampered if things like findutils would suddenly start
disallowing me from finding files with these characters in them.

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple