Locale installation and setting on Fedora have no effect

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
2
down vote

favorite












I was trying to install Chinese language support for a Fedora 26 Server hosted on Digital Ocean, multiple steps have been taken but I still couldn't get it right.



The language and charset I was trying to install is zh_CN.UTF-8



Solutions taken so far:



  • Setting %_install_langs all (which was previously %_install_langs C:en:en_US:en_US.UTF-8 as the cloud provider default) in /etc/rpm/macros.image-language-conf, and then $ dnf reinstall glibc-common, according to this Super User post linux - How do I install/generate all locales on Fedora?.


  • Installing langpacks-zh_CN using $ dnf install langpacks-zh_CN.


  • Installing glibc-langpack-zh and man-pages-zh-CN, both of which are weak dependencies of langpacks-zh_CN, and somehow the latter is not installed when installing langpacks-zh_CN.


  • Setting LANG=zh_CN.UTF-8 and LC_ALL=zh_CN.UTF-8 in /etc/locale.conf.


  • Setting export LANG=zh_CN.UTF-8 and export LC_ALL=zh_CN.UTF-8 in ~/.bashrc.


What have been different:



  • When using $ date, the prompt is now in correct language as 2017å¹´ 10月 20日 星期五 18:31:34 UTC.


  • However, anything else is still English, including man prompts, dnf prompts, nano prompts, etc.


  • But the same commands work perfectly well on a local Fedora Server VM.


Noticed situation: (but not sure if there are right or how to solve)



  • I found/usr/share/locale/zh_CN/LC_MESSAGES has fewer files in comparison with the VM on my Mac. While the VM on my Mac has tens of files in the folder (the translation project has been there for years), the cloud remote Droplet has only 1, and that is libc.mo.






