# An SSIM Month Read in the Wrong Language

Industry: Aviation

### An SSIM Month Read in the Wrong Language

A schedule import runs on a server whose default language is Spanish. The file says 01JAN26. What does the import read?

The usual approach:
```js
// The naive approach: read the month name through the locale
import { parseDateWithPattern } from "@northguild/gmt/plain/parse";

// The import asks the platform for its language, then hands it to the parser
const locale = "es-ES"; // what the platform reports on this server

parseDateWithPattern("01JAN26", "ddMMMyy", locale, { yearWindow: 2000 });
// "" — JAN is not a Spanish month
parseDateWithPattern("01ENE26", "ddMMMyy", locale, { yearWindow: 2000 });
// "2026-01-01" — ENE is Spanish, and no SSIM file writes it
```

The three letters of an SSIM month are a code in English, whatever the language of the machine reading the file. Code that hands the platform's language to a pattern parser gets Spanish month names on this server, so it rejects every January in the file and accepts a word the format never writes. On a server set to English the same code works, which is why it passes in testing. \`parseSsimDate\` reads the letters from a constant table and never asks for a language, so the answer does not depend on where it runs.

With GMT:
```js
import { parseSsimDate } from "@northguild/gmt/aviation/parse";

parseSsimDate("01JAN26", { yearWindow: 2000 });
// "2026-01-01"
parseSsimDate("01ENE26", { yearWindow: 2000 });
// ""
```

The fix is to treat the letters as a code, not a word. See [Aviation: Message
Times](/gmt/guides/industries/aviation-message-times/#why-the-month-letters-bypass-the-locale) for the
reasoning, and [Aviation mistakes](/gmt/mistakes/aviation/) for the others that come with it. The
[SSIM Date Reader](/gmt/tools/ssim-date-reader/) shows the same text read both ways.
