It relies on CSS properties applied to the element to define which shapes to fill.įonts are fundamental to the display of text. This method has the advantage that one can provide a natural fallback mechanism that works with SVG 1.1.

A GSoC project aims to replace Flowed SVG 1.2 text with this type of text. This is text flowed inside a shape according to the rules of CSS. The code for this element is found in sp-textpath.h and sp-tspan.cpp. The code for the elements used in flowed text is found in src/sp-flowtext.cpp, src/sp-flowregion.cpp, and src/sp-flowdiv.cpp. The only know implementation other than Inkscape is in Batik (if the 'version' attribute is set to 1.2). No browser implemented this type of text.

(One can also get multiline text by setting the 'white-space' property to preserve line feeds but there is no GUI and only Firefox supports this method.) The code for these elements is found in src/sp-text.cpp and src/sp-tspan.cpp. Multi-line text is mimicked by adding the attribute sodipodi:role='line' to each that represents a line. There are several distinct kinds of text in Inkscape: The Text and Font dialog code is in src/ui/dialog/text-edit.cpp. The text Toolbar code is in src/widgets/text-toolbar.cpp. ( nr stands for New Renderer.) The GUI code is distributed over a number of files: for interactive on-screen editing look in src/ui/tools/text-tool.cpp, src/text-editing.cpp, and src/text-chemistry.cpp. The actual rendering code is in src/drawing/drawing-text.cpp. Most of the code that handles text layout (including fonts) can be found in src/libnrtype.

Layout the text, taking into consideration styling (font, font-size, etc.).

Read in text, breaking it into chunks that have the same styling (usually a ) and a unique postion.

Text processing is probably the most complicated part of the Inkscape code base. This page describes Inkscape's text processing.

Aditional fonts for inkscape