SUMMARY I have a regional ticket from Spanish train operator RENFE that shows two travelers when imported in KDE Itinerary. The ticket belongs to a single traveler however. The ticket has two codes and it looks as if they are recognized as two distinct travelers. By the way, none of the two travelers actually identifies the real traveler in the ticket. They simply appear as Traveler 1 and 2. By the way, there are other similar tickets for which there are no duplication of travelers (for instance the one sent privately for https://bugs.kde.org/show_bug.cgi?id=494608) STEPS TO REPRODUCE 1. Import in Itinerary a pdf with a regional RENFE ticket OBSERVED RESULT It appears as if the ticket would be for two travelers. One shows a QR code whereas the other shows an Aztec code (I think). SOFTWARE/OS VERSIONS KDE Itinerary 24.11.70 from F-Droid using the nightly KDE F-Droid repository
The display is a bit misleading here, there's not two travelers but two tickets for the same trip, one for each of the barcodes in the PDF. I'm not familiar enough with the ticketing and ticket checks in Spain unfortunately to know the best solution for this: - If practically only one of those is needed we can just drop the other one in the extractor. - If both are needed we probably should set appropriate ticket names and display this better.
I think it is enough with the QR code. Actually, for the other tickets I have, itinerary just extracted the QR code and not the second one. I wasn't controlled in the train for that particular train, but in other trains I have shown the QR and it was fine. Moreover, RENFE app also shows only the QR.
It would be nice indeed to also display the name of the traveler regardless of whether there is one or more.
Removing the duplicate ticket has been implemented in https://invent.kde.org/pim/kitinerary/-/commit/69fd192d371ad035e7438ed39e5f8b804ccac482 and extracting the passenger name when present has been implemented in https://invent.kde.org/pim/kitinerary/-/commit/84ddd1c0caa24fff7ad1a15f53945b89038334aa.
I just wanted to confirm that this is working nicely with the last update I got from the KDE F-Droid repository. Thank you!