How can I get zsh to display international characters properly?











up vote
7
down vote

favorite
1












I just started using zsh, and love it. However, I've stumbled upon an annoyance when it comes to international characters:



➜  ~  touch åäö.txt               
➜ ~ ls
Desktop Dropbox Music Sites
Documents Library Pictures a??a??o??.txt
Downloads Movies Public
➜ ~ rm -v a<030a>a<0308>o<0308>.txt
åäö.txt
➜ ~


With bash it looks like this (the filename in rm -v is auto completed by pressing TAB in both cases).



johan@retina ~ $ touch åäö.txt
johan@retina ~ $ ls
Desktop Dropbox Music Sites
Documents Library Pictures åäö.txt
Downloads Movies Public
johan@retina ~ $ rm -v åäö.txt
åäö.txt
johan@retina ~ $


How can I fix this with zsh?



EDIT:



Setting export LANG=en_US:UTF-8 fixes the output of e.g. ls and also shows it properly on the line below current input when there are multiple matches on TAB-completion. However, selecting the file from TAB-completion it shows the wrong way on the input line, the same goes for when there is only one match.



The above example now looks like this with zsh:



➜  ~  touch åäö.txt               
➜ ~ ls
åäö.txy
➜ ~ rm -v a<030a>a<0308>o<0308>.txt
åäö.txt
➜ ~


If I have two files matching on TAB-completion it looks like this:



➜  ~  touch åäö.txt               
➜ ~ touch öäå.txt
➜ ~ rm
öäå.txt åäö.txt


Selecting one of the above by pressing TAB again and using arrow keys, or pressing either a or o to only make one match before completion generates this:



➜  ~  rm o<0308>a<0308>a<030a>.txt
➜ ~ rm a<030a>a<0308>o<0308>.txt


Any suggestions on what's wrong?










share|improve this question




















  • 2




    What's the output of echo $LANG in bash resp. zsh?
    – mpy
    Apr 15 '13 at 14:08










  • It's blank for both. I'm on OS X 10.8.3 by the way.
    – Morgan
    Apr 15 '13 at 14:30










  • Ok, then I'm out (OS X), sorry. But try nevertheless e.g. LANG=en_US.UTF-8. zsh should offer you all possibilities with LANG=<TAB>, but en_US.UTF-8 works perfect with german umlauts.
    – mpy
    Apr 15 '13 at 14:36










  • export LANG=en_US.UTF-8 fixed the ls output, however, the auto completion still shows a<030a>a<0308>o<0308>.txt
    – Morgan
    Apr 15 '13 at 14:47










  • Just another idea: Did you compile zsh yourself? If not, grab latest source (zsh.sourceforge.net/Arc/source.html) and be sure to use ./configure --enable-multibyte. After make just try by starting ./Src/zsh prior installing that version.
    – mpy
    Apr 15 '13 at 14:56















up vote
7
down vote

favorite
1












I just started using zsh, and love it. However, I've stumbled upon an annoyance when it comes to international characters:



➜  ~  touch åäö.txt               
➜ ~ ls
Desktop Dropbox Music Sites
Documents Library Pictures a??a??o??.txt
Downloads Movies Public
➜ ~ rm -v a<030a>a<0308>o<0308>.txt
åäö.txt
➜ ~


With bash it looks like this (the filename in rm -v is auto completed by pressing TAB in both cases).



johan@retina ~ $ touch åäö.txt
johan@retina ~ $ ls
Desktop Dropbox Music Sites
Documents Library Pictures åäö.txt
Downloads Movies Public
johan@retina ~ $ rm -v åäö.txt
åäö.txt
johan@retina ~ $


How can I fix this with zsh?



EDIT:



Setting export LANG=en_US:UTF-8 fixes the output of e.g. ls and also shows it properly on the line below current input when there are multiple matches on TAB-completion. However, selecting the file from TAB-completion it shows the wrong way on the input line, the same goes for when there is only one match.



The above example now looks like this with zsh:



