Created attachment 107348 [details] screenshots of how the bug manifests For some reason all of the sudden in most themes, even in the normal one I am using the most, keywords that used to be bold are not bold anymore although they are market as bold in configure - Kate > Fonts & Colors. This despite it has worked before and the the current fonts I am using have bold variants for example Dejavu Sans Mono. When using for example Dejavu Sans then keywords become bold again.
This could be a duplicate of bug 378523. Please check the font configuration files for occurences of style names, such as "Normal" or "Regular".
(In reply to Christoph Feck from comment #1) > This could be a duplicate of bug 378523. Please check the font configuration > files for occurences of style names, such as "Normal" or "Regular". Thanks for the reply and the suggestion. I was uncertain though which font configuration files you referred to, so I did a cat|grep for Normal or Regular in all files that are in the /etc/fonts/, ~/.config/fontconfig/. However, there doesn't seem to be anything that is named Normal or Regular. Had a look at the other bug report and it seems similar, might give it a try and remove everything font related from the .config/kdeglobals as suggested there and see if it changes anything. Cheers
I fixed it by changing the ~/.config/kateschemarc In the line that defines the font to be used in a schema/theme e.g. [mySchema] Font=DejaVu Sans Mono,10,-1,5,50,0,0,0,0,0,Regular I changed it to: [mySchema] Font=DejaVu Sans Mono,10,-1,5,50,0,0,0,0,0 and then it works. Why does does it have to be defined as Regular instead just of the font family which seems to be enough? Cheers
Sorry, an edit to the above comment. Since it is DejaVu the "Regular" should actually be "Book".
Thanks for the investigation, so indeed a duplicate. > Why does does it have to be defined as Regular instead just of the font family which seems to be enough? Explained in the duplicate. *** This bug has been marked as a duplicate of bug 378523 ***
*** Bug 384053 has been marked as a duplicate of this bug. ***
*** Bug 391040 has been marked as a duplicate of this bug. ***
*** Bug 394845 has been marked as a duplicate of this bug. ***