A Polish date needs a sentence, not just twelve translated month names

A catalogue team can translate every month name correctly and still produce an awkward date. The problem appears when the application treats a month heading and a date within a sentence as interchangeable. A language reviewer may approve “marzec” in a calendar heading and then find the same form inserted after a day number, where the expected construction is different.

This guide uses a fictional quotation register. Its dates and references are examples, not statements about a client's system. The useful investigation separates the stored calendar date, the context in which it appears and the person who approves the surrounding wording.

Start with the value before reviewing the label

Quotation Q-416 has an agreed document date of 5 March 2026. The source record stores the date as a date, with year, month and day. A March folder heading and a line displaying the complete document date both refer to it. Neither presentation should become a second independent date that an editor must maintain.

The heading can use the stand-alone month name “marzec”. A full Polish date uses “5 marca 2026”. In an English edition, “5 March 2026” may suit the chosen house style. The source day has not changed; the grammatical context has. A table of twelve translated labels cannot safely supply every placement merely by joining a day number and one label.

Keep the example narrow. A different sentence may require other wording. The qualified Polish reviewer should approve complete messages and representative dates, including any surrounding preposition. A date-formatting library can produce a locale-sensitive date; it cannot approve every sentence in which that date is embedded.

Locate the assembly that introduced the error

Suppose the page uses the correct formatter, but an emailed quotation summary builds its date by concatenating the day with a translated month array. The public page can pass review while the receiving message remains wrong. Correcting a stylesheet or the page's translation entry would miss the source of the discrepancy.

Inventory the places where Q-416's document date appears: the quotation page, downloadable summary, office notification and exported register. For each, record whether the value is formatted from the structured date or copied from an already formatted string. A copied phrase can retain a previous locale or context even when the original data is sound.

The repair should give each context an explicit presentation rule. A calendar heading asks for a month heading. A complete document date asks for a complete date. An export intended for another application needs an agreed machine-readable representation, rather than a decorative phrase whose interpretation depends on the recipient's language settings.

Avoid introducing an unrelated time conversion

A document date can be a calendar fact rather than an instant. Do not make it yesterday or tomorrow by converting an unnecessary midnight timestamp through the viewer's time zone. If the business actually means the time a quotation was issued, record that separate fact and its presentation rule. The question is semantic before it is technical.

JavaScript's international date-formatting interface supports a locale and explicit options. The developer still needs to decide how the underlying date is represented, which time zone applies when an instant is involved and which output components the task needs. Inspect the chosen runtime's result with the exact production locale data; do not assume a demonstration establishes every browser's behaviour.

Review the corrected chain

Use Q-416 beside dates from several other months, a year boundary and a date without a time. Check the complete page sentence, the heading, the notification and the exported value. Include an English-language reader viewing the Polish edition so that browser language does not silently override the edition selected by the site.

Ask the reviewer to approve a placement list, not a screenshot of one attractive date. Record the source value and the actual result at each placement. If an email template or export remains outside the agreed work, identify it expressly so the visible page fix is not mistaken for a complete correction.

The acceptance result is a consistent date with language appropriate to its context. It does not require replacing the entire catalogue or translating unrelated material. Content and language work can establish those responsibilities, while the project brief helps name the task and the evidence needed for review.

For implementation background, consult Intl.DateTimeFormat. The example wording still needs the project's Polish-language reviewer.