The names of the paragraph styles that generate single-row tables follows a specific naming convention that has to be respected.

A name, such as tb01a___SC4, consists of the following parts:

1.“tb” prefix that marks those styles as the styles which generate the style-based single-row tables. This prefix is not mandatory, nor is it controlled by the scripts, but it is recommended to keep it for coherency should you add more similar styles.

2.“01” prefix allows you to have more tbxx styles (as the style names within the same library need to be unique). Examples: tb01a___SC4, tb02a___SC4 and so on.

3.“a” suffix that allows you to visually ‘group’ variants of similar tables together. Examples: tb01a___SC4, tb01b___SC4 are two variants of the same table structure.

4.“___” (three underscores). This is mandatory. The software searches for the three underscores in the name of a paragraph style, and if it finds them, it treats such paragraph styles as a ‘special’ style for the style-based single-row tables. There’s a global variable glbTabNameDelim that you can add to the EditorialConfig if you want to use a different delimiter.

5.“S” marker that stands for a “single-line” table. When the software encounters the S marker after ___, it activates the special handling for such tables in the InsTabNotGenuineTbl (called from InsTab script).

6.“C” or “c” marker that stands for “columns”. The “C” tells the software that all the columns are generated by the tab marker, while the “c” tells that some columns are generated with the @ Bell marker (in the case of dots that need to spread evenly from left to right). The insertion of TAB or Bell is handled by the InsTabNotGenuineTbl script.

7.Number after the C marker tells the software how many columns are allowed/required for that table.

Therefore, looking at the style named as tb01a___SC4, we know it’s the first variant (a) of its group (01) and that it caters for a single row table (S), with max 4 columns (C4), and all the columns are generated by the tab marker (uppercase C).

Should you create more styles, follow the same convention.