Skip to content
Permalink
master
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Go to file
 
 
Cannot retrieve contributors at this time
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso8859-1">
<LINK REL=STYLESHEET HREF="fv.css" TYPE="text/css">
<TITLE>W1110</TITLE>
</HEAD>
<BODY BGCOLOR=white>
<Object type="application/x-oleobject" classid="clsid:1e2a7bd0-dab9-11d0-b93a-00c04fc99f9e">
<param name="Keyword" value="W1110">
<param name="Keyword" value="glyf">
</OBJECT>
<H1><A NAME="W1110"></A>Message: W1110</H1></div>
<HR>
<P><B><I>glyf</I>: Intersecting components of composite glyph</B></P>
<P>The glyph indicated in the validation log contains contours of glyph components that intersect (overlap). This type of glyph design introduces some ambiguity in terms of defining what is the 'inside' and 'outside' of a glyph shape, and may cause a rasterizer to reverse the overlapped portion. This problem is generally seen on older printers. Although Microsoft discourages this type of glyph design, for legacy reasons this overlap is allowed for composite glyphs.<BR><BR><IMG ALIGN="TOP" BORDER=1 SRC="intersection_component_whole_scaled.jpg">&#160;<IMG ALIGN="TOP" BORDER=1 SRC="intersection_component_detail_scaled.jpg"><BR><BR>The current implementation of the rasterizer as well as many legacy versions handle this exception and ensures that the overlap between components is filled.<BR><BR>Please note that for consistency and predictability across platforms and implementation of the rasterizer, composite glyphs with overlapping contours should be redrawn altogether as a single glyph.</P>
<P>For more information, see the <A TARGET="top" HREF="http://go.microsoft.com/fwlink?LinkID=10348">glyf table specification</A>.
</BODY>
</HTML>