Comment 3 for bug 170963

Originator: NO

I just looked on the roadmap to see if this is planned for the foreseeable
future, but I haven't found it. I would second this request since it would
solve problems in at least two areas:

* Displaying of SVG images that contain text, especially on the web. One
could keep text as text (i.e., not convert it into paths), but still
display it correctly. Since drawings often make use of special fonts, this
much more a topic than with HTML pages that often use widely available
standard fonts.
For this, an option like "embedd subset of font" could keep the file size
low but ensure correct display. The file size would often be smaller than
with text converted to paths, since every glyph has to be embedded only
once.

* Collaborative editing, exchanging files. Inkscape now supports embedding
bitmap images, so the exchange of files has become much easier. But with
fonts, it's still difficult. Embedding whole fonts as SVG fonts would allow
one to exchange only the SVG file, while still being able to edit or add
text, without depending on the font beeing available on the current
system.

Could anyone give a hint how difficult this would be to realize or if it's
already planned? My guess would also be that the existing mechanisms in
Inkscape should make this not too hard, but I may be totally wrong.