<!-- 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: --> Inkscape version: 1.2.2 OS version: Windows10 #### Steps to reproduce: <!-- Describe what you did (step-by-step) so we can reproduce: --> - open Inkscape and create an empty file - click "Text" button, and draw a sufficiently large area. -  - Input any texts with any font, (For example: "aaaaaa") and press "Enter" to create a new Line -  - Input any texts with any font. (Can same as first line or diffrence) - Save the file with any filename. (For example: "绘图1.svg") - Use inkscpae command to covert the svg file to pdf. - inkscape --export-area-drawing --export-filename=bin\绘图1.pdf src\绘图1.svg -  #### What happened? Error message: "Invalid glyph found, continuing.." show in the console. #### What should have happened? Conert svg to pdf successfully without any error or warning. Sample attachments: <!-- 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: --> ``` ``` <!-- ❤️ 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. -->