AI Catalog Text Simplification (with Flory)

TL;DR

• Working with Agent 6027 on simplifying and de-duplicating AI catalog text.
• Tried parameterizing text with an item type variable in a string template, but this breaks translations since the translator generates full strings at once in the POT file.
• Word order and gender mismatches (e.g., French masculine/feminine) can occur when a variable is inserted at runtime.
• Decided to keep distinct translation blocks for agents and flows, exported from one file, plus a build messaging function for separate pages and duplicated strings where needed.
• By afternoon, the work was in good shape - renamed everything and left notes on changes that were reverted, with Agent 6027 as reviewer.

Translation Template Problem

I’ve been working on text updates with Agent 6027, trying to simplify and de-duplicate text. We explored parameterizing text using an item type variable in a string template. However, this breaks translations because the translator procedure generates complete translated strings in one shot inside a POT file. The string template syntax is embedded in the translatable string, so if you put in a noun for the variable, the translator can’t run again on it and will just insert the variable at runtime. Even if you get a correctly translated word, it won’t necessarily match the rest of the sentence, since word order and gender may differ between languages - for example, in French, a procedure that would be feminine but was already translated as masculine would mismatch. So we need to keep distinct translation blocks for agents and flows, exported from one file to be consumed across components, along with a build messaging function that allows exporting separate pages and duplicating strings where necessary.

Status Update

The simplifying of text strings in the AI catalog is in good shape. I have Agent 6027 as the reviewer. I’ve renamed everything and left notes on changes that were reverted to the correct thing.