<!-- 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: --> New PDF importer in 1.3 beta 0 doesn't seem to recognize signals to change the case of an entire text box to all caps, title case, etc. #### Steps to reproduce: <!-- Describe what you did (step-by-step) so we can reproduce: --> - open Inkscape - import a PDF file (try attached PDF for example) - open the same PDF in a PDF viewer - observe difference in case for text regions that use all caps #### What happened? Inkscape renders text in its default case, without regard to overall case rules set by another layout software. In some cases, this leads to random cases throughout words or sentences if the original file did not set the individual letter's case correctly. The image attached below shows the same PDF in Mac preview (top left) and in Inkscape (bottom right).  #### What should have happened? Inkscape should pay attention to overall case rules like all caps or title case and render text elements accordingly. Sample attachments: <!-- Attach the sample file(s) highlighting the issue, if appropriate. --> [May-27.pdf](/uploads/a5fba80e91d3dd2d7f5cc9a6395574d0/May-27.pdf) #### Version info Inkscape 1.3-beta (cedbd6c, 2023-05-28) <!-- 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. -->