Merge fields not substituted

[silopolis]

Hi again,

gLabel-qt installed from PPA, QRcodes available, now last issue I have is merge fields are not substituted when printing (neither in preview nor when actually printing). CSV file is perfectly read (btw, that merge screen is a thing of beauty with selectable records etc :+1: :+1: :+1: ), but "${..}" fields remain in print.

Thanks in advance for your help

[jimevins]

If you actually see the literal substitution fields in the print/preview, this means there is a syntax problem. If the field is replaced by empty text, it means the syntax is good but refers to an empty or non-existent field.

Have you tried using the "Insert substitution field" button? It will insert only valid merge fields or variables in the correct syntax. If it is grayed out, it means there is no merge source or user variables defined.

At this point I can only guess, without specifics. Attaching screenshots of the editor, merge, and print tabs, would probably help.

Also, with one copy, are you getting the correct number of labels (one per selected merge record)?

[silopolis]

Hi, First tried with the original file created in gLabels. Then tried to replace old fields re-adding them using the mentioned button. In every cases, no substitution happens and literal fields remain.

Please find screenshots, original gLabels file, file after opening and various tries in gLabels-Qt, as well as data CSV file

https://drive.google.com/open?id=1sHXGm58HJndFAc6ilWCMyls3hlV3zfXn

Seems like the number of labels is ok

Thanks for your support

Edit: kept on chasing the problem and found that gLabels didn't like the field names (1st line) in my file ! Sanitized TSV file removing all spaces, points, and accented characters and substitution finally happened \o/ Clean csv file as well as adapted gLabel file with new fields names added to Gdrive folder.

May I rename this issue as a feature request for support for spaces, punctuation and special characters in field names ?

[jimevins]

Just committed 2d5650767ad94d1a9c581ce39bcb158dee9b6f9f, which should address this.