Support LANGUAGE property parameter

[Zocker1999NET]

If I understand RFC 5545 correctly, it is allowed to supply multiple SUMMARY or at least multiple DESCRIPTION properties, each with a different LANGUAGE parameter. (RFC 9073 does explicitly allow this for the new STYLED-DESCRIPTION property.) Hence the following few lines should be valid:

SUMMARY;LANGUAGE=en:Friends Meetup
SUMMARY;LANGUAGE=de:Freundestreffen
DESCRIPTION;LANGUAGE=en:We will meet all our (new) friends!
DESCRIPTION;LANGUAGE=de:Wir werden alle unseren (neuen) Freunde treffen!

If I tested correctly, the current ICSx5 implementation does just silently accept the last DESCRIPTION or SUMMARY appearing.

IMO it could be useful to support filtering for the ones with the languages preferred by the user & primarily using that variant. With this, calendar publishers could provide a single calendar subscription for all their users, with a single link, containing the events in all languages.

(Though, in all honesty, I have not yet discovered one WebCAL client which does support selecting the preferred summary & description.)

[ArnyminerZ]

Hi, I have never seen this language tag, and I'm not sure if it's even supported by our icalendar parsing library (I think it should). But I find this very useful, and I'd love to have it implemented.

Just FYI, I've moved the discussion from ICSx⁵, because this has to be implemented first on synctools.

[ArnyminerZ]

I've done a quick test, and given a prop of type Description, this is valid:

val lang = prop.parameters.getParameter<Language>(Parameter.LANGUAGE)?.value

However, we are on the middle of a big refactoring work right now on the calendar processing, and I think it's not good to add new features. #108 is still under review, and some more will be needed until the refactoring is done for events.

Once this is done, I think this would be a great feature.

However Android doesn't support multi-lingual descriptions, so we'd have to find a workaround to store the other translations somewhere. Just want to let you know that this isn't as trivial as one might think. For ICSx⁵ this doesn't really matter, we can just take store the localized description (because ICSx⁵ is read-only); but for DAVx⁵ this is really important, otherwise events may be uploaded to the server with the localized descriptions removed.

I'm talking about description, but summary also applies to everything.

[ArnyminerZ]

To extend this, we don't actually store the calendar/contacts information anywhere, we store the collections (for DAVx⁵), and all the events/contacts/tasks are store in their respective providers (from the system). That's why we don't have control on how much data we can store, it's already predefined by Android, so we can't store everything we want.

[rfc2822]

As far as I know, the Android calendar provider doesn't support (multiple) languages. So for instance, there's only a TITLE (SUMMARY), which is a String. There's no possibility to store the language or even multiple summary values together with their languages. So we could only store it in a DAVx5-proprietary field, but then, which language do we use as the (one) Android event SUMMARY? And also calendar apps won't be able to show the other languages, so it won't be helpful for a user.

[ArnyminerZ]

which language do we use as the (one) Android event SUMMARY

I guess that the first supported language by the user's system preferences, or the first one given if none is available. But yeah, having so little control over it...

I'd say this is simply not supported by Android by design.

[rfc2822]

Yes, unfortunately …