<!-- See our full bug reporting guidelines at https://inkscape.org/contribute/report-bugs/ Writing a good bug report will ensure we'll be able to help efficiently. 🙂 --> #### Summary: Old files created by 1.2.x have text with a font specified as 'sans-serif' but 1.3 says that doesn't exist with a warning triangle. #### Steps to reproduce: - Create or find an old document with 1.2.x that has editable text with the font set to 'sans-serif' - Open said document with Inkscape 1.3 - Edit text, note font has a triangle next to it - Change font to 'Sans', see triangle goes away #### What happened? The UI says 'sans-serif' is not recognized (warning triangle in the font dropdown). #### What should have happened? It should be a recognized keyword, as support was added for 'sans-serif' in a prior version to match what CSS recognizes, iirc. Obviously this is low-priority since it defaults to the same font as Sans (at least on Windows), but hopefully it's also easy to add back. 🙂 #### Version info <!-- Open 'Help > About' and click on the little bug icon in the bottom right corner that copies the debug information to your clipboard. For command line users, run 'inkscape --debug-info'. For Inkscape 1.0.2 and older, please manually add the Inkscape Version and Operating System Version. The Inkscape version is listed in the About dialog. For command line users, run 'inkscape -V' Paste the information in the empty space between the apostrophes below: --> ``` Inkscape 1.3 (0e150ed6c4, 2023-07-21) GLib version: 2.76.4 GTK version: 3.24.38 glibmm version: 2.66.6 gtkmm version: 3.24.7 libxml2 version: 2.11.4 libxslt version: 1.1.38 Cairo version: 1.17.7 Pango version: 1.50.14 HarfBuzz version: 8.0.1 OS version: Windows 10 22H2 ``` <!-- ❤️ Thank you for filling in a new bug report, we appreciate the help! ❤️ Please be patient while we try to find the time to look into your issue. Remember that Inkscape is developed by volunteers in their spare time, we'll try our best to respond to all reports. --> <!-- Please be careful when/after writing # for example in logs, code, or versions of linux - use inline code span - single backticks (`) before and after it, like this - `#1618` - use multi-line code block - triple backticks (```) to fence/enclose console logs - attach long logs as a text file. -->