To improve Windows Server I suggest you ...

Add locales that use UTF8 (Code Page 65001) by default

Most modern Unix-based OSes make UTF-8 the default character encoding.
Considering OpenSSH ( http://blogs.msdn.com/b/powershell/archive/2015/10/19/openssh-for-windows-update.aspx ), Now is the time for Windows to support UTF8-native locales. we need system-wide and reboot-trelant way.

55 votes
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)

    We’ll send you updates on this idea

    INOMATA Kentaro shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    2 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • knjname commented  ·   ·  Flag as inappropriate

        I totally agree with this idea.
        It's very cumbersome to find code snippet or another way to put texts in UTF-8.
        Everyone might have experienced it in PowerShell.
        Who wants minor encodings today.

      • Takekazu Omi commented  ·   ·  Flag as inappropriate

        I also agree that Windows use to the default console encoding is UTF-8.
        Console means powershell.exe, cmd.exe.
        And I want you to remove the BOM file.

      Feedback and Knowledge Base