Glyph Outlines in Trace Driver

Allen Blaylock <[email protected]>
Newsgroups gmane.comp.printing.ghostscript.devel
Message-ID <[email protected]>
Hello,

The text_begin function has a gx_path which the documentation notes to define the path where the character outline is to be appended. I have the trace driver print that value out, and then call glyph_outline on the font. I also have the font stroked which presumably dumps out something similar if not the same as the glyph outline. The text is has the operation TEXT_FROM_STRING so there may be multiple glyphs being processed during each text processing operation. 

As an example first time the text_begin function is called the path variable passed in contains (6.62891 82.3711 moveto) and the first element of the path returned by glyph_outline is (204 -256 moveto) with all subsequent path elements having points of approximately the same value. The next time text_begin is called a similar move to is executed the passed in path variable is approximately the same while the first element of the path returned by glyph_outline is (5927 1.05166e+006 moveto) with all subsequent path elements having points of approximately the same value.

Why is there such a large difference in the magnitudes of the path values between glyph outlines? 
How would one transform the glyph outlines into the current coordinate space?
Is text_begin the correct place to be doing this kind of operation?

A full output of the trace output can be found here: 
http://pastebin.com/y5UXCEWQ
And the input file:
http://filebin.ca/250Fnqs1hm3a/Untitled-7.pdf
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.