### 30.1.2 Understanding how templates are named

Template files in your Mif2Go distribution have names that follow a certain pattern. Each name has a prefix that indicates the scope of the settings the template contains, followed by the type of template (config or macro):

Template name | Editable file name | Scope of settings
omsys.ini | local_omsys.ini | All Omni Systems projects
m2g_type.ini | local_m2g_type.ini | All Mif2Go projects
m2htm_type.ini | local_m2htm_type.ini | Mif2Go HTML and XML projects
m2rtf_type.ini | local_m2rtf_type.ini | Mif2Go RTF projects

Most general configuration templates and macro libraries use this naming convention.

| 30.1.1 Understanding how templates are organized |  | 30.1.3 Understanding how templates are chained together |