// the following is to inform that "%s" is to be the first day of week // %s will be replaced with the day name. Calendar._TT["DAY_FIRST"] = "Display %s first"; // This may be locale-dependent. It specifies the week-end days, as an array // of comma-separated numbers. The numbers are from 0 to 6: 0 means Sunday, 1 // means Monday, etc. Calendar._TT["WEEKEND"] = "0,6";
Depending on the language, Jira will include a different calendar language file. For Japanese this is calendar-ja.js. Both Jira 3.10 and 3.11 had these properties missing in their Japanese language files. We’ve cleaned up all of this for 3.12 such that the language files now include the properties above.
So how did things work in Jira 3.10?
There was a nice little hack at the end to add the required properties if they hadn’t been set yet.
Now the fact that this was defined in header.jsp meant that this was loaded on every single page in Jira. We introduced a lot of performance improvements to page load times in Jira 3.11, which resulted in the calendar being converted to a web-resource that could be included on demand. In order to do so, we created a calendar-language.jsp (mapped from calendar-language.js via web.xml) that would dynamically include the correct calendar-[LOCALE].js file depending on the language set in Jira:
At least only Japanese seems to be affected by this bug, as it is the only language that doesn’t explicitly set WEEKDAY and DAY_FIRST in its calendar_ja.js file. This bug has now been fixed for Jira 3.12 and all the little hacks have been cleaned up properly.