Tracking Issue: Text tool and typography improvements

[nicoburns]

• Searchable fonts (Make menu lists searchable #1499)
• Line height (Add line height and character spacing to the Text node #2016)
• Character width (Add line height and character spacing to the Text node #2016)
• Wrapping text boxes (Add max width/height to text layers and draggable text boxes to the Text tool #2118, Add sizing gizmos to the Text tool's text area #2176)
• Faux italic (Replace Rustybuzz with Parley for text layout, and add text tilt parameter #2739)
• Bidirectional text (Replace Rustybuzz with Parley for text layout, and add text tilt parameter #2739)
• Text alignment, justification, and hyphenation #2351
• Text on a path #978
• Style spans (so users can have a bold word in a paragraph of regular text or one word a different size/color/font than other words).
• Move text editing to be fully handled by the editor (currently an input box is displayed and the text is hidden). An initial prototype exists at Rich text spans #1589.
• Ligatures
• Faux bold
• Font fallback for other scripts (probably Noto Sans / Noto Serif seeing as we can't access the filesystem).
• Advanced styling options
• Inline graphics (other graphical content pasted as glyphs in the text flow)

[0HyperCube]

Thank you for this feature request @nicoburns. The current text tool hasn't really had much development attention, as we have been focusing on migration to a node based document. However this is now mostly complete, and so we can soon focus more on improving the usability of the tools. I have added some additional text tool improvements to your issue for reference.

[Keavon]

It's probably wise that we adopt Cosmic Text for this. As @0HyperCube mentioned, once our migration to the full node graph is done in the near future, we should then be able to branch out to improve existing features like this one using the full power of the (procedural!) node system.