Revision as of 17:25, 12 December 2019

KDE Itinerary

Getting KDE Itinerary

Android

Not yet available in F-Droid or Google Play Store unfortunately.

Nightly development builds are available here:

Direct APK download: https://binary-factory.kde.org/view/Android/job/Itinerary_android/
KDE nightly F-Droid repo: https://community.kde.org/Android/FDroid

Plasma Mobile, Flatpak

flatpak remote-add --if-not-exists kdeapps --from https://distribute.kde.org/kdeapps.flatpakrepo
flatpak install kdeapps org.kde.itinerary

Self-compiled

https://invent.kde.org/kde/itinerary

Make sure you have the ZXing-C++ and Poppler dependencies. For Poppler, this needs the private Poppler API, the header files for this are provided through separate packages by several distributions, so make sure to have those installed as well.

Getting data into KDE Itinerary

Direct import

Use Global drawer > Import... in the app to import data from a file directly. Usually works for PDF and PkPass files, full emails are hard to get hold of on mobile usually.

KMail Itinerary plug-in

Interaction with the KMail plug-in is a bit hidden in older versions (19.08 or before), via the small icon in the top right corner (to be fixed).

Via NextCloud/DavDroid: Select "Add To Calendar", and pick a calendar on a NextCloud server. Once synced to an Android phone via DavDroid, select "Check Calendar" in the global drawer of the app. Other CalDav servers might work, other sync apps than DavDroid will likely not work.

Via KDE Connect: Select "Send to <device>".

Troubleshooting

The KMail Itinerary plug-in isn't finding anything

Is the itinerary plug-in installed? Check $LIBDIR/plugins/messageviewer/bodypartformatter/messageviewer_bodypartformatter_semantic.so. If you are missing this, it's in the kdepim-addons repository, and can probably found similarly named distro packages.
Is KItinerary built with Poppler and ZXing? Check the output of `$LIBDIR/libexec/kf5/kitinerary-extractor --capabilities` (19.04 or newer). This should show something like this:

HTML support        : libxml2
PDF support         : poppler
iCal support        : kcal
Barcode decoder     : zxing
Phone number decoder: libphonenumber

Is the input document supported by KItinerary? See https://community.kde.org/KDE_PIM/KItinerary/Supported_Providers

How to report bugs? Use https://bugs.kde.org, product "KDE Itinerary". If the bug involves sensitive documents that you don't want to publish there, you can send those directly to [email protected].

Terms

KDE Itinerary: the mobile app for showing your itinerary.
KItinerary: the library providing the data extraction engine (yes, sub-optimal naming considering the above).
KMail Itinerary Plug-in: plugin for KMail running the data extractor on the email you are currently looking at and showing a blue framed box at the top with what it found
KItinerary Workbench: diagnostic and development tool for the data extractors.
Poppler: PDF parsing library, needed by KItinerary in order to process PDF files.
ZXing-C++: Barcode decoding library, needed by KItinerary to decode any form of barcode.

@@ Line 5: / Line 5: @@
 === Android ===
-* Nightly build https://binary-factory.kde.org/view/Android/job/Itinerary_android/
+Not yet available in F-Droid or Google Play Store unfortunately.
+Nightly development builds are available here:
+* Direct APK download: https://binary-factory.kde.org/view/Android/job/Itinerary_android/
 * KDE nightly F-Droid repo: https://community.kde.org/Android/FDroid
@@ Line 15: / Line 18: @@
 === Self-compiled ===
-Make sure you have the ZXing-C++ and Poppler dependencies. The latter include the private Poppler API, and headers which are provided through separate packages by several distributions.
+https://invent.kde.org/kde/itinerary
+Make sure you have the ZXing-C++ and Poppler dependencies. For Poppler, this needs the private Poppler API, the header files for this are provided through separate packages by several distributions, so make sure to have those installed as well.
 == Getting data into KDE Itinerary ==