− | Several fields allow annual variants (documented in the table above). These work by prefixing <samp>_y{{t|year variant}}</samp> to the key, where the {{t|year variant}} is an incrementing number starting at 1 with no upper limit. For example, two entries <samp>set-up_y1</samp> and <samp>set-up_y2</samp> will alternate (<samp>set-up_y1</samp> in year 1, <samp>set-up_y2</samp> in year 2, <samp>set-up_y1</samp> in year 3, etc). If year variants are defined for a key, the original key is ignored (e.g. <samp>set-up</samp> will never be used if <samp>set-up_y*</samp> entries are defined). | + | Several fields allow annual variants (documented in the table above). These work by prefixing <samp>_y{{t|year variant}}</samp> to the key, where the {{t|year variant}} is an incrementing number starting at 1 with no upper limit. For example, two entries <samp>set-up_y1</samp> and <samp>set-up_y2</samp> will alternate (<samp>set-up_y1</samp> in year 1, <samp>set-up_y2</samp> in year 2, <samp>set-up_y1</samp> in year 3, etc). If year variants are defined for a key, the original key is ignored (''e.g.'', <samp>set-up</samp> will never be used if <samp>set-up_y*</samp> entries are defined). |