public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "thiago at kde dot org" <gcc-bugzilla@gcc.gnu.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	[thread overview]
Message-ID: <bug-111244-4-PMlfsOmHrm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111244-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111244

--- Comment #5 from Thiago Macieira <thiago at kde dot org> ---
(In reply to Jonathan Wakely from comment #3)
> Somebody else will have to fix this, I've already wasted too much of my life
> 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:
> 
> https://learn.microsoft.com/en-us/windows/apps/design/globalizing/use-utf8-
> code-page

I can't embed a UTF-8 manifest in my DLL and much less in my .a. As a library
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 there
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 deploy
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.

  parent reply	other threads:[~2023-08-30 20:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-30 19:10 [Bug c++/111244] New: " thiago at kde dot org
2023-08-30 19:25 ` [Bug libstdc++/111244] " pinskia at gcc dot gnu.org
2023-08-30 19:31 ` thiago at kde dot org
2023-08-30 19:59 ` redi at gcc dot gnu.org
2023-08-30 20:03 ` costas.argyris at gmail dot com
2023-08-30 20:15 ` thiago at kde dot org [this message]
2023-08-30 20:50 ` costas.argyris at gmail dot com
2023-08-30 20:56 ` thiago at kde dot org

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=bug-111244-4-PMlfsOmHrm@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).