A Syrian reader sees تشرين الثاني where a reader in Cairo or Riyadh sees نوفمبر. Both are November. Which set your app prints comes down to a single locale tag, and plain Arabic, ar, picks the other one.
The Syriac month names are the Arabic names for the twelve Gregorian months as used in Syria, Lebanon, Jordan, Palestine and Iraq, from كانون الثاني for January to كانون الأول for December. They label exactly the same months as يناير to ديسمبر, the set used in Egypt and the Gulf, so the name changes and the date never does.
They go by several names. In English you will see Syriac, Levantine or simply Syrian month names, and in Arabic الأشهر السريانية or الأشهر الشامية. Whatever the label, a Syrian user expects them in every date the app shows, and an app that prints يناير instead reads as if it was made for another market.
Software treats the two sets as a property of the locale. Unicode CLDR, the locale data that browsers rely on, ties the Levantine names to Arabic as written in Syria, ar-SY, and ties يناير and فبراير to plain Arabic, ar. So the month a user sees depends on the locale tag your code passes, not on the language alone.
| Name | Notes | |
|---|---|---|
| English | Syriac month names | Also written Levantine month names or Syrian month names. |
| Modern Standard Arabic | الأشهر السريانية | Also الأشهر الشامية. The other set, يناير to ديسمبر, is the one plain ar prints. |
| Also heard in Syria | شهر 1، شهر 2 ... | People also give the month by its number, as in شهر 11 for تشرين الثاني. |
| In code or standards | ar-SY | The locale tag that selects these names in browsers. Flutter's package:intl needs them registered by hand. |
| Levantine name | Egyptian and Gulf style | Month |
|---|---|---|
| كانون الثاني | يناير | 1, January |
| شباط | فبراير | 2, February |
| آذار | مارس | 3, March |
| نيسان | أبريل | 4, April |
| أيار | مايو | 5, May |
| حزيران | يونيو | 6, June |
| تموز | يوليو | 7, July |
| آب | أغسطس | 8, August |
| أيلول | سبتمبر | 9, September |
| تشرين الأول | أكتوبر | 10, October |
| تشرين الثاني | نوفمبر | 11, November |
| كانون الأول | ديسمبر | 12, December |
Take a clinic booking app in Homs that confirms an appointment for 5 January 2026. Built in Flutter with the locale ar_SY and nothing else, the confirmation uses the يناير set, because package:intl 0.20.2 has no ar_SY data and quietly falls back to plain ar. Once the Syrian names are registered with initializeDateFormattingCustom, the same call, DateFormat.yMMMMd('ar_SY'), prints 5 كانون الثاني 2026. We tested both sides on 16 November 2026: before registering, a November date came out as نوفمبر, and after, the Levantine name appeared.
The web version of the same app gets there with less work. Intl.DateTimeFormat("ar-SY", { dateStyle: "long", timeZone: "Asia/Damascus" }) turns 16 November 2026 into ١٦ تشرين الثاني ٢٠٢٦, while plain ar formats that date as 16 نوفمبر 2026. The digits changed too: ar-SY writes Arabic-Indic digits unless you add -u-nu-latn to the tag.
DateFormat.localeExists('ar_SY') returns false and dates fall back to ar with no warning. Register the Syrian names with initializeDateFormattingCustom; after that, Material's own labels use them as well, which our test checks with formatMonthYear.كانون الثاني (January), شباط (February), آذار (March), نيسان (April), أيار (May), حزيران (June), تموز (July), آب (August), أيلول (September), تشرين الأول (October), تشرين الثاني (November), كانون الأول (December).
Browser output checked with Node 24 (ICU 78), and Flutter output with package:intl 0.20.2, both on 16 November 2026. Locale data changes between versions, so test on the devices your users have.
Send us a screenshot of a date your app prints. We will tell you which setting produced it and how to fix it.