From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 33E243858D28; Wed, 30 Aug 2023 20:15:06 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 33E243858D28 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1693426506; bh=1n7G8wCBtXC1RtwqXfTrLwRqxFyZTvzG+IZew1RXlcY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=M+ZMJnhoqkrywjns1iel0lFlphfXgwGLF/PuzaB+X2C/sxX+sehsGGYfxOb2lMgWD Mfzo9wf3SsXGRwKzINiS/PC62oDovRILuaAbwCWGJRLpyX/v/UC7dbd12/hlmvrOct i5vIgoNTQqxHWyfXUxLEoU5aRSZYVXLB3dRE1L8I= From: "thiago at kde dot org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/111244] std::filesystem::path encoding mismatches locale on Windows Date: Wed, 30 Aug 2023 20:15:05 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 13.2.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: thiago at kde dot org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D111244 --- Comment #5 from Thiago Macieira --- (In reply to Jonathan Wakely from comment #3) > Somebody else will have to fix this, I've already wasted too much of my l= ife > making std:: filesystem (mostly) work on Windows. Same here. (In reply to Costas Argyris from comment #4) > I'm wondering if it will work after embedding a UTF-8 manifest into your > a.out executable, as described here: >=20 > https://learn.microsoft.com/en-us/windows/apps/design/globalizing/use-utf= 8- > code-page I can't embed a UTF-8 manifest in my DLL and much less in my .a. As a libra= ry writer (I'm the QtCore maintainer), that's out of my hands - it is an application decision. If GCC+Binutils team wants to enforce that for the future, be my guest. I'd support your decision; I think it's high time this happened. But I'm sure t= here would be a lot of push-back from people who can't do that because their existing Windows applications rely on the legacy encodings or those who dep= loy to Windows versions that didn't have such support. I have a vague memory of discussing this in the Qt development mailing list, but can't find it. A softer approach is for std::filesystem to declare that it only supports UTF-8-manifested applications (closing this bug as WONTFIX / working-as-designed). I'd again support your decision and will simply pass = the requirement along to my users.=