I suspect, that this is potentially caused by bootstrap that was done in English - I only found out later, that you can change locale for bootstrap. Is there a way to change this after bootstrap?
Have now tested with I18n.enableVerboseLocalizationSession():
it confirms that first screenshot from above is filled from translation keys (therefore translated), while the second screenshot have hardcoded English value and no keys are added by verbose translations…
No, it’s not hardcoded. It uses different locale keys depending on how you access the page. I already have a fix for it, but didn’t want to commit it before the release of 2.2.