Skip to content

Conversation

@da4089
Copy link

@da4089 da4089 commented Feb 23, 2024

@da4089 da4089 added this to the v2.0 milestone Mar 19, 2024
@@ -1,5 +1,6 @@
from . import base

properties_allow_localization = ['NAME','SUMMARY','DESCRIPTION','LOCATION']
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PROPERTIES_ALLOW_LOCALIZATION = set('NAME','SUMMARY','DESCRIPTION','LOCATION') 
Comment on lines +104 to +107
if name in language_count:
language_count[name][lang] = language_count[name].get(lang, 0) + 1
else:
language_count[name] = {lang: 1}
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Either only line 105 and no if-statement at all, or change line 105 to

language_count[name][lang] += 1 

since you ensured that it exists in line 104

@da4089
Copy link
Author

da4089 commented Jan 3, 2025

For vCards, the current IETF solution to this problem is the use of the ALTID tag, as specified in RFC-6350 aka vCard-4.0.

However, as of v0.9.9 and v1.0.0pre, we don't yet support vCard-4.0. So far as I can see, RFC-2426 aka vCard-3.0 has no specified way of supporting more than one translated value for the same property. That said, it appears that the LANGUAGE tag is valid for any property.

For iCalendar, RFC-5545 specifies the LANGUAGE parameter. It's allowed on:

  • CATEGORIES (s3.8.1.2)
  • COMMENT (s3.8.1.4)
  • DESCRIPTION (s3.8.1.5)
  • LOCATION (s3.8.1.7)
  • RESOURCES (s3.8.1.10)
  • SUMMARY (s3.8.1.12)
  • TZNAME (s3.8.3.2)
  • ATTENDEE (s3.8.4.1)
  • CONTACT (s3.8.4.2)
  • ORGANIZER (s3.8.4.3)
  • REQUEST-STATUS (s3.8.8.3)

Note that no NAME property exists for iCalendar, nor vCard.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

3 participants