<!-- 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: <!-- Summarize the issue/suggestion concisely: --> Ok, this is an odd bug. I was looking through some old files today looking for one I needed. I finally find said file, and open it up in Inkscape. Once I do, I attempt to access the text in the file that happened to be in Times New Roman. However, when I selected the text, it weirdly calmed the font was 'Times New', and didn't exist, yet in the file itself (via a text editor), it clearly says it is indeed saved as Times New Roman in the style tag. So, I don't know if this was an issue that somehow came from the version of Inkscape the file was last edited in (0.48.3.1 r9886), but it just seems 'odd'. So, I isolated the font style info and maybe one of you devs can figure out what the heck is happening here to give it the wrong name in Inkscape. The crazy thing is, if I fix the font, and resave the file, the issue then goes away. Just want to stress, this minimal reproducible file was created in 1.1.2, with me then replacing the style tags with the exact same style lines the original file via a text editor. This issue happens in both 1.1.2 & 1.2.1 (all I've been able to test so far) with new profiles. #### Steps to reproduce: <!-- Describe what you did (step-by-step) so we can reproduce: --> 1) Open attached file: [font_issue.svg](/uploads/92b7d3040815c62f2426c078c0c090d8/font_issue.svg) 2) Select the text. 3) Double click on the text to make it editable. #### What happened? If you look up at the text edit bar, in the place where the font name is located, it calls it "Times New", and says it can't find the font on the system. Picture via Inkscape 1.1.2 (b8e25be833, 2022-02-05) x64:  #### What should have happened? In the text edit bar where the font name is located, it should say "Times New Roman" (which I do have installed). Picture via Inkscape 0.48.5 r10040 x64:  <!-- Attach the sample file(s) highlighting the issue, if appropriate. --> #### 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.1.2 (b8e25be833, 2022-02-05) x64 Inkscape 1.2.1 (9c6d41e410, 2022-07-14) x64 Windows 7 SP1 x64 ``` <!-- ❤️ 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. -->