In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

This was using the implicit bool conversion rather than the intended
pointer comparison.

If both timezones differ widely, we can otherwise end up with the wrong
date here, and therefore not find anything.

This is needed to model cancellations, a currently unfortunately widely
needed feature. This requires a few changes to our enum (de)serialization
to be compliant with JSON-LD. And due to this having a default value it
causes quite some changes in the test files, adding the new property.

This does not actually make use of the property yet, besides from parsing
both the new and legacy forms from JSON-LD.

This particularly increases UIC code mappings in IT and ES that were
meanwhile added upstream.

GIT_SILENT: Prepare 5.14.0 beta1. Update ecm as 5.67.0 is broken see 417396. 5.68 will be release in 2 days. But dependancy freeze is tomorrow.

Those are types I found while browsing the internet for car dealerships, movie theaters, and various retail stores.
Theoretically we could map all the stores to Store and then have e.g. p-b-i indicate them differently but
since none of the more specialized types have any additional properties, just mapping all of them
to LocalBusiness should be sufficient for showing name, address, and contact data.

Differential Revision: https://phabricator.kde.org/D27911

This cleanly separates VDV specific semantics from general BER decoding,
and cleans up the various incomplete/adhoc BER decoding hacks in the VDV
code.

The previous implementation was driven by how this was implemented for VDV,
the way this is done now doesn't require the parent context anymore.

Needed by the VDV ticket parser.

This will replace various incomplete adhoc solutions for this in the VDV
ticket parsing. It will also be helpful for decoding at least parts of SBB
and Thalys ticket codes.

This currently only does the bare minimum, proper type decoding and
recursing into nested structures would also be useful, as well as support
for built-in primitive type content.

This is taken from the KMail plug-in, but is also needed for PBI.

Most of the work is already done by the JSON-LD generic extraction, we
just need to augment the checkin/out times.

This will now make multi-type and graph expansion actually visible to PBI.

From Mozilla's documentation [1]

> If the element is an […] img […] element
> The value is the resulting URL string that results from parsing the value of the element's src attribute

[1] https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/itemprop#Values

Differential Revision: https://phabricator.kde.org/D27720

Found an old reservation in my inbox, adjusted the labels and date format to support it, too.

Differential Revision: https://phabricator.kde.org/D27718

Useful for e.g. checkinTime. It can technically be a date time but in practice it has to be seen if it actually is used as more than a time.

Differential Revision: https://phabricator.kde.org/D27713

Result isn't entirely propagated yet due to a pending API change for that.
This also doesn't do any reference resolving etc. Should nevertheless
already help PBI a bit.

Fixes generation of 0-length ical events in that case.