share|improve this question


























    up vote
    2
    down vote

    favorite












    I was trying to install Chinese language support for a Fedora 26 Server hosted on Digital Ocean, multiple steps have been taken but I still couldn't get it right.



    The language and charset I was trying to install is zh_CN.UTF-8



    Solutions taken so far:



    • Setting %_install_langs all (which was previously %_install_langs C:en:en_US:en_US.UTF-8 as the cloud provider default) in /etc/rpm/macros.image-language-conf, and then $ dnf reinstall glibc-common, according to this Super User post linux - How do I install/generate all locales on Fedora?.


    • Installing langpacks-zh_CN using $ dnf install langpacks-zh_CN.


    • Installing glibc-langpack-zh and man-pages-zh-CN, both of which are weak dependencies of langpacks-zh_CN, and somehow the latter is not installed when installing langpacks-zh_CN.


    • Setting LANG=zh_CN.UTF-8 and LC_ALL=zh_CN.UTF-8 in /etc/locale.conf.


    • Setting export LANG=zh_CN.UTF-8 and export LC_ALL=zh_CN.UTF-8 in ~/.bashrc.


    What have been different:



    • When using $ date, the prompt is now in correct language as 2017å¹´ 10月 20日 星期五 18:31:34 UTC.


    • However, anything else is still English, including man prompts, dnf prompts, nano prompts, etc.


    • But the same commands work perfectly well on a local Fedora Server VM.


    Noticed situation: (but not sure if there are right or how to solve)



    • I found/usr/share/locale/zh_CN/LC_MESSAGES has fewer files in comparison with the VM on my Mac. While the VM on my Mac has tens of files in the folder (the translation project has been there for years), the cloud remote Droplet has only 1, and that is libc.mo.






    share|improve this question
























      up vote
      2
      down vote

      favorite









      up vote
      2
      down vote

      favorite











      I was trying to install Chinese language support for a Fedora 26 Server hosted on Digital Ocean, multiple steps have been taken but I still couldn't get it right.



      The language and charset I was trying to install is zh_CN.UTF-8



      Solutions taken so far:



      • Setting %_install_langs all (which was previously %_install_langs C:en:en_US:en_US.UTF-8 as the cloud provider default) in /etc/rpm/macros.image-language-conf, and then $ dnf reinstall glibc-common, according to this Super User post linux - How do I install/generate all locales on Fedora?.


      • Installing langpacks-zh_CN using $ dnf install langpacks-zh_CN.


      • Installing glibc-langpack-zh and man-pages-zh-CN, both of which are weak dependencies of langpacks-zh_CN, and somehow the latter is not installed when installing langpacks-zh_CN.


      • Setting LANG=zh_CN.UTF-8 and LC_ALL=zh_CN.UTF-8 in /etc/locale.conf.


      • Setting export LANG=zh_CN.UTF-8 and export LC_ALL=zh_CN.UTF-8 in ~/.bashrc.


      What have been different:



      • When using $ date, the prompt is now in correct language as 2017å¹´ 10月 20日 星期五 18:31:34 UTC.


      • However, anything else is still English, including man prompts, dnf prompts, nano prompts, etc.


      • But the same commands work perfectly well on a local Fedora Server VM.


      Noticed situation: (but not sure if there are right or how to solve)



      • I found/usr/share/locale/zh_CN/LC_MESSAGES has fewer files in comparison with the VM on my Mac. While the VM on my Mac has tens of files in the folder (the translation project has been there for years), the cloud remote Droplet has only 1, and that is libc.mo.






      share|improve this question














      I was trying to install Chinese language support for a Fedora 26 Server hosted on Digital Ocean, multiple steps have been taken but I still couldn't get it right.



      The language and charset I was trying to install is zh_CN.UTF-8



      Solutions taken so far:



      • Setting %_install_langs all (which was previously %_install_langs C:en:en_US:en_US.UTF-8 as the cloud provider default) in /etc/rpm/macros.image-language-conf, and then $ dnf reinstall glibc-common, according to this Super User post linux - How do I install/generate all locales on Fedora?.


      • Installing langpacks-zh_CN using $ dnf install langpacks-zh_CN.


      • Installing glibc-langpack-zh and man-pages-zh-CN, both of which are weak dependencies of langpacks-zh_CN, and somehow the latter is not installed when installing langpacks-zh_CN.


      • Setting LANG=zh_CN.UTF-8 and LC_ALL=zh_CN.UTF-8 in /etc/locale.conf.


      • Setting export LANG=zh_CN.UTF-8 and export LC_ALL=zh_CN.UTF-8 in ~/.bashrc.


      What have been different:



      • When using $ date, the prompt is now in correct language as 2017å¹´ 10月 20日 星期五 18:31:34 UTC.


      • However, anything else is still English, including man prompts, dnf prompts, nano prompts, etc.


      • But the same commands work perfectly well on a local Fedora Server VM.


      Noticed situation: (but not sure if there are right or how to solve)



      • I found/usr/share/locale/zh_CN/LC_MESSAGES has fewer files in comparison with the VM on my Mac. While the VM on my Mac has tens of files in the folder (the translation project has been there for years), the cloud remote Droplet has only 1, and that is libc.mo.








      share|improve this question













      share|improve this question




      share|improve this question








      edited Dec 27 '17 at 12:11

























      asked Oct 20 '17 at 19:03









      jackxujh

      162212




      162212




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          1
          down vote



          accepted










          After changing the settings as you have, you'll need to dnf reinstall any packages which are missing translations (not everything uses the langpacks feature yet). For example:



          dnf reinstall dnf


          and then you'll have translations for DNF. Repeat this for any other packages which are missing translations.



          This will also happen as bugfix and security updates come in for the packages, and of course any new packages which come in after you've made the config change will bring translations along.






          share|improve this answer






















          • Wow! That was mind-blowning! Definitely didn't think of reinstalling dnf! And Chinese now works of dnf!
            – jackxujh
            Oct 21 '17 at 14:30










          Your Answer







          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "106"
          ;
          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: false,
          noModals: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













           

          draft saved


          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f399412%2flocale-installation-and-setting-on-fedora-have-no-effect%23new-answer', 'question_page');

          );

          Post as a guest






























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          1
          down vote



          accepted










          After changing the settings as you have, you'll need to dnf reinstall any packages which are missing translations (not everything uses the langpacks feature yet). For example:



          dnf reinstall dnf


          and then you'll have translations for DNF. Repeat this for any other packages which are missing translations.



          This will also happen as bugfix and security updates come in for the packages, and of course any new packages which come in after you've made the config change will bring translations along.






          share|improve this answer






















          • Wow! That was mind-blowning! Definitely didn't think of reinstalling dnf! And Chinese now works of dnf!
            – jackxujh
            Oct 21 '17 at 14:30














          up vote
          1
          down vote



          accepted










          After changing the settings as you have, you'll need to dnf reinstall any packages which are missing translations (not everything uses the langpacks feature yet). For example:



          dnf reinstall dnf


          and then you'll have translations for DNF. Repeat this for any other packages which are missing translations.



          This will also happen as bugfix and security updates come in for the packages, and of course any new packages which come in after you've made the config change will bring translations along.






          share|improve this answer






















          • Wow! That was mind-blowning! Definitely didn't think of reinstalling dnf! And Chinese now works of dnf!
            – jackxujh
            Oct 21 '17 at 14:30












          up vote
          1
          down vote



          accepted







          up vote
          1
          down vote



          accepted






          After changing the settings as you have, you'll need to dnf reinstall any packages which are missing translations (not everything uses the langpacks feature yet). For example:



          dnf reinstall dnf


          and then you'll have translations for DNF. Repeat this for any other packages which are missing translations.



          This will also happen as bugfix and security updates come in for the packages, and of course any new packages which come in after you've made the config change will bring translations along.






          share|improve this answer














          After changing the settings as you have, you'll need to dnf reinstall any packages which are missing translations (not everything uses the langpacks feature yet). For example:



          dnf reinstall dnf


          and then you'll have translations for DNF. Repeat this for any other packages which are missing translations.



          This will also happen as bugfix and security updates come in for the packages, and of course any new packages which come in after you've made the config change will bring translations along.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Oct 21 '17 at 14:32

























          answered Oct 21 '17 at 14:25









          mattdm

          27k1170109




          27k1170109











          • Wow! That was mind-blowning! Definitely didn't think of reinstalling dnf! And Chinese now works of dnf!
            – jackxujh
            Oct 21 '17 at 14:30
















          • Wow! That was mind-blowning! Definitely didn't think of reinstalling dnf! And Chinese now works of dnf!
            – jackxujh
            Oct 21 '17 at 14:30















          Wow! That was mind-blowning! Definitely didn't think of reinstalling dnf! And Chinese now works of dnf!
          – jackxujh
          Oct 21 '17 at 14:30




          Wow! That was mind-blowning! Definitely didn't think of reinstalling dnf! And Chinese now works of dnf!
          – jackxujh
          Oct 21 '17 at 14:30

















           

          draft saved


          draft discarded















































           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f399412%2flocale-installation-and-setting-on-fedora-have-no-effect%23new-answer', 'question_page');

          );

          Post as a guest













































































          Popular posts from this blog

          How to check contact read email or not when send email to Individual?

          Displaying single band from multi-band raster using QGIS

          How many registers does an x86_64 CPU actually have?