➜  ~  touch åäö.txt               
➜ ~ ls
åäö.txy
➜ ~ rm -v a<030a>a<0308>o<0308>.txt
åäö.txt
➜ ~


If I have two files matching on TAB-completion it looks like this:



➜  ~  touch åäö.txt               
➜ ~ touch öäå.txt
➜ ~ rm
öäå.txt åäö.txt


Selecting one of the above by pressing TAB again and using arrow keys, or pressing either a or o to only make one match before completion generates this:



➜  ~  rm o<0308>a<0308>a<030a>.txt
➜ ~ rm a<030a>a<0308>o<0308>.txt


Any suggestions on what's wrong?










share|improve this question




















  • 2




    What's the output of echo $LANG in bash resp. zsh?
    – mpy
    Apr 15 '13 at 14:08










  • It's blank for both. I'm on OS X 10.8.3 by the way.
    – Morgan
    Apr 15 '13 at 14:30










  • Ok, then I'm out (OS X), sorry. But try nevertheless e.g. LANG=en_US.UTF-8. zsh should offer you all possibilities with LANG=<TAB>, but en_US.UTF-8 works perfect with german umlauts.
    – mpy
    Apr 15 '13 at 14:36










  • export LANG=en_US.UTF-8 fixed the ls output, however, the auto completion still shows a<030a>a<0308>o<0308>.txt
    – Morgan
    Apr 15 '13 at 14:47










  • Just another idea: Did you compile zsh yourself? If not, grab latest source (zsh.sourceforge.net/Arc/source.html) and be sure to use ./configure --enable-multibyte. After make just try by starting ./Src/zsh prior installing that version.
    – mpy
    Apr 15 '13 at 14:56













up vote
7
down vote

favorite
1









up vote
7
down vote

favorite
1






1





I just started using zsh, and love it. However, I've stumbled upon an annoyance when it comes to international characters:



➜  ~  touch åäö.txt               
➜ ~ ls
Desktop Dropbox Music Sites
Documents Library Pictures a??a??o??.txt
Downloads Movies Public
➜ ~ rm -v a<030a>a<0308>o<0308>.txt
åäö.txt
➜ ~


With bash it looks like this (the filename in rm -v is auto completed by pressing TAB in both cases).



johan@retina ~ $ touch åäö.txt
johan@retina ~ $ ls
Desktop Dropbox Music Sites
Documents Library Pictures åäö.txt
Downloads Movies Public
johan@retina ~ $ rm -v åäö.txt
åäö.txt
johan@retina ~ $


How can I fix this with zsh?



EDIT:



Setting export LANG=en_US:UTF-8 fixes the output of e.g. ls and also shows it properly on the line below current input when there are multiple matches on TAB-completion. However, selecting the file from TAB-completion it shows the wrong way on the input line, the same goes for when there is only one match.



The above example now looks like this with zsh:



➜  ~  touch åäö.txt               
➜ ~ ls
åäö.txy
➜ ~ rm -v a<030a>a<0308>o<0308>.txt
åäö.txt
➜ ~


If I have two files matching on TAB-completion it looks like this:



➜  ~  touch åäö.txt               
➜ ~ touch öäå.txt
➜ ~ rm
öäå.txt åäö.txt


Selecting one of the above by pressing TAB again and using arrow keys, or pressing either a or o to only make one match before completion generates this:



➜  ~  rm o<0308>a<0308>a<030a>.txt
➜ ~ rm a<030a>a<0308>o<0308>.txt


Any suggestions on what's wrong?










share|improve this question















I just started using zsh, and love it. However, I've stumbled upon an annoyance when it comes to international characters:



➜  ~  touch åäö.txt               
➜ ~ ls
Desktop Dropbox Music Sites
Documents Library Pictures a??a??o??.txt
Downloads Movies Public
➜ ~ rm -v a<030a>a<0308>o<0308>.txt
åäö.txt
➜ ~


With bash it looks like this (the filename in rm -v is auto completed by pressing TAB in both cases).



