Localization, variables, and rules

Four related systems shape a respondent’s experience:

System	Responsibility
Translations	Select the respondent-facing strings for a language or locale.
Regional policy	Format and parse dates, times, date ranges, calendars, and hour cycles.
Variables	Derive reusable values from fields, variables, and supported functions.
Conditional rules	Change visibility, enabled state, required state, or value when conditions change.

Translation is not regional formatting

Spanish copy can still use an Australian time zone. A French locale can format dates without a French translation set. Configure and test the two separately.

Variables are reusable derivations

Variables keep an expression in one place. Dynamic-value insertion references them in supported titles, descriptions, labels, and other text.

Avoid storing a derived display value as a second respondent answer unless the business process truly needs it.

Rules react to state

Rules evaluate against form state and apply their target behavior. A hidden field should not stay required, because the respondent cannot then satisfy it. A computed value should not create a circular dependency.

Test the combination

For each published language and regional policy:

1. preview both branches of each important rule;
2. confirm derived text uses the translated surrounding copy;
3. enter dates near time-zone or daylight-saving boundaries;
4. navigate away and back;
5. use Test Save and inspect the serialized response.

Building these is covered in Use variables and rules and Configure settings and localization.