Optimizing for Maximum QSOs per 2-column Label
de W4TV
When QSLing via QSL labels, DXKeeper will by confirm multiple QSOs with the same station on the same label if
the station callsign items of each such QSO are identical
the Via item of each such QSO are identical
if multiple QTHs are in use, the QTH components, e.g. street, city, state, country, and postal code, of each such QSO are identical
- there is space on the label
the Confirm Multiple QSOs per QSL option is enabled
Windows versions
- 8.1
- 10
- 11
Printer Parameters
Make & Model |
Brother MFC-7860 |
Left margin |
0.167 |
Top margin |
0.167 |
Width |
8.167 |
Height |
10.667 |
the selected printer's margins, height, and width as reported by the printer driver are displayed at the top of DXKeeper's Print Preview window
Ignore printer-imposed margins: unchecked
Labels
- Avery 5961
- generic 5961
Label Parameters
Labels per column |
10 |
Row 1 offset |
.55 |
Row height |
1.0 |
Column 1 offset |
0.25 |
Column 2 offset |
4.375 |
Label width |
3.875 |
Fonts
Section |
Font |
Confirmation |
Verdana 12 (Bold) |
Heading |
Verdana 6 |
QSO Information |
Verdana 6 |
- so configured, a label can contain 5 QSOs
Notes
If both Include QSL Mgr in Confirmation and Include [buro] in Confirmation are enabled, the Confirmation Font must be reduced to 10 points prevent the Confirmation line from extending beyond the edges of the label.
- Some inkjet printers may not be able to print 6 point fonts with sufficient resolution. In that case, increasing the font size to 8 points will reduce the number of available QSOs/lines by one.
- Label parameters may require adjustment with printers from other manufacturers
- Avery 5xxx labels are laser printer labels, and 8xxx labels are equivalent-size inkjet labels; they differ in the heat resistance of the adhesive.
Examples
12 point Confirmation Font with only Include QSL Mgr in Confirmation enabled
10 point Confirmation Font with Include QSL Mgr in Confirmation and Include [buro] in Confirmation both enabled
Post a question or suggestion on the DXLab Discussion Group