Alphanumeric Text Patterns

CODE/UoM abstraction lets a translation memory ignore differences in alphanumeric part codes (such as product SKUs and serial numbers) and units of measure (such as 3.3V, 224mA, 10Ω) when matching segments. Segments that differ only by those values collapse into a single TM entry and score as a 100% match rather than separate fuzzy matches.

Audience and Permissions

Role	What they can do
Account Admin	Enable or disable the toggle at the organization unit level. Projects inherit the setting when the TM is bound.
PM	Enable or disable the toggle per TM on a specific project.
Vendor	No configuration access. The editor shows source highlights and target underlines for detected CODE/UoM values automatically when the feature is active for at least one project TM.
TM Admin	View `[CODE]` and `[UOM]` placeholders and substituted values in TM search results. The toggle also appears, and works, in project-less TM fuzzy searches.

Key Concepts

Term	Meaning
Part code (CODE)	An alphanumeric identifier such as a product SKU, part number, or serial code. Examples: `ADS9219EVM`, `TCAN4572EVM`, `B7-202`.
Unit of measure (UOM)	A numeric value followed by a unit. Examples: `3.3V`, `224mA`, `10Ω`, `1A`.
`[CODE]` / `[UOM]` markers	Canonical placeholders stored in the TM instead of the literal value. `[CODE] GUI software` matches any segment with a code followed by "GUI software".
Substitution	At search or read time, the literal CODE/UoM values from the current segment are reinserted into the stored markers so the translator sees the correct value.
Literal override	When a translator intentionally changes a code or measure value in the target, wxrks stores the exact literal pair as a separate TM entry so future exact recurrences return the translator's choice verbatim.
Indexed marker	A marker like `[UOM:2]` that records which source value a target slot represents. Used when a translation reorders values (e.g., "min 1A ... max 2A" translated as "Máximo 2A e mínimo 1A").

Enabling CODE/UoM at the Organization Unit Level

From the main navigation, go to Organizations > Organizational Units.
Click the organization unit you want to configure.
Open the Context tab.

In the CODE/UoM column, turn on the toggle for each TM that should ignore part codes and units of measure when matching.
Hover over the ⓘ icon next to the toggle to read the explanation: "Ignore differences in part numbers and units of measure when matching. Projects inherit this when binding the TM."

Changes save automatically after a short delay. Projects that bind this TM later inherit the CODE/UoM setting.

Enabling CODE/UoM on a Project

Open the project and go to its Settings area.
Locate the TM list under the Context tab section.

In the CODE/UoM column, turn on the toggle for any TM where you want CODE/UoM abstraction active.
Hover over the ⓘ icon next to the toggle to read the explanation: "Ignore differences in part numbers and units of measure when matching."

The toggle takes effect on the next segment confirmation against that TM. Already-stored entries are unaffected — only new confirmations are stored with [CODE]/[UOM] markers.

What Translators See in the Editor

Source Text Highlighting

When a project TM has CODE/UoM enabled, the source text shows persistent, non-editable highlights:

Orange dotted underline on alphanumeric part codes.
Green dotted underline on units of measure.

These highlights appear as soon as the segment loads and remain visible at all times. The text underneath is still normal, editable text — the highlight is purely visual.

Target Text Underlines

When the target translation contains a value that matches a CODE or UOM value detected in the source, the editor adds a colored underline in the target:

Clicking or navigating to an underlined value opens a popover with the type label (Tm-code or Tm-uom) and the message: "Code/measure value from the source — double-check it."

These underlines are read-only reminders. They are not spellcheck corrections and have no interactive replace/ignore buttons. They disappear automatically as soon as you edit the target text.

Auto-Correction Warning on TM Suggestions

When the backend cannot auto-correct a CODE/UOM value for a TM suggestion (because the number of markers in the stored entry does not match the number of values in the current source), a warning triangle appears on that suggestion in the TM panel:

Hovering over the triangle shows: "Code/measure value could not be auto-corrected for this match — it may still show a placeholder or a value from a different segment. Check it before confirming."

