Comment 8 for bug 1449476

Difference as claimed between Inkscape 0.48 and 0.91 not reproduced on OS X 10.7.5:
The outlining of the stroked characters is rendered "badly" (not precisely fitting the (filled) characters at certain smaller sizes) in PDFs generated using Inkscape 0.48.2, 0.48.5, 0.91 and 0.91+devel, and it also occurs with various tested cairo versions (1.12.2, 1.12.16, 1.14.2). PDF content was "verified/inspected" with Apple's Preview.app and with poppler-glib-demo (PDF tool from latest poppler 0.32).

The difference as reported and demonstrated in the attached PDF files could be related to:
a) the versions of the dependencies bundled with Inkscape (e.g. the 32bit packages of Inkscape ship with outdated unstable cairo snapshot 1.11.2, the 64bit builds of Inkscape 0.91 include cairo 1.14.x (snapshot from rather recent git master).
or possibly to:
b) the circumstance that Inkscape 0.91 on Windows switched the pango font backend from native to fontconfig (same as used on the other platforms).

[ Initially I thought it could be related to the new CFF hinter in recent freetype (see bug #1396582), but the imprecise outlines of the stroked texts at certain (smaller) sizes happens with older freetype versions as well as with latest freetype if compiled to use the old CFF hinter. ]

Another odd fact: conversion of affected PDFs to SVG using poppler (either the new (0.91) option in Inkscape's PDF import dialog; or the command line tool from poppler (pdftocairo)) produces results where the outlined glyphs (from the original filled text) and the outlines from the stroke fit precisely, for all sizes.