03/04 is well formed: you still do not know which date the message promises

Ask which date it represents before translating

In the fictional message Your appointment is on 03/04/2027, English alone does not establish whether the appointment is 3 April or 4 March. Do not choose a date because the JSON is valid or the sentence sounds natural. Confirm the convention and day with the message’s source, then translate a date that has actually been defined.

The W3C date guide explains regional ambiguity in numeric dates and suggests making the month explicit. Microsoft’s documentation also distinguishes regional day, month and year ordering. Consulted on 25 October 2026; neither confirms our invented appointment.

A valid resource with an unresolved decision

Assume this example file:

{"appointmentMessage": "Your appointment is on 03/04/2027"}

The key identifies the message, not the date order. “Tu cita es el 03/04/2027” retains the ambiguity. “Tu cita es el 3 de abril de 2027” removes it only if that date is confirmed; otherwise it introduces invented precision.

Ask the author or consult the authorised record behind the text without publishing real appointment data. For this example, we now stipulate that the author confirms 3 April 2027. We can then review:

{"appointmentMessage": "Tu cita es el 3 de abril de 2027"}

If confirmation instead said 4 March, that is the month the message should contain. This is not a stylistic choice between two dates; first obtain the missing fact.

Add useful context before approval

In your review, make clear which date was confirmed and where you checked it. If the resource inserts the date through a variable, do not replace it with a fixed appointment: ask the product maintainer how that value is formatted. Both JSON snippets here are static demonstrations, not a proposal to change your application’s data format.

Iria documents local JSON/RESX projects with context, RESX comments, memory and revision workflows. Its official brief states that structural checks do not establish meaning or translation quality. We do not attribute an appointment or regional-convention verifier to them.

Finish with the fact, not an assumption

Check that the final text contains the confirmed month, year and the appointment the source intended. If confirmation is still missing, keep the concrete question open instead of approving an intuitive guess.

Weblate and Crowdin describe other localisation editors, consulted on 25 October 2026. Their controls are not transferred to Iria, and their handling of this example was not tested. Review Studio’s published capabilities and Iria installers for local Windows translation: it is a paid product with documented licence validation and model requirements.