Tomas R.

I'd like to know what others think, but imo showing the same day in both calendars looks a bit confusing when you're selecting a range:  I prefer the old...

There is an [API](https://transifex.github.io/openapi/index.html#tag/Resource-Translations/paths/~1resource_translations/patch) for bulk updating translations, though for new strings we'd also first need to [create the resource string](https://transifex.github.io/openapi/index.html#tag/Resource-Strings/paths/~1resource_strings/post). Alternatively, maybe we could modify the PO files locally...

Yeah I think a fresh pull to temp directory would be the way to go. If we stick with the tx client we don't need to worry about transforming the...

Looks correct, though the compilation step (`indico i18n compile`) which turns the .po files into .mo files (for python, for js we create a json I think) is missing. It...

One unfortunate thing that happens when we move jinja code to react is that we lose the translations. This is because we have separate PO files for python, js and...

It is now allowed to select an interval with zero duration e.g. `12:00 - 12:00` which leads to this error (haven't dug into why yet):  Maybe we can keep...

> On an entirely separate note, if you're trying to express the concept of intervals through two time pickers, why not just use time + duration controls instead? Assuming that...

> I'm thinking a duration like '1.1 hours' would require a bit to much mental math for some people (e.g., me). I guess this comes from the difference in behavior...

Sorry I missed this notification :disappointed: The general consensus was that having two time pickers for the start and end times is better because people are more likely to be...

Since this *is* an actual name, I would also prefer to keep `Name` here. We can give it context to make it translatable separately from other instances of `Name` and...