o .j@sddlZddlZejdddgddZejdgdd d Zejd d d gddZddZddZejdddgddZ ddZ ddZ dS)N)fieldexpected_value)PRODIDu+-//Plönë.org//NONSGML plone.app.event//EN)z X-WR-CALDESCu!test non ascii: äöü ÄÖÜ €cCs$|j}||d|ksJdSNzutf-8)calendar_with_unicodeto_icaldecode)rr calendarscalr R/home/thesage/.local/lib/python3.10/site-packages/icalendar/tests/test_encoding.py(test_calendar_from_ical_respects_unicodesr ) test_inputrr))event_with_unicode_fieldsSUMMARYu!Non-ASCII Test: ÄÖÜ äöü €)r DESCRIPTIONu>icalendar should be able to handle non-ascii: €äüöÄÜÖ.)rLOCATIONu Tribstrül)%issue_64_event_with_non_ascii_summaryruåäö)!issue_64_event_with_ascii_summaryrabcdefcCs&||}||d|ksJdSr)rr)rrreventseventr r r %test_event_from_ical_respects_unicodesr)rexpected_output)2issue_101_icalendar_chokes_on_umlauts_in_organizeru acme, ädmin)event_with_unicode_organizeruДжон ДоуcCs||djd|ks JdS)N ORGANIZERCN)params)rrrr r r test_events_parameter_unicoded(s rcCsJ|jddd}|tdddddd }|jjrJ||ks#Jd S) wIssue #237 - Fail to parse timezone with non-ascii TZID see https://github.com/collective/icalendar/issues/237 VEVENTrDTSTARTi zAmerica/Sao_PauloN)4issue_237_fail_to_parse_timezone_with_non_ascii_tzidwalkdecodeddatetimeerrors)r in_timezonestartexpectedr r r /test_parses_event_with_non_ascii_tzid_issue_2375s r/cCs|jddks JdS)r tzidu(UTC-03:00) BrasíliaN)issue_237_brazilia_standard) timezonesr r r 2test_parses_timezone_with_non_ascii_tzid_issue_237Asr3 timezone_namestandarddaylightcCs&|j|ddd|ksJdS)r rTZNAMEu Brasília N)r1r()r2r4r r r 4test_parses_timezone_with_non_ascii_tzname_issue_273Hs r8cCsH|jdD]}t|jdksJd|jdd}|ds!JqdS)z6 Test if error messages are encoded properly. veventzNot the right amount of errors.rz+Content line could not be parsed into partsN) broken_icalr(lenr+ startswith)r rerrorr r r test_broken_propertySs r?cCs,|jdD] }t|jdksJdqdS)zL Test if we support base64 encoded binary data in parameter values. r9rzGot too many errorsN) x_locationr(r<r+)r rr r r test_apple_xlocation]srA) r*pytestmark parametrizer rrr/r3r8r?rAr r r r s6