Localization of time/date with FullCalendar's language files #17
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This enables support for time/date localization through FullCalendar/Moment's language files.
Here's an example (from
/examples/language.htm
):It's a requirement that the language file is loaded after booking.js but before initialization. Individual settings can still be passed to FullCalendar and have precedence over the language settings.
Text strings on the booking page are not currently translatable, still researching for a proper implementation (perhaps extend the FullCalendar/Moment format?)