| 1 |
--- |
| 2 |
layout: default |
| 3 |
title: Unit 8 |
| 4 |
nav_order: 80 |
| 5 |
parent: Graphite Tutorial |
| 6 |
grand_parent: Developers |
| 7 |
--- |
| 8 |
|
| 9 |
{: .tut-nav-bar } |
| 10 |
| [◀ Unit 7: Glyph attributes](graide_tutorial7) | [▲ Contents](../graide_tutorial#contents) | [Intermission ▶](graide_tutorial8a) | |
| 11 |
|
| 12 |
# Unit 8: Slot attributes |
| 13 |
|
| 14 |
## Discussion |
| 15 |
|
| 16 |
Unlike glyph attributes, which are constant for every instance of a given glyph, the values of slot attributes may differ for each instance of a glyph. It is the glyph’s role as a slot within the context of the entire stream of text that determines the values of its slot attributes. |
| 17 |
|
| 18 |
Slot attributes are set within rules. Most slot attributes are system-defined (and will be discussed further on), but there is also a set of user-definable (that is, programmer-definable) slot attributes, called user1, user2, etc. More meaningful names can be given to the user-definable attributes using #define. |
| 19 |
|
| 20 |
Slot attributes can be tested in the context of the rule in the same way that glyph attributes are. |
| 21 |
|
| 22 |
{: .tut-nav-bar } |
| 23 |
| [◀ Unit 7: Glyph attributes](graide_tutorial7) | [▲ Contents](../graide_tutorial#contents) | [Intermission ▶](graide_tutorial8a) | |