[FEATURE REQUEST] Print Logbook as PDF/Paper

[Builderhummel]

By submitting feature requests, you have the opportunity to contribute your ideas and inspiration to the Wavelog Dev-Team. Please be aware that not every feature request will be addressed or answered.

What Feature is Missing?
The feature should allow to print the QSO-Log in landscape and portrait using multiple filters (e.g. print every 15m CW QSO from 01.01.25-01.06.25 containing the following fields: "callsign, locator, rapport,..."). This could be achieved by adding a new button in "/logbookadvanced" called "Print to PDF"/"Export to PDF".

Why is This Feature Important?
This feature helps to create a fast paper backup for the logs. This is especially important for club stations, which are trying to switch to electronic logs, but still want to keep a paper copy. Moreover, annotating on paper is preferred by some hams. Also, it adds access when no electricity is present (e.g. to run a computer to access wavelog)

Is This Feature Personal or Beneficial to Others as Well?
Every user has the benefit of being able to print out the log as paper backup.

[HB9HIL]

Hello @Builderhummel

To be honest I don't see a dedicated print feature in a software which is basically made for electronical documentation. You always can create an ADIF file based on filter in the logbook advanced. This adif file is basically a textfile which can be easy printed out.

[Builderhummel]

Hi @HB9HIL,

in my understanding, the software is a way to store, manage and represent QSO Logs. A printout is just another form of representation.

Of course, you can write another tool to printout ADIF files (or simply consume the API, etc.), but then you would need, for example, an additional data storage to keep track which QSO was already printed as well as separate host for the new application (e.g. the same computer where the log was entered).

But what happens if you want to have quick access to the printout file on any device (e.g. your smartphone or printer terminal) (i.e. one of many reasons to choose a web app in the first place)?

In my opinion, such a feature provides important functionality, convenience and should not be too complicated to implement.

[phl0]

Of course, you can write another tool to printout ADIF files (or simply consume the API, etc.), but then you would need, for example, an additional data storage to keep track which QSO was already printed as well as separate host for the new application (e.g. the same computer where the log was entered).

Where would you store the information which QSOs were printed if the print function was implemented? There are no (ADIF) fields to store such information.

[Builderhummel]

Of course, you can write another tool to printout ADIF files (or simply consume the API, etc.), but then you would need, for example, an additional data storage to keep track which QSO was already printed as well as separate host for the new application (e.g. the same computer where the log was entered).

Where would you store the information which QSOs were printed if the print function was implemented? There are no (ADIF) fields to store such information.

ADIF supports user defined fields e.g. <wavelog_log_paperprintout:1>1 (you are already using it for e.g. <QRZCOM_QSO_UPLOAD_DATE:8>20250916)
https://www.adif.org/316/ADIF_316.htm#User_defined_Fields

For Wavelog, I would add another column to a table in the db (I could not find documentation about the used db-model, so I cannot make a suggestion here).

[phl0]

ADIF supports user defined fields e.g. <wavelog_log_paperprintout:1>1 (you are already using it for e.g. <QRZCOM_QSO_UPLOAD_DATE:8>20250916) https://www.adif.org/316/ADIF_316.htm#User_defined_Fields

For Wavelog, I would add another column to a table in the db (I could not find documentation about the used db-model, so I cannot make a suggestion here).

That is known (QRZCOM_QSO_UPLOAD_DATE is an official ADIF field btw). But tbh: I think this is a very edge case with huge effort compared to low usage...

[AndreasK79]

In the latest dev, an export to CSV is enabled in the advanced logbook. That is the closest thing to this that we will implement. The CSV file can be opened in any spreadsheet application and printed from there.