The text output functions are called only for a device-managed surface (a device bitmap or surface), or for a GDI-managed surface if the driver has hooked the call in EngAssociateSurface. The graphic output primitives for text are:
GDI calls DrvTextOut to render a set of glyph's pixels at specified positions for text output. Many of the DrvTextOut capabilities are defined with the GCAPS bits of the DEVINFO structure returned by DrvEnablePDEV.
The input parameters for DrvTextOut define two sets of pixels, foreground and opaque. The driver renders the surface to provide the following results:
1.The opaque pixels are rendered first, with the opaque brush.
2.The foreground pixels are then rendered with the foreground brush.
Each of these rendering operations is performed in a clip region. The pixels outside the clip region cannot be affected.
The driver must render the surface so opaque pixels are calculated and drawn on the surface first with an opaque brush. Then foreground pixels are calculated and rendered with a foreground brush. Each of these operations is limited by clipping.
Foreground and opaque pixels make up a mask through which color is brushed onto the surface. The glyphs of a font do not, in themselves, have color. The foreground set of pixels is defined as the union of the glyphs' pixels and the pixels of certain extra rectangles used to simulate strikethrough or underline. Opaque pixels are defined by opaque rectangles.
DrvTextOut selects the specified font using a pointer, pfo, to query the current FONTOBJ. This process can include downloading a soft font or a font substitution, or any other font optimizations necessary for the device.
If a driver has scalable fonts, it should call FONTOBJ_pxoGetXform for the current FONTOBJ to return the notional-to-device transform for the associated font. This is required for a driver-supplied font. Notional space is the design space of the device font. For example, PostScript fonts are defined in 1000-by-1000 unit character cells. Most of the metrics returned in the IFIMETRICS structure are converted to notional space, which is why the notional-to-device transform is necessary.
The graphics engine queries the driver by calling DrvGetGlyphMode to find out how it should internally cache its font information. It can cache individual glyphs as bitmaps, cutlines, or neither (the proper choice for device fonts).