React-big-calendar: moment localizer ignores culture setting on time ranges

Created on 5 Apr 2016 · 4Comments · Source: jquense/react-big-calendar

See Lines #15 #16 on moment.js. 'h.mma' is always used and and always produces AM/PM regardless culture setting

Source

kromit

👍2

Most helpful comment

Without implementing the PR above one could apply the following formatters as a prop to the calendar:

formats={{
  eventTimeRangeFormat: ({ start, end }, culture, localizer) => (
    `${localizer.format(start, "LT")} - ${localizer.format(end, "LT")}`
  ),
  agendaTimeRangeFormat: ({ start, end }, culture, localizer) => (
    `${localizer.format(start, "LT")} - ${localizer.format(end, "LT")}`
  )
}}

krokofant on 3 Jul 2016

👍3

All 4 comments

This issue is a bit annoying

krokofant on 29 Jun 2016

It seems like _LT_ would work better than any other _h:mma_ variation. _LT_ is the localized format for time as specified in the MomentJS docs.

The localized version _L_ is used in the _dateRangeFormat_ method but not the _timeRangeFormat_ which this issue is about.

Any downside to changing this?

krokofant on 29 Jun 2016

Without implementing the PR above one could apply the following formatters as a prop to the calendar:

formats={{
  eventTimeRangeFormat: ({ start, end }, culture, localizer) => (
    `${localizer.format(start, "LT")} - ${localizer.format(end, "LT")}`
  ),
  agendaTimeRangeFormat: ({ start, end }, culture, localizer) => (
    `${localizer.format(start, "LT")} - ${localizer.format(end, "LT")}`
  )
}}

krokofant on 3 Jul 2016

👍3

Same as https://github.com/intljusticemission/react-big-calendar/issues/267 ?