den | 16 January 2026

Version 0.2.0 implemented a major architectural restructure of the Paratext Diagram Labeler, that enables maps from multiple collections to make use of the same labels without “stepping on each other’s toes”, even handling different label variations. For example, in the previous SMP1 system, the label “Way of Shur” was associated with the Biblical term for “Shur”, but then a Biblica map that needed to label a place as “Shur” would have conflicting use of this term. The restructure allows both maps to draw from the term for “Shur”, ensuring it’s spelled consistently for both, without conflict.

Key architectural changes:

  • The Labeler now maintains a dictionary for each project, specifying the text for each label. Maps/diagrams from all collections use the same dictionary entries, so a road labelled “To Jericho” on a Biblica map will be able to reuse the text for “To Jericho” from an SIL map.
  • Most labels are defined as containing one place-name, such as “Jericho”. However, it’s possible for a label to contain more than one placename, such as “Jebus (Jerusalem)”, or no place-names, such as “Paul’s Second Journey”.
  • Each place-name may have one or more Biblical terms associated with it, and each term may have a set of Scripture references in which the term is expected to be found. For example, Jericho has both a Hebrew term and a Greek term. The Labeler allows you to treat these as a joined unit, ensuring that you use the same spelling for Jericho in both the Old Testament and the New Testament.
  • Also stored with each label on each map is a setting of Sync, Override, or Omit.
    • Sync means that if the dictionary value is later updated, this label should be updated, too.
    • Override means that this label’s value is locked, unlinked from the dictionary value.
    • Omit means that this label should be omitted from the map.
  • Labels containing Scripture references (common on Biblica maps) can be auto-generated from the Paratext project’s Scripture Reference settings.

Version 0.2.1 added further improvements:

  • Added support for other number systems. Exporting to IDML or MAPX will even update numbers that are not data merge fields. e.g. Scale markers.
  • Added support for specifying rules for tagged label templates. e.g. to#, q#
  • Comparing labels to renderings is now normalization-insensitive.