Straightening out the language string situation in the JS calendar (bug 1455137)
The main thing this fixes, is that it causes the JS calendar to use ONLY the
new lang strings pieform_calendar_dateformat & pieform_calendar_timeformat,
for its formatting. These strings are in strftime() format, and are converted
into the JQuery Datepicker/Timepicker format by PHP (if we change to a different
calendar plugin in the future, we can change the PHP conversion function).
This fixes the bug where translators could break the calendar by changing the
JS format strings so they no longer matched the PHP format strings.
As a side effect of this change, I've also made it so that the help strings
are derived from the format string, and are translatable.
Reviewed: https:/ /reviews. mahara. org/5614 /git.nzoss. org.nz/ mahara/ mahara/ commit/ 43a6c846dd5c0d4 0106cba2a5d5353 aa6a60038a
Committed: https:/
Submitter: Robert Lyon (<email address hidden>)
Branch: 15.04_STABLE
commit 43a6c846dd5c0d4 0106cba2a5d5353 aa6a60038a
Author: Aaron Wells <email address hidden>
Date: Mon Aug 24 18:24:27 2015 +1200
Straightening out the language string situation in the JS calendar (bug 1455137)
The main thing this fixes, is that it causes the JS calendar to use ONLY the calendar_ dateformat & pieform_ calendar_ timeformat, Timepicker format by PHP (if we change to a different
new lang strings pieform_
for its formatting. These strings are in strftime() format, and are converted
into the JQuery Datepicker/
calendar plugin in the future, we can change the PHP conversion function).
This fixes the bug where translators could break the calendar by changing the
JS format strings so they no longer matched the PHP format strings.
As a side effect of this change, I've also made it so that the help strings
are derived from the format string, and are translatable.
behatnotneeded
Change-Id: I152962cc27f36f 93b51ee0327ed94 2fb089f7f5b