The translator should verify the target text manually before confirming if this warning appears.

What TM Admins See in Search Results

When searching a TM that has CODE/UoM enabled, the results table shows a legend bar when markers or detected values are present:

[SCREENSHOT PLACEHOLDER: TM search results page with the legend bar visible, showing the orange [CODE] chip labeled "alphanumeric code" and the green [UOM] chip labeled "unit of measure"]

[CODE] placeholders appear with an orange background. Hovering shows: "Placeholder for an alphanumeric code — matches any code value when searching."
[UOM] placeholders appear with a green background. Hovering shows: "Placeholder for a unit of measure — matches any measure value when searching."
Substituted values (the actual codes and measures from your search query) appear with the same orange or green background. Hovering shows: "Detected in your search as an alphanumeric code" or "...as a unit of measure."

displayText vs stored text

The search results table shows a substituted preview of each stored entry:

What you see in the table: If your query contained CODE/UOM values, they are reinserted into any matching [CODE]/[UOM] markers so you see a readable preview (e.g., searching for ADS9219EVM GUI software displays Software GUI ADS9219EVM instead of Software GUI [CODE]).
What is stored in the TM: The actual stored text uses [CODE] and [UOM] markers. The edit modal always opens the stored form — you cannot accidentally save a substituted value back to the TM.

Important Behavior and Edge Cases

One canonical entry per shape: When the same canonical text (e.g., [CODE] GUI software) is confirmed from different source documents, wxrks creates only one stored TM entry and updates it in place. The first confirmation's context is preserved as the 101% match anchor.
Translator overrides are preserved: If a translator intentionally uses a different code or measure in the target than the source, wxrks stores the exact literal source-target pair as a separate entry. Future exact recurrences match this literal entry and return the translator's choice verbatim.
Reordered multi-value targets: When a translation reorders multiple UOM values (e.g., "min 1A / max 2A" becomes "Máximo 2A / mínimo 1A"), wxrks stores indexed markers ([UOM:1], [UOM:2]) so substitution restores the correct value in each position.
Compound values: Values joined by a / (e.g., 224mA/448mA) are treated as separate UOM spans that share a group, so positional pairing within the group is safe. Each part is its own [UOM].
The toggle is per TM: A project can have one TM with CODE/UoM on and another with it off. When both are writable, canonicalized entries go to the opted-in TMs. Non-opted-in TMs receive the literal text as always.
Pre-existing TMs: A TM that already has segments stored before the toggle was enabled will contain literal values, not markers. Those older entries are not retroactively canonicalized. Only newly confirmed segments are stored with [CODE]/[UOM] markers.

Troubleshooting

Symptom	Likely Cause	What to Do
No orange/green highlights appear in the editor	The project's TM does not have the CODE/UoM toggle enabled.	Check the project's TM settings or the org unit's TM settings and turn on the toggle.
A TM suggestion shows a `[CODE]` or `[UOM]` placeholder in the target instead of the actual value	The backend could not auto-correct the value (marker/value count mismatch).	Look for the warning triangle on the suggestion. Manually type the correct code or measure before confirming.
Multiple duplicate TM entries for the same canonical text	The TM was confirmed before the fallback de-duplication was active, or from different contexts.	Manually clean duplicates in the TM admin interface. New confirmations will reuse the first entry going forward.
A compound value like `224mA/448mA` is only partially highlighted	Offsets from backend substitution are used directly, so highlights should be consistent.	If a highlight mismatch persists, it may be a display artifact — verify the stored text in the TM search edit modal.

Quick Reference

Action	Path
Enable for all projects in an org unit	Organizations > Units > [unit] > TM tab > CODE/UoM toggle
Enable on a specific project	Project > Settings > TM section > CODE/UoM toggle
See source CODE/UoM highlights	Open any segment in the editor — highlights appear automatically
See TM search placeholders	TM > Fuzzy Search (or TM detail page) — legend and colored markers appear when present
Check for auto-correction warnings	Look for a warning triangle on TM suggestions in the editor sidebar