Most active commenters

    ←back to thread

    PEP 686 – Make UTF-8 mode default

    (peps.python.org)
    238 points GalaxySnail | 14 comments | 26 Apr 24 11:55 UTC | HN request time: 0.493s | source | bottom
    1. Affric ◴[26 Apr 24 13:10 UTC] No.40169026[source]▶
    Make UTF-8 default on Windows
    replies(6): >>40169144 #>>40169474 #>>40170343 #>>40171178 #>>40173598 #>>40175253 #
    2. johannes1234321 ◴[26 Apr 24 13:30 UTC] No.40169144[source]▶
    Since Windows Version 1903 (May 2019 Update) they push for Utf-8. But Windows is a big pile of compatible legacy.
    3. tedivm ◴[26 Apr 24 13:58 UTC] No.40169474[source]▶
    That's exactly what this proposal (which has been accepted) is going to do.
    replies(1): >>40169524 #
    4. lolinder ◴[26 Apr 24 14:01 UTC] No.40169524[source]▶
    I think they mean that the Windows operating system should default to UTF-8.
    5. pjc50 ◴[26 Apr 24 15:07 UTC] No.40170343[source]▶
    In addition to ApiFunctionA and ApiFunctionW, introduce ApiFunction8? (times whole API surface)

    Introduce a #define UNICODE_NO_REALLY_ALL_UNICODE_WE_MEAN_IT_THIS_TIME ?

    replies(1): >>40170814 #
    6. cryptonector ◴[26 Apr 24 15:40 UTC] No.40170814[source]▶
    ApiFunctionA is UTF-8 capable. Needs a run-time switch too, not just compile-time.
    replies(3): >>40170987 #>>40173012 #>>40174417 #
    7. garaetjjte ◴[26 Apr 24 15:52 UTC] No.40170987{3}[source]▶
    It's now possible, but for years the excuse was that MBCS encodings only supported characters up to 2 bytes.
    8. layer8 ◴[26 Apr 24 16:20 UTC] No.40171178[source]▶
    That would break so many applications and workflows that it will never happen.
    9. ComputerGuru ◴[26 Apr 24 19:22 UTC] No.40173012{3}[source]▶
    Only under windows 11, I believe. And that switch is off by default.
    replies(1): >>40174609 #
    10. ◴[26 Apr 24 20:05 UTC] No.40173598[source]▶
    11. sebazzz ◴[26 Apr 24 21:17 UTC] No.40174417{3}[source]▶
    Yes: https://learn.microsoft.com/en-us/windows/win32/sbscs/applic...

    > On Windows 10, this element forces a process to use UTF-8 as the process code page. For more information, see Use the UTF-8 code page. On Windows 10, the only valid value for activeCodePage is UTF-8.

    > This element was first added in Windows 10 version 1903 (May 2019 Update). You can declare this property and target/run on earlier Windows builds, but you must handle legacy code page detection and conversion as usual. This element has no attributes.

    12. int_19h ◴[26 Apr 24 21:38 UTC] No.40174609{4}[source]▶
    You're thinking of the global setting that is enabled by the user and applies to all apps that operate in terms of "current code page" - if enabled, that codepage becomes 65001 (UTF-8).

    However, on Win10+, apps themselves can explicitly opt into UTF-8 for all non-widechar Win32 APIs regardless of the current locale/codepage.

    13. numpad0 ◴[26 Apr 24 22:58 UTC] No.40175253[source]▶
    lots of apps can't even handle non-ASCII username on Windows
    replies(1): >>40176779 #
    14. Affric ◴[27 Apr 24 03:07 UTC] No.40176779[source]▶
    I have seen the worst of it.

    Too many companies running franken-software from decades ago.