How to make FreeMind render fonts smooth again?











up vote
1
down vote

favorite
1












After upgrading from Ubuntu 18.04 to 18.10, the mindmapping application FreeMind shows "rough" fonts (means, without any antialiasing) in some parts.



The mindmap display still has anti-aliased fonts, as long as I have that configured under "Tools → Preferences … → Appearance → Antialias". However, the menu fonts and anything written in the editor (rich text editor or plain text editor) has no antialiasing anymore.



How to fix that?










share|improve this question




























    up vote
    1
    down vote

    favorite
    1












    After upgrading from Ubuntu 18.04 to 18.10, the mindmapping application FreeMind shows "rough" fonts (means, without any antialiasing) in some parts.



    The mindmap display still has anti-aliased fonts, as long as I have that configured under "Tools → Preferences … → Appearance → Antialias". However, the menu fonts and anything written in the editor (rich text editor or plain text editor) has no antialiasing anymore.



    How to fix that?










    share|improve this question


























      up vote
      1
      down vote

      favorite
      1









      up vote
      1
      down vote

      favorite
      1






      1





      After upgrading from Ubuntu 18.04 to 18.10, the mindmapping application FreeMind shows "rough" fonts (means, without any antialiasing) in some parts.



      The mindmap display still has anti-aliased fonts, as long as I have that configured under "Tools → Preferences … → Appearance → Antialias". However, the menu fonts and anything written in the editor (rich text editor or plain text editor) has no antialiasing anymore.



      How to fix that?










      share|improve this question















      After upgrading from Ubuntu 18.04 to 18.10, the mindmapping application FreeMind shows "rough" fonts (means, without any antialiasing) in some parts.



      The mindmap display still has anti-aliased fonts, as long as I have that configured under "Tools → Preferences … → Appearance → Antialias". However, the menu fonts and anything written in the editor (rich text editor or plain text editor) has no antialiasing anymore.



      How to fix that?







      java 18.10






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Dec 1 at 2:46

























      asked Nov 30 at 2:12









      tanius

      2,4171821




      2,4171821






















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          1
          down vote













          The switch from Ubuntu 18.04 to 18.10 included the switch from OpenJDK 10 to 11, and probably that (re-)introduced a bug related to the configuration of anti-aliasing in all Swing-based Java applications, such as Freemind.



          There is a general solution here, which still works in Ubuntu 18.10. But, at least in desktop environments based on the Openbox window manager (LXDE / LXQt / Lubuntu), the relevant options are not picked up by FreeMind when configured in any of the following places:




          • /etc/environment

          • /etc/profile.d/…


          • /etc/xdg/openbox/environment (recommended here)


          Instead, use the following solution (assumed that you use the regularly installed Freemind startup script written in bash):





          1. Create and edit the following file:





            • ~/.freemind/freemindrc to configure anti-aliasing for your user only, or


            • /etc/freemind/freemindrc to configure it system-wide




          2. Put in the following line and save the file:



            _JAVA_OPTIONS='-Dawt.useSystemAAFontSettings=on -Dswing.aatext=true'


          3. Start Freemind normally. Its start script will read the file you created and use the option provided. Editor text is now properly anti-aliased.


          4. The menu fonts are now anti-aliased, but have strange artefacts that makes them ugly in a different way. To fix this, you can switch to the "Gtk" or "GTK+" look & feel under "Tools → Preferences … → Appearance → Look and Feel → Look and Feel". But be aware that these themes have their own problems, just not about fonts.



          Note that if you installed FreeMind as a snap package, this solution will only work if you start FreeMind with the command /snap/freemind/current/freemind/freemind.sh. It will not work if you use the automatically generated desktop icons or menu entries, as these use a different wrapper mechanism to start FreeMind. (Which can be adapted as well, but I don't yet know how …)






          share|improve this answer























            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',
            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%2f1097314%2fhow-to-make-freemind-render-fonts-smooth-again%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            1
            down vote













            The switch from Ubuntu 18.04 to 18.10 included the switch from OpenJDK 10 to 11, and probably that (re-)introduced a bug related to the configuration of anti-aliasing in all Swing-based Java applications, such as Freemind.



            There is a general solution here, which still works in Ubuntu 18.10. But, at least in desktop environments based on the Openbox window manager (LXDE / LXQt / Lubuntu), the relevant options are not picked up by FreeMind when configured in any of the following places:




            • /etc/environment

            • /etc/profile.d/…


            • /etc/xdg/openbox/environment (recommended here)


            Instead, use the following solution (assumed that you use the regularly installed Freemind startup script written in bash):





            1. Create and edit the following file:





              • ~/.freemind/freemindrc to configure anti-aliasing for your user only, or


              • /etc/freemind/freemindrc to configure it system-wide




            2. Put in the following line and save the file:



              _JAVA_OPTIONS='-Dawt.useSystemAAFontSettings=on -Dswing.aatext=true'


            3. Start Freemind normally. Its start script will read the file you created and use the option provided. Editor text is now properly anti-aliased.


            4. The menu fonts are now anti-aliased, but have strange artefacts that makes them ugly in a different way. To fix this, you can switch to the "Gtk" or "GTK+" look & feel under "Tools → Preferences … → Appearance → Look and Feel → Look and Feel". But be aware that these themes have their own problems, just not about fonts.



            Note that if you installed FreeMind as a snap package, this solution will only work if you start FreeMind with the command /snap/freemind/current/freemind/freemind.sh. It will not work if you use the automatically generated desktop icons or menu entries, as these use a different wrapper mechanism to start FreeMind. (Which can be adapted as well, but I don't yet know how …)






            share|improve this answer



























              up vote
              1
              down vote













              The switch from Ubuntu 18.04 to 18.10 included the switch from OpenJDK 10 to 11, and probably that (re-)introduced a bug related to the configuration of anti-aliasing in all Swing-based Java applications, such as Freemind.



              There is a general solution here, which still works in Ubuntu 18.10. But, at least in desktop environments based on the Openbox window manager (LXDE / LXQt / Lubuntu), the relevant options are not picked up by FreeMind when configured in any of the following places:




              • /etc/environment

              • /etc/profile.d/…


              • /etc/xdg/openbox/environment (recommended here)


              Instead, use the following solution (assumed that you use the regularly installed Freemind startup script written in bash):





              1. Create and edit the following file:





                • ~/.freemind/freemindrc to configure anti-aliasing for your user only, or


                • /etc/freemind/freemindrc to configure it system-wide




              2. Put in the following line and save the file:



                _JAVA_OPTIONS='-Dawt.useSystemAAFontSettings=on -Dswing.aatext=true'


              3. Start Freemind normally. Its start script will read the file you created and use the option provided. Editor text is now properly anti-aliased.


              4. The menu fonts are now anti-aliased, but have strange artefacts that makes them ugly in a different way. To fix this, you can switch to the "Gtk" or "GTK+" look & feel under "Tools → Preferences … → Appearance → Look and Feel → Look and Feel". But be aware that these themes have their own problems, just not about fonts.



              Note that if you installed FreeMind as a snap package, this solution will only work if you start FreeMind with the command /snap/freemind/current/freemind/freemind.sh. It will not work if you use the automatically generated desktop icons or menu entries, as these use a different wrapper mechanism to start FreeMind. (Which can be adapted as well, but I don't yet know how …)






              share|improve this answer

























                up vote
                1
                down vote










                up vote
                1
                down vote









                The switch from Ubuntu 18.04 to 18.10 included the switch from OpenJDK 10 to 11, and probably that (re-)introduced a bug related to the configuration of anti-aliasing in all Swing-based Java applications, such as Freemind.



                There is a general solution here, which still works in Ubuntu 18.10. But, at least in desktop environments based on the Openbox window manager (LXDE / LXQt / Lubuntu), the relevant options are not picked up by FreeMind when configured in any of the following places:




                • /etc/environment

                • /etc/profile.d/…


                • /etc/xdg/openbox/environment (recommended here)


                Instead, use the following solution (assumed that you use the regularly installed Freemind startup script written in bash):





                1. Create and edit the following file:





                  • ~/.freemind/freemindrc to configure anti-aliasing for your user only, or


                  • /etc/freemind/freemindrc to configure it system-wide




                2. Put in the following line and save the file:



                  _JAVA_OPTIONS='-Dawt.useSystemAAFontSettings=on -Dswing.aatext=true'


                3. Start Freemind normally. Its start script will read the file you created and use the option provided. Editor text is now properly anti-aliased.


                4. The menu fonts are now anti-aliased, but have strange artefacts that makes them ugly in a different way. To fix this, you can switch to the "Gtk" or "GTK+" look & feel under "Tools → Preferences … → Appearance → Look and Feel → Look and Feel". But be aware that these themes have their own problems, just not about fonts.



                Note that if you installed FreeMind as a snap package, this solution will only work if you start FreeMind with the command /snap/freemind/current/freemind/freemind.sh. It will not work if you use the automatically generated desktop icons or menu entries, as these use a different wrapper mechanism to start FreeMind. (Which can be adapted as well, but I don't yet know how …)






                share|improve this answer














                The switch from Ubuntu 18.04 to 18.10 included the switch from OpenJDK 10 to 11, and probably that (re-)introduced a bug related to the configuration of anti-aliasing in all Swing-based Java applications, such as Freemind.



                There is a general solution here, which still works in Ubuntu 18.10. But, at least in desktop environments based on the Openbox window manager (LXDE / LXQt / Lubuntu), the relevant options are not picked up by FreeMind when configured in any of the following places:




                • /etc/environment

                • /etc/profile.d/…


                • /etc/xdg/openbox/environment (recommended here)


                Instead, use the following solution (assumed that you use the regularly installed Freemind startup script written in bash):





                1. Create and edit the following file:





                  • ~/.freemind/freemindrc to configure anti-aliasing for your user only, or


                  • /etc/freemind/freemindrc to configure it system-wide




                2. Put in the following line and save the file:



                  _JAVA_OPTIONS='-Dawt.useSystemAAFontSettings=on -Dswing.aatext=true'


                3. Start Freemind normally. Its start script will read the file you created and use the option provided. Editor text is now properly anti-aliased.


                4. The menu fonts are now anti-aliased, but have strange artefacts that makes them ugly in a different way. To fix this, you can switch to the "Gtk" or "GTK+" look & feel under "Tools → Preferences … → Appearance → Look and Feel → Look and Feel". But be aware that these themes have their own problems, just not about fonts.



                Note that if you installed FreeMind as a snap package, this solution will only work if you start FreeMind with the command /snap/freemind/current/freemind/freemind.sh. It will not work if you use the automatically generated desktop icons or menu entries, as these use a different wrapper mechanism to start FreeMind. (Which can be adapted as well, but I don't yet know how …)







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Nov 30 at 21:42

























                answered Nov 30 at 2:12









                tanius

                2,4171821




                2,4171821






























                    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%2f1097314%2fhow-to-make-freemind-render-fonts-smooth-again%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

                    Quarter-circle Tiles

                    build a pushdown automaton that recognizes the reverse language of a given pushdown automaton?

                    Mont Emei