johan@retina ~ $ touch åäö.txt
johan@retina ~ $ ls
Desktop Dropbox Music Sites
Documents Library Pictures åäö.txt
Downloads Movies Public
johan@retina ~ $ rm -v åäö.txt
åäö.txt
johan@retina ~ $


How can I fix this with zsh?



EDIT:



Setting export LANG=en_US:UTF-8 fixes the output of e.g. ls and also shows it properly on the line below current input when there are multiple matches on TAB-completion. However, selecting the file from TAB-completion it shows the wrong way on the input line, the same goes for when there is only one match.



The above example now looks like this with zsh:



➜  ~  touch åäö.txt               
➜ ~ ls
åäö.txy
➜ ~ rm -v a<030a>a<0308>o<0308>.txt
åäö.txt
➜ ~


If I have two files matching on TAB-completion it looks like this:



➜  ~  touch åäö.txt               
➜ ~ touch öäå.txt
➜ ~ rm
öäå.txt åäö.txt


Selecting one of the above by pressing TAB again and using arrow keys, or pressing either a or o to only make one match before completion generates this:



➜  ~  rm o<0308>a<0308>a<030a>.txt
➜ ~ rm a<030a>a<0308>o<0308>.txt


Any suggestions on what's wrong?







macos bash zsh utf-8 international






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Apr 18 '13 at 6:49

























asked Apr 15 '13 at 12:08









Morgan

326159




326159








  • 2




    What's the output of echo $LANG in bash resp. zsh?
    – mpy
    Apr 15 '13 at 14:08










  • It's blank for both. I'm on OS X 10.8.3 by the way.
    – Morgan
    Apr 15 '13 at 14:30










  • Ok, then I'm out (OS X), sorry. But try nevertheless e.g. LANG=en_US.UTF-8. zsh should offer you all possibilities with LANG=<TAB>, but en_US.UTF-8 works perfect with german umlauts.
    – mpy
    Apr 15 '13 at 14:36










  • export LANG=en_US.UTF-8 fixed the ls output, however, the auto completion still shows a<030a>a<0308>o<0308>.txt
    – Morgan
    Apr 15 '13 at 14:47










  • Just another idea: Did you compile zsh yourself? If not, grab latest source (zsh.sourceforge.net/Arc/source.html) and be sure to use ./configure --enable-multibyte. After make just try by starting ./Src/zsh prior installing that version.
    – mpy
    Apr 15 '13 at 14:56














  • 2




    What's the output of echo $LANG in bash resp. zsh?
    – mpy
    Apr 15 '13 at 14:08










  • It's blank for both. I'm on OS X 10.8.3 by the way.
    – Morgan
    Apr 15 '13 at 14:30










  • Ok, then I'm out (OS X), sorry. But try nevertheless e.g. LANG=en_US.UTF-8. zsh should offer you all possibilities with LANG=<TAB>, but en_US.UTF-8 works perfect with german umlauts.
    – mpy
    Apr 15 '13 at 14:36










  • export LANG=en_US.UTF-8 fixed the ls output, however, the auto completion still shows a<030a>a<0308>o<0308>.txt
    – Morgan
    Apr 15 '13 at 14:47










  • Just another idea: Did you compile zsh yourself? If not, grab latest source (zsh.sourceforge.net/Arc/source.html) and be sure to use ./configure --enable-multibyte. After make just try by starting ./Src/zsh prior installing that version.
    – mpy
    Apr 15 '13 at 14:56








2




2




What's the output of echo $LANG in bash resp. zsh?
– mpy
Apr 15 '13 at 14:08




What's the output of echo $LANG in bash resp. zsh?
– mpy
Apr 15 '13 at 14:08












It's blank for both. I'm on OS X 10.8.3 by the way.
– Morgan
Apr 15 '13 at 14:30




It's blank for both. I'm on OS X 10.8.3 by the way.
– Morgan
Apr 15 '13 at 14:30












