# Sourcing Composites

**URL:** <https://forum.high-logic.com/t/sourcing-composites/4590>\
**Category:** FontCreator - Support\
**Created:** [February 26, 2015, 5:04pm UTC](https://forum.high-logic.com/t/sourcing-composites/4590 "2015-02-26T17:04:36Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Bhikkhu\_Pesala](https://forum.high-logic.com/user_avatar/forum.high-logic.com/bhikkhu_pesala/32/9411_2.png) [@Bhikkhu\_Pesala](https://forum.high-logic.com/u/Bhikkhu_Pesala)\
**Post date:** [February 26, 2015, 6:25pm UTC](https://forum.high-logic.com/t/sourcing-composites/4590/3 "2015-02-26T18:25:43Z")

</div>

The [Complete Composites](https://forum.high-logic.com/t/complete-composites/1164/1) Tutorial thread will tell you more, and [the PDF file](http://forum.high-logic.com/download/file.php?id=2038) linked to at the end of the thread goes into the technical details of how it works.

If some of your composites are blank or incomplete, probably the diacritics used to compose them are missing or empty.

Some use a combining overline, which will be absent for most users, but there should be a fallback glyph (the underscore character). If that’s also missing, then add it.

For exampe: g stroke is composed of lower case g + combing long stroke overlay (decimal code-point 822). If the font doesn’t contain that glyph, the underscore glyph is used instead (decimal code-point 95)

```plaintext
<Composite><!-- g stroke -->
<GlyphMapping>485</GlyphMapping>
	<Member id="1">
	<GlyphMapping>103</GlyphMapping>
		<UseMetrics>TRUE</UseMetrics>
	</Member>
	<Member id="2">
	<GlyphMapping>822</GlyphMapping>
		<GlyphMapping>95</GlyphMapping>
	</Member>

```

---

_[View the full topic](https://forum.high-logic.com/t/sourcing-composites/4590)._