The font family "Cascadia" doesn't apply to the text. *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. select text tool 2. create text box 3. type text and choose font "Cascadia ##" (## can be Code or Mono, both don't work) 4. save change OBSERVED RESULT 1. the text in the vector layer is different from the text in edit text window EXPECTED RESULT 1. they should be the same SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION 1. Please check if there are any other text font cannot apply on the text.
Hi, can you share a screenshot of the difference? Cascadia is a variable font, and it might be that the two different text engines are selecting a different weight.
Created attachment 164983 [details] Cascadia working in Krita 5.3's new text tool For what it's worth, it *does* work in 5.3 with the new text tool, so at the very least it will work in the next version of Krita?
I consider that as problem solved. We don't do any of the rendering ourselves in Krita 5.2, so this isn't something we can actually influence. Plus, all text code in 5.2 is legacy.
Comment on attachment 164983 [details] Cascadia working in Krita 5.3's new text tool As Krita 5.3 is not public yet, does it mean I have to wait for the new version?
Created attachment 164997 [details] Here is a lyrics quotation of "Lily" on canvas, and the text is not Cascadia on the canvas Here is a lyrics quotation of "Lily" on canvas, and the text is not Cascadia on the canvas, but I made the setting in the text tool.
Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information.