Ok, then I'm out (OS X), sorry. But try nevertheless e.g. LANG=en_US.UTF-8. zsh should offer you all possibilities with LANG=<TAB>, but en_US.UTF-8 works perfect with german umlauts.
– mpy
Apr 15 '13 at 14:36




Ok, then I'm out (OS X), sorry. But try nevertheless e.g. LANG=en_US.UTF-8. zsh should offer you all possibilities with LANG=<TAB>, but en_US.UTF-8 works perfect with german umlauts.
– mpy
Apr 15 '13 at 14:36












export LANG=en_US.UTF-8 fixed the ls output, however, the auto completion still shows a<030a>a<0308>o<0308>.txt
– Morgan
Apr 15 '13 at 14:47




export LANG=en_US.UTF-8 fixed the ls output, however, the auto completion still shows a<030a>a<0308>o<0308>.txt
– Morgan
Apr 15 '13 at 14:47












Just another idea: Did you compile zsh yourself? If not, grab latest source (zsh.sourceforge.net/Arc/source.html) and be sure to use ./configure --enable-multibyte. After make just try by starting ./Src/zsh prior installing that version.
– mpy
Apr 15 '13 at 14:56




Just another idea: Did you compile zsh yourself? If not, grab latest source (zsh.sourceforge.net/Arc/source.html) and be sure to use ./configure --enable-multibyte. After make just try by starting ./Src/zsh prior installing that version.
– mpy
Apr 15 '13 at 14:56










4 Answers
4






active

oldest

votes

















up vote
3
down vote













Thanks @mpy for solving the LANG problem. The answer is to use:



export LANG=en_US.UTF-8


in your .zshrc.



The remaining problem is caused by the completion system. Unfortunately completion is a monster feature. It involves shell functions or perhaps even scripts being called and somewhere in that process possibly LANG is again set to a wrong value. If you have root privileges you can debug this shell script code). Good luck with the
completion guide.






