> Date: Wed, 29 Sep 2021 10:06:22 -0700
> From: "Kaz Kylheku (gmake)" <729-670-0...@kylheku.com>
> Cc: nob...@gmail.com, help-make@gnu.org
> 
> > I think the underlying OS also must support UTF-8 encoded file names
> > (or be agnostic to file-name encodings).  So, for example, on
> > MS-Windows using UTF-8 in Makefiles will not work if it is used for
> > file names.
> 
> Test using Cygwin:

Cygwin is not MS-Windows, it provides a rich layer of Posix
functionality, including UTF-8 support, above Windows.  Try the native
Windows build of GNU Make instead.

> When I open the dire^H^H^H^Hfolder in Windows Explorer,
> the 対象 name correctly appears, too. Thus, native Windows understands
> the name properly.

Because Cygwin converts UTF-8 into UTF-18, the so-called "Unicode
encoding" that is native to MS-Windows.  It's an illusion.

  • Gmake UTF... Jon Forrest
    • Re: ... Kaz Kylheku (gmake)
      • ... Eli Zaretskii
        • ... Kaz Kylheku (gmake)
          • ... Eli Zaretskii
            • ... Kaz Kylheku (gmake)
              • ... Eli Zaretskii
                • ... Jon Forrest
                • ... Kaz Kylheku (gmake)
                • ... Eli Zaretskii
                • ... Kaz Kylheku (gmake)
                • ... Eli Zaretskii
                • ... Stefan Monnier via Users list for the GNU implementation of make
                • ... Dan Kegel
                • ... Eli Zaretskii

Reply via email to