How to disable bitmap fonts?












1














I was trying a bitmap font from github, and I had to enable bitmap fonts as they are disabled by default in Ubuntu. I did not know that enabling bitmap fonts would have some side-effects. I'm sure something seems wrong with my the text in Chrome(just as if it's using a new font altogether). I don't like it. So I'd like to revert it as it was before I enabled bitmap fonts.



I used the following commands to enable bitmap fonts:



cd /etc/fonts/conf.d/
sudo rm /etc/fonts/conf.d/10* && sudo rm -rf 70-no-bitmaps.conf && sudo ln -s ../conf.avail/70-yes-bitmaps.conf
sudo dpkg-reconfigure fontconfig


Please help me to disable bitmap fonts. Thanks in advance!










share|improve this question



























    1














    I was trying a bitmap font from github, and I had to enable bitmap fonts as they are disabled by default in Ubuntu. I did not know that enabling bitmap fonts would have some side-effects. I'm sure something seems wrong with my the text in Chrome(just as if it's using a new font altogether). I don't like it. So I'd like to revert it as it was before I enabled bitmap fonts.



    I used the following commands to enable bitmap fonts:



    cd /etc/fonts/conf.d/
    sudo rm /etc/fonts/conf.d/10* && sudo rm -rf 70-no-bitmaps.conf && sudo ln -s ../conf.avail/70-yes-bitmaps.conf
    sudo dpkg-reconfigure fontconfig


    Please help me to disable bitmap fonts. Thanks in advance!










    share|improve this question

























      1












      1








      1







      I was trying a bitmap font from github, and I had to enable bitmap fonts as they are disabled by default in Ubuntu. I did not know that enabling bitmap fonts would have some side-effects. I'm sure something seems wrong with my the text in Chrome(just as if it's using a new font altogether). I don't like it. So I'd like to revert it as it was before I enabled bitmap fonts.



      I used the following commands to enable bitmap fonts:



      cd /etc/fonts/conf.d/
      sudo rm /etc/fonts/conf.d/10* && sudo rm -rf 70-no-bitmaps.conf && sudo ln -s ../conf.avail/70-yes-bitmaps.conf
      sudo dpkg-reconfigure fontconfig


      Please help me to disable bitmap fonts. Thanks in advance!










      share|improve this question













      I was trying a bitmap font from github, and I had to enable bitmap fonts as they are disabled by default in Ubuntu. I did not know that enabling bitmap fonts would have some side-effects. I'm sure something seems wrong with my the text in Chrome(just as if it's using a new font altogether). I don't like it. So I'd like to revert it as it was before I enabled bitmap fonts.



      I used the following commands to enable bitmap fonts:



      cd /etc/fonts/conf.d/
      sudo rm /etc/fonts/conf.d/10* && sudo rm -rf 70-no-bitmaps.conf && sudo ln -s ../conf.avail/70-yes-bitmaps.conf
      sudo dpkg-reconfigure fontconfig


      Please help me to disable bitmap fonts. Thanks in advance!







      fonts






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked May 24 at 10:11









      swingcake

      7311




      7311






















          2 Answers
          2






          active

          oldest

          votes


















          1














          The directory /etc/fonts/conf.d/ contains symbolic links to configuration files within /etc/fonts/conf.avail/. These symlinks can be added and removed to customize the configuration of fontconfig.



          The commands you previously ran disabled all 10-* configuration options, as well as disabling 70-no-bitmaps and enabling 70-yes-bitmaps. To reverse the latter part specifically, you can run the following:



          cd /etc/fonts/conf.d
          sudo rm 70-yes-bitmaps.conf
          sudo ln -s ../conf.avail/70-no-bitmaps.conf ./


          To reverse the effect of disabling the 10-* configuration files depends on which config files you had enabled to begin with. Here are the 10-* config files I have enabled on my machine:



          cd /etc/fonts/conf.d
          sudo ln -s ../conf.avail/10-hinting-slight.conf ./
          sudo ln -s ../conf.avail/10-scale-bitmap-fonts.conf ./
          sudo ln -s ../conf.avail/10-sub-pixel-rgb.conf ./


          Alternatively, here is how you can enable the default 10-* options for Ubuntu Bionic:



          cd /etc/fonts/conf.d
          sudo ln -s ../conf.avail/10-hinting-slight.conf ./
          sudo ln -s ../conf.avail/10-scale-bitmap-fonts.conf ./
          sudo ln -s ../conf.avail/10-antialias.conf ./


          I would personally recommend however, that you opt for sub-pixel-rgb instead of antialias unless you don't have a standard LCD monitor.



          You may find however that the strange font rendering you're getting in Chrome is because you disabled these 10-* config files and not because you enabled bitmap fonts. You may want to try only re-enabling just these config files without swapping back from 70-yes-bitmaps to 70-no-bitmaps before reverting completely to having no bitmap fonts. Enabling 70-yes-bitmaps should not affect any other fonts besides allowing bitmap fonts to be used. It is also possible that you have some missing fonts and may get better results than you had originally by running:



          sudo apt install ttf-mscorefonts-installer


          Finally, after you have altered your fontconfig configuration, you should run:



          sudo dpkg-reconfigure fontconfig


          This will update your fontconfig cache so your changes can take effect. You may also need to restart your programs / log out and back in / reboot your computer to see the changes take effect.






          share|improve this answer























          • It seems that I already have ttf-mscorefonts-installer installed. I also have no idea which 10-* configuration files I had symlinked. Although, I can give you a list of of 10-* config files in /etc/fonts/conf.avail: edit in progress
            – swingcake
            May 24 at 14:14












          • @swingcake I have updated the answer with the defaults for Ubuntu. You could enable these or instead opt for config files I have enabled if you would rather have subpixel "cleartype"-like font rendering.
            – Candy Gumdrop
            May 24 at 14:25










          • Thank you for the very insightful answer. I have an IPS LCD panel, and would definitely follow your recommendation regarding that. I would also like to ask for the source of your information(the default 10-* config files in Bionic). Another doubt I have is that why did the author of that particular bitmap font add the disabling of 10-* config files if that was not required to enable bitmap fonts at all. Is there a relation at all between them? One more thing, in the command above to enable bitmap fonts sudo ln -s ../conf.avail/70-yes-bitmaps.conf there is no ./ compared to your command
            – swingcake
            May 24 at 16:08






          • 1




            @swingcake I got the default files for Bionic by downloading the .deb package for fontconfig-config and inspecting its contents. I'm not sure why they might remove the 10-* configs. Maybe they were intending to make all fonts non-antialiased. I used ./ to be explicit about creating the symlink in the current directory (just what I'm used to and more similar to usage of the cp command), though it can be omitted and ln creates a symlink in the current directory by default.
            – Candy Gumdrop
            May 24 at 16:15






          • 1




            @swingcake Updated the answer (no it won't affect other fonts).
            – Candy Gumdrop
            May 24 at 17:45



















          0














          Aside answer by @Candy Gumdrop, it's good to disable embedded bitmap, some fonts (like Calibri) will look terrible in some resolutions (see image bellow) if this setting stills enabled. Calibri fonts and other cleartype fonts have bitmap versions embedded in them which activate at small sizes, which makes it look bad.



          You can disable by doing this:



          cd /etc/fonts/conf.d

          cat << END | sudo tee ../conf.avail/99-no-embeddedbitmap.conf
          <?xml version="1.0"?>
          <!DOCTYPE fontconfig SYSTEM "fonts.dtd">
          <fontconfig>
          <its:rules xmlns:its="http://www.w3.org/2005/11/its" version="1.0">
          <its:translateRule translate="no" selector="/fontconfig/*[not(self::description)]"/>
          </its:rules>

          <description>Disable embedded bitmap</description>
          <match target="font" >
          <edit name="embeddedbitmap" mode="assign">
          <bool>false</bool>
          </edit>
          </match>
          </fontconfig>
          END

          sudo ln -s ../conf.avail/99-no-embeddedbitmap.conf ./

          sudo dpkg-reconfigure fontconfig


          enter image description here






          share|improve this answer










          New contributor




          iuridiniz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.


















            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "89"
            };
            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',
            autoActivateHeartbeat: false,
            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%2faskubuntu.com%2fquestions%2f1039763%2fhow-to-disable-bitmap-fonts%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            1














            The directory /etc/fonts/conf.d/ contains symbolic links to configuration files within /etc/fonts/conf.avail/. These symlinks can be added and removed to customize the configuration of fontconfig.



            The commands you previously ran disabled all 10-* configuration options, as well as disabling 70-no-bitmaps and enabling 70-yes-bitmaps. To reverse the latter part specifically, you can run the following:



            cd /etc/fonts/conf.d
            sudo rm 70-yes-bitmaps.conf
            sudo ln -s ../conf.avail/70-no-bitmaps.conf ./


            To reverse the effect of disabling the 10-* configuration files depends on which config files you had enabled to begin with. Here are the 10-* config files I have enabled on my machine:



            cd /etc/fonts/conf.d
            sudo ln -s ../conf.avail/10-hinting-slight.conf ./
            sudo ln -s ../conf.avail/10-scale-bitmap-fonts.conf ./
            sudo ln -s ../conf.avail/10-sub-pixel-rgb.conf ./


            Alternatively, here is how you can enable the default 10-* options for Ubuntu Bionic:



            cd /etc/fonts/conf.d
            sudo ln -s ../conf.avail/10-hinting-slight.conf ./
            sudo ln -s ../conf.avail/10-scale-bitmap-fonts.conf ./
            sudo ln -s ../conf.avail/10-antialias.conf ./


            I would personally recommend however, that you opt for sub-pixel-rgb instead of antialias unless you don't have a standard LCD monitor.



            You may find however that the strange font rendering you're getting in Chrome is because you disabled these 10-* config files and not because you enabled bitmap fonts. You may want to try only re-enabling just these config files without swapping back from 70-yes-bitmaps to 70-no-bitmaps before reverting completely to having no bitmap fonts. Enabling 70-yes-bitmaps should not affect any other fonts besides allowing bitmap fonts to be used. It is also possible that you have some missing fonts and may get better results than you had originally by running:



            sudo apt install ttf-mscorefonts-installer


            Finally, after you have altered your fontconfig configuration, you should run:



            sudo dpkg-reconfigure fontconfig


            This will update your fontconfig cache so your changes can take effect. You may also need to restart your programs / log out and back in / reboot your computer to see the changes take effect.






            share|improve this answer























            • It seems that I already have ttf-mscorefonts-installer installed. I also have no idea which 10-* configuration files I had symlinked. Although, I can give you a list of of 10-* config files in /etc/fonts/conf.avail: edit in progress
              – swingcake
              May 24 at 14:14












            • @swingcake I have updated the answer with the defaults for Ubuntu. You could enable these or instead opt for config files I have enabled if you would rather have subpixel "cleartype"-like font rendering.
              – Candy Gumdrop
              May 24 at 14:25










            • Thank you for the very insightful answer. I have an IPS LCD panel, and would definitely follow your recommendation regarding that. I would also like to ask for the source of your information(the default 10-* config files in Bionic). Another doubt I have is that why did the author of that particular bitmap font add the disabling of 10-* config files if that was not required to enable bitmap fonts at all. Is there a relation at all between them? One more thing, in the command above to enable bitmap fonts sudo ln -s ../conf.avail/70-yes-bitmaps.conf there is no ./ compared to your command
              – swingcake
              May 24 at 16:08






            • 1




              @swingcake I got the default files for Bionic by downloading the .deb package for fontconfig-config and inspecting its contents. I'm not sure why they might remove the 10-* configs. Maybe they were intending to make all fonts non-antialiased. I used ./ to be explicit about creating the symlink in the current directory (just what I'm used to and more similar to usage of the cp command), though it can be omitted and ln creates a symlink in the current directory by default.
              – Candy Gumdrop
              May 24 at 16:15






            • 1




              @swingcake Updated the answer (no it won't affect other fonts).
              – Candy Gumdrop
              May 24 at 17:45
















            1














            The directory /etc/fonts/conf.d/ contains symbolic links to configuration files within /etc/fonts/conf.avail/. These symlinks can be added and removed to customize the configuration of fontconfig.



            The commands you previously ran disabled all 10-* configuration options, as well as disabling 70-no-bitmaps and enabling 70-yes-bitmaps. To reverse the latter part specifically, you can run the following:



            cd /etc/fonts/conf.d
            sudo rm 70-yes-bitmaps.conf
            sudo ln -s ../conf.avail/70-no-bitmaps.conf ./


            To reverse the effect of disabling the 10-* configuration files depends on which config files you had enabled to begin with. Here are the 10-* config files I have enabled on my machine:



            cd /etc/fonts/conf.d
            sudo ln -s ../conf.avail/10-hinting-slight.conf ./
            sudo ln -s ../conf.avail/10-scale-bitmap-fonts.conf ./
            sudo ln -s ../conf.avail/10-sub-pixel-rgb.conf ./


            Alternatively, here is how you can enable the default 10-* options for Ubuntu Bionic:



            cd /etc/fonts/conf.d
            sudo ln -s ../conf.avail/10-hinting-slight.conf ./
            sudo ln -s ../conf.avail/10-scale-bitmap-fonts.conf ./
            sudo ln -s ../conf.avail/10-antialias.conf ./


            I would personally recommend however, that you opt for sub-pixel-rgb instead of antialias unless you don't have a standard LCD monitor.



            You may find however that the strange font rendering you're getting in Chrome is because you disabled these 10-* config files and not because you enabled bitmap fonts. You may want to try only re-enabling just these config files without swapping back from 70-yes-bitmaps to 70-no-bitmaps before reverting completely to having no bitmap fonts. Enabling 70-yes-bitmaps should not affect any other fonts besides allowing bitmap fonts to be used. It is also possible that you have some missing fonts and may get better results than you had originally by running:



            sudo apt install ttf-mscorefonts-installer


            Finally, after you have altered your fontconfig configuration, you should run:



            sudo dpkg-reconfigure fontconfig


            This will update your fontconfig cache so your changes can take effect. You may also need to restart your programs / log out and back in / reboot your computer to see the changes take effect.






            share|improve this answer























            • It seems that I already have ttf-mscorefonts-installer installed. I also have no idea which 10-* configuration files I had symlinked. Although, I can give you a list of of 10-* config files in /etc/fonts/conf.avail: edit in progress
              – swingcake
              May 24 at 14:14












            • @swingcake I have updated the answer with the defaults for Ubuntu. You could enable these or instead opt for config files I have enabled if you would rather have subpixel "cleartype"-like font rendering.
              – Candy Gumdrop
              May 24 at 14:25










            • Thank you for the very insightful answer. I have an IPS LCD panel, and would definitely follow your recommendation regarding that. I would also like to ask for the source of your information(the default 10-* config files in Bionic). Another doubt I have is that why did the author of that particular bitmap font add the disabling of 10-* config files if that was not required to enable bitmap fonts at all. Is there a relation at all between them? One more thing, in the command above to enable bitmap fonts sudo ln -s ../conf.avail/70-yes-bitmaps.conf there is no ./ compared to your command
              – swingcake
              May 24 at 16:08






            • 1




              @swingcake I got the default files for Bionic by downloading the .deb package for fontconfig-config and inspecting its contents. I'm not sure why they might remove the 10-* configs. Maybe they were intending to make all fonts non-antialiased. I used ./ to be explicit about creating the symlink in the current directory (just what I'm used to and more similar to usage of the cp command), though it can be omitted and ln creates a symlink in the current directory by default.
              – Candy Gumdrop
              May 24 at 16:15






            • 1




              @swingcake Updated the answer (no it won't affect other fonts).
              – Candy Gumdrop
              May 24 at 17:45














            1












            1








            1






            The directory /etc/fonts/conf.d/ contains symbolic links to configuration files within /etc/fonts/conf.avail/. These symlinks can be added and removed to customize the configuration of fontconfig.



            The commands you previously ran disabled all 10-* configuration options, as well as disabling 70-no-bitmaps and enabling 70-yes-bitmaps. To reverse the latter part specifically, you can run the following:



            cd /etc/fonts/conf.d
            sudo rm 70-yes-bitmaps.conf
            sudo ln -s ../conf.avail/70-no-bitmaps.conf ./


            To reverse the effect of disabling the 10-* configuration files depends on which config files you had enabled to begin with. Here are the 10-* config files I have enabled on my machine:



            cd /etc/fonts/conf.d
            sudo ln -s ../conf.avail/10-hinting-slight.conf ./
            sudo ln -s ../conf.avail/10-scale-bitmap-fonts.conf ./
            sudo ln -s ../conf.avail/10-sub-pixel-rgb.conf ./


            Alternatively, here is how you can enable the default 10-* options for Ubuntu Bionic:



            cd /etc/fonts/conf.d
            sudo ln -s ../conf.avail/10-hinting-slight.conf ./
            sudo ln -s ../conf.avail/10-scale-bitmap-fonts.conf ./
            sudo ln -s ../conf.avail/10-antialias.conf ./


            I would personally recommend however, that you opt for sub-pixel-rgb instead of antialias unless you don't have a standard LCD monitor.



            You may find however that the strange font rendering you're getting in Chrome is because you disabled these 10-* config files and not because you enabled bitmap fonts. You may want to try only re-enabling just these config files without swapping back from 70-yes-bitmaps to 70-no-bitmaps before reverting completely to having no bitmap fonts. Enabling 70-yes-bitmaps should not affect any other fonts besides allowing bitmap fonts to be used. It is also possible that you have some missing fonts and may get better results than you had originally by running:



            sudo apt install ttf-mscorefonts-installer


            Finally, after you have altered your fontconfig configuration, you should run:



            sudo dpkg-reconfigure fontconfig


            This will update your fontconfig cache so your changes can take effect. You may also need to restart your programs / log out and back in / reboot your computer to see the changes take effect.






            share|improve this answer














            The directory /etc/fonts/conf.d/ contains symbolic links to configuration files within /etc/fonts/conf.avail/. These symlinks can be added and removed to customize the configuration of fontconfig.



            The commands you previously ran disabled all 10-* configuration options, as well as disabling 70-no-bitmaps and enabling 70-yes-bitmaps. To reverse the latter part specifically, you can run the following:



            cd /etc/fonts/conf.d
            sudo rm 70-yes-bitmaps.conf
            sudo ln -s ../conf.avail/70-no-bitmaps.conf ./


            To reverse the effect of disabling the 10-* configuration files depends on which config files you had enabled to begin with. Here are the 10-* config files I have enabled on my machine:



            cd /etc/fonts/conf.d
            sudo ln -s ../conf.avail/10-hinting-slight.conf ./
            sudo ln -s ../conf.avail/10-scale-bitmap-fonts.conf ./
            sudo ln -s ../conf.avail/10-sub-pixel-rgb.conf ./


            Alternatively, here is how you can enable the default 10-* options for Ubuntu Bionic:



            cd /etc/fonts/conf.d
            sudo ln -s ../conf.avail/10-hinting-slight.conf ./
            sudo ln -s ../conf.avail/10-scale-bitmap-fonts.conf ./
            sudo ln -s ../conf.avail/10-antialias.conf ./


            I would personally recommend however, that you opt for sub-pixel-rgb instead of antialias unless you don't have a standard LCD monitor.



            You may find however that the strange font rendering you're getting in Chrome is because you disabled these 10-* config files and not because you enabled bitmap fonts. You may want to try only re-enabling just these config files without swapping back from 70-yes-bitmaps to 70-no-bitmaps before reverting completely to having no bitmap fonts. Enabling 70-yes-bitmaps should not affect any other fonts besides allowing bitmap fonts to be used. It is also possible that you have some missing fonts and may get better results than you had originally by running:



            sudo apt install ttf-mscorefonts-installer


            Finally, after you have altered your fontconfig configuration, you should run:



            sudo dpkg-reconfigure fontconfig


            This will update your fontconfig cache so your changes can take effect. You may also need to restart your programs / log out and back in / reboot your computer to see the changes take effect.







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited May 24 at 17:44

























            answered May 24 at 11:45









            Candy Gumdrop

            1505




            1505












            • It seems that I already have ttf-mscorefonts-installer installed. I also have no idea which 10-* configuration files I had symlinked. Although, I can give you a list of of 10-* config files in /etc/fonts/conf.avail: edit in progress
              – swingcake
              May 24 at 14:14












            • @swingcake I have updated the answer with the defaults for Ubuntu. You could enable these or instead opt for config files I have enabled if you would rather have subpixel "cleartype"-like font rendering.
              – Candy Gumdrop
              May 24 at 14:25










            • Thank you for the very insightful answer. I have an IPS LCD panel, and would definitely follow your recommendation regarding that. I would also like to ask for the source of your information(the default 10-* config files in Bionic). Another doubt I have is that why did the author of that particular bitmap font add the disabling of 10-* config files if that was not required to enable bitmap fonts at all. Is there a relation at all between them? One more thing, in the command above to enable bitmap fonts sudo ln -s ../conf.avail/70-yes-bitmaps.conf there is no ./ compared to your command
              – swingcake
              May 24 at 16:08






            • 1




              @swingcake I got the default files for Bionic by downloading the .deb package for fontconfig-config and inspecting its contents. I'm not sure why they might remove the 10-* configs. Maybe they were intending to make all fonts non-antialiased. I used ./ to be explicit about creating the symlink in the current directory (just what I'm used to and more similar to usage of the cp command), though it can be omitted and ln creates a symlink in the current directory by default.
              – Candy Gumdrop
              May 24 at 16:15






            • 1




              @swingcake Updated the answer (no it won't affect other fonts).
              – Candy Gumdrop
              May 24 at 17:45


















            • It seems that I already have ttf-mscorefonts-installer installed. I also have no idea which 10-* configuration files I had symlinked. Although, I can give you a list of of 10-* config files in /etc/fonts/conf.avail: edit in progress
              – swingcake
              May 24 at 14:14












            • @swingcake I have updated the answer with the defaults for Ubuntu. You could enable these or instead opt for config files I have enabled if you would rather have subpixel "cleartype"-like font rendering.
              – Candy Gumdrop
              May 24 at 14:25










            • Thank you for the very insightful answer. I have an IPS LCD panel, and would definitely follow your recommendation regarding that. I would also like to ask for the source of your information(the default 10-* config files in Bionic). Another doubt I have is that why did the author of that particular bitmap font add the disabling of 10-* config files if that was not required to enable bitmap fonts at all. Is there a relation at all between them? One more thing, in the command above to enable bitmap fonts sudo ln -s ../conf.avail/70-yes-bitmaps.conf there is no ./ compared to your command
              – swingcake
              May 24 at 16:08






            • 1




              @swingcake I got the default files for Bionic by downloading the .deb package for fontconfig-config and inspecting its contents. I'm not sure why they might remove the 10-* configs. Maybe they were intending to make all fonts non-antialiased. I used ./ to be explicit about creating the symlink in the current directory (just what I'm used to and more similar to usage of the cp command), though it can be omitted and ln creates a symlink in the current directory by default.
              – Candy Gumdrop
              May 24 at 16:15






            • 1




              @swingcake Updated the answer (no it won't affect other fonts).
              – Candy Gumdrop
              May 24 at 17:45
















            It seems that I already have ttf-mscorefonts-installer installed. I also have no idea which 10-* configuration files I had symlinked. Although, I can give you a list of of 10-* config files in /etc/fonts/conf.avail: edit in progress
            – swingcake
            May 24 at 14:14






            It seems that I already have ttf-mscorefonts-installer installed. I also have no idea which 10-* configuration files I had symlinked. Although, I can give you a list of of 10-* config files in /etc/fonts/conf.avail: edit in progress
            – swingcake
            May 24 at 14:14














            @swingcake I have updated the answer with the defaults for Ubuntu. You could enable these or instead opt for config files I have enabled if you would rather have subpixel "cleartype"-like font rendering.
            – Candy Gumdrop
            May 24 at 14:25




            @swingcake I have updated the answer with the defaults for Ubuntu. You could enable these or instead opt for config files I have enabled if you would rather have subpixel "cleartype"-like font rendering.
            – Candy Gumdrop
            May 24 at 14:25












            Thank you for the very insightful answer. I have an IPS LCD panel, and would definitely follow your recommendation regarding that. I would also like to ask for the source of your information(the default 10-* config files in Bionic). Another doubt I have is that why did the author of that particular bitmap font add the disabling of 10-* config files if that was not required to enable bitmap fonts at all. Is there a relation at all between them? One more thing, in the command above to enable bitmap fonts sudo ln -s ../conf.avail/70-yes-bitmaps.conf there is no ./ compared to your command
            – swingcake
            May 24 at 16:08




            Thank you for the very insightful answer. I have an IPS LCD panel, and would definitely follow your recommendation regarding that. I would also like to ask for the source of your information(the default 10-* config files in Bionic). Another doubt I have is that why did the author of that particular bitmap font add the disabling of 10-* config files if that was not required to enable bitmap fonts at all. Is there a relation at all between them? One more thing, in the command above to enable bitmap fonts sudo ln -s ../conf.avail/70-yes-bitmaps.conf there is no ./ compared to your command
            – swingcake
            May 24 at 16:08




            1




            1




            @swingcake I got the default files for Bionic by downloading the .deb package for fontconfig-config and inspecting its contents. I'm not sure why they might remove the 10-* configs. Maybe they were intending to make all fonts non-antialiased. I used ./ to be explicit about creating the symlink in the current directory (just what I'm used to and more similar to usage of the cp command), though it can be omitted and ln creates a symlink in the current directory by default.
            – Candy Gumdrop
            May 24 at 16:15




            @swingcake I got the default files for Bionic by downloading the .deb package for fontconfig-config and inspecting its contents. I'm not sure why they might remove the 10-* configs. Maybe they were intending to make all fonts non-antialiased. I used ./ to be explicit about creating the symlink in the current directory (just what I'm used to and more similar to usage of the cp command), though it can be omitted and ln creates a symlink in the current directory by default.
            – Candy Gumdrop
            May 24 at 16:15




            1




            1




            @swingcake Updated the answer (no it won't affect other fonts).
            – Candy Gumdrop
            May 24 at 17:45




            @swingcake Updated the answer (no it won't affect other fonts).
            – Candy Gumdrop
            May 24 at 17:45













            0














            Aside answer by @Candy Gumdrop, it's good to disable embedded bitmap, some fonts (like Calibri) will look terrible in some resolutions (see image bellow) if this setting stills enabled. Calibri fonts and other cleartype fonts have bitmap versions embedded in them which activate at small sizes, which makes it look bad.



            You can disable by doing this:



            cd /etc/fonts/conf.d

            cat << END | sudo tee ../conf.avail/99-no-embeddedbitmap.conf
            <?xml version="1.0"?>
            <!DOCTYPE fontconfig SYSTEM "fonts.dtd">
            <fontconfig>
            <its:rules xmlns:its="http://www.w3.org/2005/11/its" version="1.0">
            <its:translateRule translate="no" selector="/fontconfig/*[not(self::description)]"/>
            </its:rules>

            <description>Disable embedded bitmap</description>
            <match target="font" >
            <edit name="embeddedbitmap" mode="assign">
            <bool>false</bool>
            </edit>
            </match>
            </fontconfig>
            END

            sudo ln -s ../conf.avail/99-no-embeddedbitmap.conf ./

            sudo dpkg-reconfigure fontconfig


            enter image description here






            share|improve this answer










            New contributor




            iuridiniz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.























              0














              Aside answer by @Candy Gumdrop, it's good to disable embedded bitmap, some fonts (like Calibri) will look terrible in some resolutions (see image bellow) if this setting stills enabled. Calibri fonts and other cleartype fonts have bitmap versions embedded in them which activate at small sizes, which makes it look bad.



              You can disable by doing this:



              cd /etc/fonts/conf.d

              cat << END | sudo tee ../conf.avail/99-no-embeddedbitmap.conf
              <?xml version="1.0"?>
              <!DOCTYPE fontconfig SYSTEM "fonts.dtd">
              <fontconfig>
              <its:rules xmlns:its="http://www.w3.org/2005/11/its" version="1.0">
              <its:translateRule translate="no" selector="/fontconfig/*[not(self::description)]"/>
              </its:rules>

              <description>Disable embedded bitmap</description>
              <match target="font" >
              <edit name="embeddedbitmap" mode="assign">
              <bool>false</bool>
              </edit>
              </match>
              </fontconfig>
              END

              sudo ln -s ../conf.avail/99-no-embeddedbitmap.conf ./

              sudo dpkg-reconfigure fontconfig


              enter image description here






              share|improve this answer










              New contributor




              iuridiniz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
              Check out our Code of Conduct.





















                0












                0








                0






                Aside answer by @Candy Gumdrop, it's good to disable embedded bitmap, some fonts (like Calibri) will look terrible in some resolutions (see image bellow) if this setting stills enabled. Calibri fonts and other cleartype fonts have bitmap versions embedded in them which activate at small sizes, which makes it look bad.



                You can disable by doing this:



                cd /etc/fonts/conf.d

                cat << END | sudo tee ../conf.avail/99-no-embeddedbitmap.conf
                <?xml version="1.0"?>
                <!DOCTYPE fontconfig SYSTEM "fonts.dtd">
                <fontconfig>
                <its:rules xmlns:its="http://www.w3.org/2005/11/its" version="1.0">
                <its:translateRule translate="no" selector="/fontconfig/*[not(self::description)]"/>
                </its:rules>

                <description>Disable embedded bitmap</description>
                <match target="font" >
                <edit name="embeddedbitmap" mode="assign">
                <bool>false</bool>
                </edit>
                </match>
                </fontconfig>
                END

                sudo ln -s ../conf.avail/99-no-embeddedbitmap.conf ./

                sudo dpkg-reconfigure fontconfig


                enter image description here






                share|improve this answer










                New contributor




                iuridiniz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.









                Aside answer by @Candy Gumdrop, it's good to disable embedded bitmap, some fonts (like Calibri) will look terrible in some resolutions (see image bellow) if this setting stills enabled. Calibri fonts and other cleartype fonts have bitmap versions embedded in them which activate at small sizes, which makes it look bad.



                You can disable by doing this:



                cd /etc/fonts/conf.d

                cat << END | sudo tee ../conf.avail/99-no-embeddedbitmap.conf
                <?xml version="1.0"?>
                <!DOCTYPE fontconfig SYSTEM "fonts.dtd">
                <fontconfig>
                <its:rules xmlns:its="http://www.w3.org/2005/11/its" version="1.0">
                <its:translateRule translate="no" selector="/fontconfig/*[not(self::description)]"/>
                </its:rules>

                <description>Disable embedded bitmap</description>
                <match target="font" >
                <edit name="embeddedbitmap" mode="assign">
                <bool>false</bool>
                </edit>
                </match>
                </fontconfig>
                END

                sudo ln -s ../conf.avail/99-no-embeddedbitmap.conf ./

                sudo dpkg-reconfigure fontconfig


                enter image description here







                share|improve this answer










                New contributor




                iuridiniz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.









                share|improve this answer



                share|improve this answer








                edited Dec 17 at 23:41





















                New contributor




                iuridiniz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.









                answered Dec 17 at 23:32









                iuridiniz

                1013




                1013




                New contributor




                iuridiniz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.





                New contributor





                iuridiniz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.






                iuridiniz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Ask Ubuntu!


                    • 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%2faskubuntu.com%2fquestions%2f1039763%2fhow-to-disable-bitmap-fonts%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

                    數位音樂下載

                    When can things happen in Etherscan, such as the picture below?

                    格利澤436b