share|improve this answer






























    up vote
    0
    down vote













    The problem is still the same on the last versions of zsh which come
    with Mac OS X 10.8 (aka Mountain Lion), 10.9 (aka Mavericks) & 10.10 (aka Yosemite) (I am still beta testing 10.11 and can't disclose information about it).
    The completion of zsh is failing.



    The port version is working correctly at least with version 5.1.1:



    /usr/bin/sudo port install zsh


    Test:



    /opt/local/bin/zsh


    % touch hølé
    % ls -l htab

    → ls -l hølé

    % -rw-r--r-- 1 bob wheel 0 Apr 2 18:49 hølé

    %






    share|improve this answer




























      up vote
      0
      down vote













      I had the same problem in Arch Linux using zsh.



      Using bash everything works just fine, but when I switch to zsh some characters were displayed wrong (e.g. ñ,°).



      I've added export LANG="en_US.UTF-8" to my .zshrc and nothing happened.



      I did everything to set LANG inside zsh and nothing fixes.



      Then I changed my shell back to bash with chsh -s /bin/bash and I noticed my env var LANG was wrong with printenv LANG it showed me LANG=C.



      This is a new installation so I forget to create /etc/locale.conf file and set my LANG="en_US.UTF-8" and after restarting everything work perfect.



      Hope this helps.






      share|improve this answer




























        up vote
        0
        down vote













        Try




        1. Having a Powerline compatible font installed https://github.com/powerline/fonts

        2. Setting these ENV vars in .zshrc:



        LANG="en_US.UTF-8"
        LC_COLLATE="en_US.UTF-8"
        LC_CTYPE="en_US.UTF-8"
        LC_MESSAGES="en_US.UTF-8"
        LC_MONETARY="en_US.UTF-8"
        LC_NUMERIC="en_US.UTF-8"
        LC_TIME="en_US.UTF-8"
        LC_ALL="en_US.UTF-8"





        share|improve this answer





















          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "3"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f583031%2fhow-can-i-get-zsh-to-display-international-characters-properly%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          4 Answers
          4






          active

          oldest

          votes








          4 Answers
          4






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          3
          down vote













          Thanks @mpy for solving the LANG problem. The answer is to use:



          export LANG=en_US.UTF-8


          in your .zshrc.



          The remaining problem is caused by the completion system. Unfortunately completion is a monster feature. It involves shell functions or perhaps even scripts being called and somewhere in that process possibly LANG is again set to a wrong value. If you have root privileges you can debug this shell script code). Good luck with the
          completion guide.






          share|improve this answer



























            up vote
            3
            down vote













            Thanks @mpy for solving the LANG problem. The answer is to use:



            export LANG=en_US.UTF-8


            in your .zshrc.



            The remaining problem is caused by the completion system. Unfortunately completion is a monster feature. It involves shell functions or perhaps even scripts being called and somewhere in that process possibly LANG is again set to a wrong value. If you have root privileges you can debug this shell script code). Good luck with the
            completion guide.






            share|improve this answer

























              up vote
              3
              down vote










              up vote
              3
              down vote









              Thanks @mpy for solving the LANG problem. The answer is to use:



              export LANG=en_US.UTF-8


              in your .zshrc.



              The remaining problem is caused by the completion system. Unfortunately completion is a monster feature. It involves shell functions or perhaps even scripts being called and somewhere in that process possibly LANG is again set to a wrong value. If you have root privileges you can debug this shell script code). Good luck with the
              completion guide.






              share|improve this answer














              Thanks @mpy for solving the LANG problem. The answer is to use:



              export LANG=en_US.UTF-8


              in your .zshrc.



              The remaining problem is caused by the completion system. Unfortunately completion is a monster feature. It involves shell functions or perhaps even scripts being called and somewhere in that process possibly LANG is again set to a wrong value. If you have root privileges you can debug this shell script code). Good luck with the
              completion guide.







              share|improve this answer














              share|improve this answer



              share|improve this answer








              edited Dec 6 '14 at 18:18









              slhck

              158k47437461




              158k47437461










              answered Jun 23 '13 at 17:34









              user829755

              322211




              322211
























                  up vote
                  0
                  down vote













                  The problem is still the same on the last versions of zsh which come
                  with Mac OS X 10.8 (aka Mountain Lion), 10.9 (aka Mavericks) & 10.10 (aka Yosemite) (I am still beta testing 10.11 and can't disclose information about it).
                  The completion of zsh is failing.



                  The port version is working correctly at least with version 5.1.1:



                  /usr/bin/sudo port install zsh


                  Test:



                  /opt/local/bin/zsh


                  % touch hølé
                  % ls -l htab

                  → ls -l hølé

                  % -rw-r--r-- 1 bob wheel 0 Apr 2 18:49 hølé

                  %






                  share|improve this answer

























                    up vote
                    0
                    down vote













                    The problem is still the same on the last versions of zsh which come
                    with Mac OS X 10.8 (aka Mountain Lion), 10.9 (aka Mavericks) & 10.10 (aka Yosemite) (I am still beta testing 10.11 and can't disclose information about it).
                    The completion of zsh is failing.



                    The port version is working correctly at least with version 5.1.1:



                    /usr/bin/sudo port install zsh


                    Test:



                    /opt/local/bin/zsh


                    % touch hølé
                    % ls -l htab

                    → ls -l hølé

                    % -rw-r--r-- 1 bob wheel 0 Apr 2 18:49 hølé

                    %






                    share|improve this answer























                      up vote
                      0
                      down vote










                      up vote
                      0
                      down vote









                      The problem is still the same on the last versions of zsh which come
                      with Mac OS X 10.8 (aka Mountain Lion), 10.9 (aka Mavericks) & 10.10 (aka Yosemite) (I am still beta testing 10.11 and can't disclose information about it).
                      The completion of zsh is failing.



                      The port version is working correctly at least with version 5.1.1:



                      /usr/bin/sudo port install zsh


                      Test:



                      /opt/local/bin/zsh


                      % touch hølé
                      % ls -l htab

                      → ls -l hølé

                      % -rw-r--r-- 1 bob wheel 0 Apr 2 18:49 hølé

                      %






                      share|improve this answer












                      The problem is still the same on the last versions of zsh which come
                      with Mac OS X 10.8 (aka Mountain Lion), 10.9 (aka Mavericks) & 10.10 (aka Yosemite) (I am still beta testing 10.11 and can't disclose information about it).
                      The completion of zsh is failing.



                      The port version is working correctly at least with version 5.1.1:



                      /usr/bin/sudo port install zsh


                      Test:



                      /opt/local/bin/zsh


                      % touch hølé
                      % ls -l htab

                      → ls -l hølé

                      % -rw-r--r-- 1 bob wheel 0 Apr 2 18:49 hølé

                      %







                      share|improve this answer












                      share|improve this answer



                      share|improve this answer










                      answered Apr 2 '16 at 17:00









                      daniel Azuelos

                      237111




                      237111






















                          up vote
                          0
                          down vote













                          I had the same problem in Arch Linux using zsh.



                          Using bash everything works just fine, but when I switch to zsh some characters were displayed wrong (e.g. ñ,°).



                          I've added export LANG="en_US.UTF-8" to my .zshrc and nothing happened.



                          I did everything to set LANG inside zsh and nothing fixes.



                          Then I changed my shell back to bash with chsh -s /bin/bash and I noticed my env var LANG was wrong with printenv LANG it showed me LANG=C.



                          This is a new installation so I forget to create /etc/locale.conf file and set my LANG="en_US.UTF-8" and after restarting everything work perfect.



                          Hope this helps.






                          share|improve this answer

























                            up vote
                            0
                            down vote













                            I had the same problem in Arch Linux using zsh.



                            Using bash everything works just fine, but when I switch to zsh some characters were displayed wrong (e.g. ñ,°).



                            I've added export LANG="en_US.UTF-8" to my .zshrc and nothing happened.



                            I did everything to set LANG inside zsh and nothing fixes.



                            Then I changed my shell back to bash with chsh -s /bin/bash and I noticed my env var LANG was wrong with printenv LANG it showed me LANG=C.



                            This is a new installation so I forget to create /etc/locale.conf file and set my LANG="en_US.UTF-8" and after restarting everything work perfect.



                            Hope this helps.






                            share|improve this answer























                              up vote
                              0
                              down vote










                              up vote
                              0
                              down vote









                              I had the same problem in Arch Linux using zsh.



                              Using bash everything works just fine, but when I switch to zsh some characters were displayed wrong (e.g. ñ,°).



                              I've added export LANG="en_US.UTF-8" to my .zshrc and nothing happened.



                              I did everything to set LANG inside zsh and nothing fixes.



                              Then I changed my shell back to bash with chsh -s /bin/bash and I noticed my env var LANG was wrong with printenv LANG it showed me LANG=C.



                              This is a new installation so I forget to create /etc/locale.conf file and set my LANG="en_US.UTF-8" and after restarting everything work perfect.



                              Hope this helps.






                              share|improve this answer












                              I had the same problem in Arch Linux using zsh.



                              Using bash everything works just fine, but when I switch to zsh some characters were displayed wrong (e.g. ñ,°).



                              I've added export LANG="en_US.UTF-8" to my .zshrc and nothing happened.



                              I did everything to set LANG inside zsh and nothing fixes.



                              Then I changed my shell back to bash with chsh -s /bin/bash and I noticed my env var LANG was wrong with printenv LANG it showed me LANG=C.



                              This is a new installation so I forget to create /etc/locale.conf file and set my LANG="en_US.UTF-8" and after restarting everything work perfect.



                              Hope this helps.







                              share|improve this answer












                              share|improve this answer



                              share|improve this answer










                              answered Jun 26 '16 at 14:07









                              Hernan Daniel Garcia Sifontes

                              12




                              12






















                                  up vote
                                  0
                                  down vote













                                  Try




                                  1. Having a Powerline compatible font installed https://github.com/powerline/fonts

                                  2. Setting these ENV vars in .zshrc:



                                  LANG="en_US.UTF-8"
                                  LC_COLLATE="en_US.UTF-8"
                                  LC_CTYPE="en_US.UTF-8"
                                  LC_MESSAGES="en_US.UTF-8"
                                  LC_MONETARY="en_US.UTF-8"
                                  LC_NUMERIC="en_US.UTF-8"
                                  LC_TIME="en_US.UTF-8"
                                  LC_ALL="en_US.UTF-8"





                                  share|improve this answer

























                                    up vote
                                    0
                                    down vote













                                    Try




                                    1. Having a Powerline compatible font installed https://github.com/powerline/fonts

                                    2. Setting these ENV vars in .zshrc:



                                    LANG="en_US.UTF-8"
                                    LC_COLLATE="en_US.UTF-8"
                                    LC_CTYPE="en_US.UTF-8"
                                    LC_MESSAGES="en_US.UTF-8"
                                    LC_MONETARY="en_US.UTF-8"
                                    LC_NUMERIC="en_US.UTF-8"
                                    LC_TIME="en_US.UTF-8"
                                    LC_ALL="en_US.UTF-8"





                                    share|improve this answer























                                      up vote
                                      0
                                      down vote










                                      up vote
                                      0
                                      down vote









                                      Try




                                      1. Having a Powerline compatible font installed https://github.com/powerline/fonts

                                      2. Setting these ENV vars in .zshrc:



                                      LANG="en_US.UTF-8"
                                      LC_COLLATE="en_US.UTF-8"
                                      LC_CTYPE="en_US.UTF-8"
                                      LC_MESSAGES="en_US.UTF-8"
                                      LC_MONETARY="en_US.UTF-8"
                                      LC_NUMERIC="en_US.UTF-8"
                                      LC_TIME="en_US.UTF-8"
                                      LC_ALL="en_US.UTF-8"





                                      share|improve this answer












                                      Try




                                      1. Having a Powerline compatible font installed https://github.com/powerline/fonts

                                      2. Setting these ENV vars in .zshrc:



                                      LANG="en_US.UTF-8"
                                      LC_COLLATE="en_US.UTF-8"
                                      LC_CTYPE="en_US.UTF-8"
                                      LC_MESSAGES="en_US.UTF-8"
                                      LC_MONETARY="en_US.UTF-8"
                                      LC_NUMERIC="en_US.UTF-8"
                                      LC_TIME="en_US.UTF-8"
                                      LC_ALL="en_US.UTF-8"






                                      share|improve this answer












                                      share|improve this answer



                                      share|improve this answer










                                      answered Nov 24 at 11:36









                                      Dmitriy

                                      1013




                                      1013






























                                          draft saved

                                          draft discarded




















































                                          Thanks for contributing an answer to Super User!


                                          • Please be sure to answer the question. Provide details and share your research!

                                          But avoid



                                          • Asking for help, clarification, or responding to other answers.

                                          • Making statements based on opinion; back them up with references or personal experience.


                                          To learn more, see our tips on writing great answers.





                                          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                                          Please pay close attention to the following guidance:


                                          • Please be sure to answer the question. Provide details and share your research!

                                          But avoid



                                          • Asking for help, clarification, or responding to other answers.

                                          • Making statements based on opinion; back them up with references or personal experience.


                                          To learn more, see our tips on writing great answers.




                                          draft saved


                                          draft discarded














                                          StackExchange.ready(
                                          function () {
                                          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f583031%2fhow-can-i-get-zsh-to-display-international-characters-properly%23new-answer', 'question_page');
                                          }
                                          );

                                          Post as a guest















                                          Required, but never shown





















































                                          Required, but never shown














                                          Required, but never shown












                                          Required, but never shown







                                          Required, but never shown

































                                          Required, but never shown














                                          Required, but never shown












                                          Required, but never shown







                                          Required, but never shown







                                          Popular posts from this blog

                                          Список кардиналов, возведённых папой римским Каликстом III

                                          Deduzione

                                          Mysql.sock missing - “Can't connect to local MySQL server through socket”