As part of the Font API project we should support TrueDoc, see http://www.bitstream.com/font_rendering/products/tdis/overview.html. We need to contact bitstream, there is a link at the bottom of the overview page, and arrange to get the TrueDoc system, then get it to work with our interpreters. Hopefully it will be similar to Monotype, the new Zoran offering supports the BitStream renderer. I thought this should be tied in with the font api project, which seems to lack an end user deliverable, let me know if you want to handle it differently.
It makes sense as a requirement for the design work, so I'm fine with the bug. Thanks for the reminder. The end user deliverable is better support for alternate font renders, but you're correct that we've been focussed on the internal advantages of separating font parsing at the interpreter level from rendering through the graphics library.
Outline support has been added in revision 11259. This is little more than a proof of possibility, the current code only works with type 1 PostScript fonts. However addition of other font types should be reasonably possible from this starting point. Re-assigning this one to Chris for future enhancements.
I don't believe we need to track this in bugzilla any more. In 10 years, we've never had a request for Bitstream. We already have Freetype and UFST, and a skeleton for Bitstream, and completing it shouldn't be more complex than the existing two. If a credible requirement for it arises, we'll finish the work. But as of now, I'm closing this.