|
From: | Auto mailings of changes to Lily Issues via Testlilyissues-auto |
Subject: | [Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #2173 Deal with file names not encoded in UTF-8 |
Date: | Sat, 01 Feb 2020 07:48:04 -0000 |
Add Unicode filename support for Windows 10 1903+
On Windows 10 1903 and above, -A APIs support UTF-8 encodings.
This commit enables it by adding an application manifest.
https://docs.microsoft.com/en-us/windows/uwp/design/globalizing/use-utf8-code-page
If you use older Windows,
it has no effect and the behavior is the same as before.
For Cygwin environments, UTF-8 can be used originally,
so this commit doesn't add the application manifest.
http://codereview.appspot.com/575600044
[issues:#2173] Deal with file names not encoded in UTF-8
Status: Started
Created: Mon Jan 02, 2012 11:32 AM UTC by Anonymous
Last Updated: Sat Feb 01, 2020 07:44 AM UTC
Owner: nobody
Originally created by: *anonymous
Originally created by: address@hidden
<http://permalink.gmane.org/gmane.comp.gnu.lilypond.devel/43243>
Lilypond talks utf-8. If the operating system decides to talk something else on its command line or its file names, appropriate conversions need to be put in place whenever Lilypond displays or generates a file name.
This apparently concerns Windows and likely also other systems.
Sent from sourceforge.net because address@hidden is subscribed to https://sourceforge.net/p/testlilyissues/issues/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
_______________________________________________ Testlilyissues-auto mailing list address@hidden https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Prev in Thread] | Current Thread | [Next in Thread] |