< KDE PIM Revision as of 07:13, 26 July 2019 (view source)Vkrause (talk | contribs)m (→Troubleshooting)← Older edit Revision as of 15:43, 5 October 2019 (view source) Tosky (talk | contribs) (→Self-compiled: add some notes about the usage of the private Poppler API and headers)Newer edit → Line 13: Line 13: === Self-compiled === === Self-compiled === −Make sure you have the ZXing-C++ and Poppler dependencies.+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. == Getting data into KDE Itinerary == == Getting data into KDE Itinerary == Revision as of 15:43, 5 October 2019 Contents 1 KDE Itinerary 1.1 Getting KDE Itinerary 1.1.1 Android 1.1.2 Plasma Mobile, Flatpak 1.1.3 Self-compiled 1.2 Getting data into KDE Itinerary 1.2.1 Direct import 1.2.2 KMail Itinerary plug-in 1.3 Troubleshooting 1.3.1 The KMail Itinerary plug-in isn't finding anything 1.4 Terms KDE Itinerary Getting KDE Itinerary Android Nightly build https://binary-factory.kde.org/view/Android/job/Itinerary_android/ (automatic sync to KDE F-Droid repo currently broken) 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 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. 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, 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 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. Retrieved from "https://community.kde.org/index.php?title=KDE_PIM/KDE_Itinerary&oldid=86404" Content is available under Creative Commons License SA 4.0 unless otherwise noted.