Bug 435372 - [Regression] Unable to set fonts in color schemas
Summary: [Regression] Unable to set fonts in color schemas
Status: RESOLVED INTENTIONAL
Alias: None
Product: frameworks-ktexteditor
Classification: Frameworks and Libraries
Component: general (other bugs)
Version First Reported In: 5.80.0
Platform: Other Other
: NOR normal
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-04-05 04:53 UTC by Safa Alfulaij
Modified: 2021-09-25 08:53 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Kate per-filetype font settings (48.51 KB, image/png)
2021-09-25 08:29 UTC, Jan Paul Batrina
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Safa Alfulaij 2021-04-05 04:53:53 UTC
SUMMARY

With the last update of Kate, I lost my custom-made schemas and am not able to choose the font in any new custom-made schemas I create
This is really sad as I have different types of documents that I want to display each with another font (letters, code, printing, etc) and now I am not able to do that the way I used to do it.
What I see now is a global font state, which sets the font on every document.
I thought Kate stands for KDE Advanced Text Editor.
Comment 1 Jan Paul Batrina 2021-09-25 08:29:07 UTC
Created attachment 141897 [details]
Kate per-filetype font settings

> am not able to choose the font in any new custom-made schemas I create
When color schemas were ported to color schemes, the ability to specifiy the font was removed. From https://kate-editor.org/post/2020/2020-09-06-kate-color-themes/:

"The UI is changed to call this “Color Theme” instead of “Schema”, the font choosing is decoupled from this now in the settings dialog. Color themes can only alter the coloring and text attributes like bold/italic/underline/…, but not switch the font itself."

That said, you can still write here your use case(s) (I think the more specific, the better) so that others can offer alternative ways to accomplish the same goal now that the feature is removed, or if there is no other way then the maintainers might be convinced to reinstate it (provided that there will be people interested in re-implementing).

> With the last update of Kate, I lost my custom-made schemas
With the issue of fonts addressed above, https://invent.kde.org/frameworks/syntax-highlighting/-/blob/master/utils/kateschema_to_theme_converter.py provides a way to convert your custom schemas to the corresponding color themes (I remember reading (but couldn't find) a blog post of how to use it, but hopefully the script Usage included in the script will be enough for now).

> What I see now is a global font state, which sets the font on every document.
It's a little bit hidden, but you can specify the font/font-size (among many other things) using the variables in filetypes (Settings > Open/Save > Modes & filetypes), see the attached screenshot
Comment 2 Safa Alfulaij 2021-09-25 08:53:53 UTC
My use case is that I use Kate instead of word processor applications (Writer, Word, etc).

I believe that I can live now with filetype-specific font selection, which is still better than nothing at all. But I need to open another 2 bugs so that the UI/UX is enhanced, and that the font should change when changing the filetype (currently it doesn't, and does only on opening files with that filetype)

Thanks Jan!