Peter Laursen

My feedback

  1. 766 votes
    Sign in
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)

      We’ll send you updates on this idea

      As Chip said, UTF-16 is rather baked into the stuff we do. The console host does use UTF-16 somewhere in there. :P We just have the matter of dealing with code pages throughout the history of computing existence that causes us heartburn every time we think about how to fix this. :( It’s definitely something that we would like to look into on our backlog.


      Peter Laursen commented  · 

      I can use chcp 65001

      .. BUT I cannot find a font that works properly in cmd/bash. "Lucida console" is often recommended but does not work with Chinese, Arabic and more. I tried a few TT fonts including Courier New. But the console does not work well withaccented etc. TT fonts in t

      See this MySQL result set in SQLyog (a MySQL GUI client) in WIndows

      id english native
      ------ -------- --------------------------
      1 danish dansk
      2 russisk ру́сский
      3 turkish Türkçe
      4 mandarin 官話
      7 arabic العَرَبِيَّة

      (the font I use in this program is Courier new and it works here as you see)

      .. but lots of display issues in "cmd" with any font (no matter if If I run the 'mysql' client for Windows or the Lnux build in 'bash' it will not display correctly with any font even if I use "chcp 65001").

      Bash is UTF8 natively and the windows console should work with that. Neither "cmd" nor "Powershell" does. This exposes the primitiveness of "cmd" (and "Powershell" too in this respect)

      It may be enough to improve the "Lucida Console" font with more languages' support. I believe it is a font problem in the console(s) only. The byte-sequences are probably correct but what does it help if it cannot be displayed?

      Peter Laursen supported this idea  · 

    Feedback and Knowledge Base