Calendar invitation: use system default instead of sender's language as fallback #12020
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…as fallback Signed-off-by: Georg Ehrke <[email protected]>
rullzer
approved these changes
Oct 25, 2018
rullzer
requested review from
MorrisJobke,
nickvergessen,
blizzz and
icewind1991
|
Backport this or not? |
cc @georgehrke |
|
extremely minor bug, so this is enough for 15 imo |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
fixes #11795
@rullzer This (partly) fixes #11795. It's better to use the instance language as a fallback, rather than the sender's language.
If there is a
LANGUAGEparameter set for an Attendee in the calendar data, then it will always use that language. So to use the correct language of another user, this needs a modification in the calendar app (that's already planned).