Team names

Team names

The <team_names> element defines the full list of team names that will be included in the final design output. Each <team_name> represents one complete name entry, split into up to three parts for greater layout flexibility.

XML structure

<team_names>
      <team_name
            name1="aa"           <!-- First column text -->
            name2="bb"           <!-- Second column text -->
            name3="cc"           <!-- Third column text -->
      /> 
      <team_name
            name1="dd"
            name2="ee"
            name3="ff" >
            <thread ... />       <!-- Optional: specific thread for this team name -->
      </team_name>
      <team_name
            name1="hh"
            name2="ii"
            name3="jj"
      /> 
</team_names>

Typical use

Use multiple <team_name> entries to produce a roster of names in a single run – perfect for:

  1. Sports teams
  2. Staff uniforms
  3. Group gifts

Key concepts

✅ Name columns

  1. name1, name2, and name3 specify sub-sections of a team name.
  2. They are concatenated together with spaces in the final lettering: Full Name = name1 + " " + name2 + " " + name3
  3. Common usage:
    1. name1 → First name
    2. name2 → Middle name
    3. name3 → Last name

Info
Splitting names allows per-column settings, like using larger lettering height for last names.

✅ Partial names

You can use only one or two of the sub-names. Example:
<team_name name1="Alex Johnson" name2="" name3="" />

✅ Individual thread

  1. Each <team_name> can optionally define its own thread.
  2. If no thread is specified, the default thread from <team_name_lettering> is used.

Example

<team_names>
   <team_name name1="John" name2="A." name3="Smith" />
   <team_name name1="Mary" name2="Beth" name3="Jones">
      <thread name="Gold" />
   </team_name>
   <team_name name1="Alex Johnson" />
</team_names>

  1. EWA design recipe
  2. EWA API methods overview
  3. EWA data packages overview