jimevins / glabels-qt Goto Github PK

If print outlines is enabled its clear which item is the starting item in the case where the starting item isn't 1, for example, how does one tell which item is the 4th or 8th item?

PageRenderer looks like a good place to add code to highlight the starting item except with no knowledge of the glables application I'm guessing this is the same code that renders the final output for printing.

So thoughts on how I might add highlighting or indicating of the starting item to print? Maybe adding text overlays in the center of each label with large numbers like '1' on the first one, '2' on the second etc? But only from the print preview screen. Maybe create another renderer copied from the first for the actual printing operation and a flag for showing label number preview?

Some way to inject a correction/offset into the label dimensions, without modifying the actual product template, to correct for the inaccuracy of an individual pronter, at print-time.

So, assume the product template IS correct, and so you don't want to change it. Merely, your printer is slightly not calibrated like the size of a single pixel is microscopically off, so that, maybe labels at the top of the page look perfect, but everything is 1mm off by the bottom of the page. Same goes for left to right.

Similarly, maybe all dimensions are correct, but the paper feed mechanism is simply off a little to one side or another.

You could make much better prints if you could just twiddle a knob at the last second in the print dialog, to insert a static offset for any of the normal values (xsize, ysize, xstart, ystart, xpitch, ypitch...) and also 2 extra values for x-scaling and y-scaling, which would have default values of either 0 or 1 depending on how you want to implement it, meaning either "Scale by 0.000%" or "Scale = 1:1.000". IE, you're telling it to scale each pixel by +0.002 or -0.002 or something.

This could be used to clear up and compensate for a range of printer ills. Like my current HP color laserjet, It needs two corrections. It needs the output to be scaled slightly from the nominal perfect template dimensions, to add about 1 to 1.5MM to the total vertical dimensions for an entire US-Letter page. Not offset, scaled up. And it's pulling the label sheets slightly skewed, rotated. The top of the page has good-enough horizontal alignment. The bottom of the page is skewed about 1mm right, causing the image to print about 1mm off the left edge of the labels, and stop 1mm short of the right edge of the labels. If I could conveniently just insert a small static offset to the right, and a small scaling increase, I could quickly get all labels on the sheet to look good, without actually having to have the software do any actual de-skew. (actually, that would be, injecting a skew (rotation by something like 0.25 degree), to compensate for the printers physical skew, to get a final result that LOOKS like de-skew)

Hello,

some years ago I've converted the gLabels user manual from DocBook to Mallard and made it translatable. Now gLabels will switch from GTK to Qt, and we will need a new approach. Keeping the Mallard structure and workflow as-is would be possible, but it would need yelp-tools from Gnome. Bad idea...

IMHO, the topic-based approach is much better in comparison with the rather static DocBook stuff. So my first idea was to simply convert the Mallard files to HTML using yelp-tools. HTML is the base for both Qtassistant and KDE help viewer. Then we have to think about translations... There's a tool named html2po [1]. Don't know if it is the best choice, because maintaining static HTML code is a lot of work. Maybe we have a Gnome-agnostic Mallard converter anywhere on the web, which would allow to keep the format and structure...? Pintail [2] could possibly solve this problem. Next time I'll have a look at it. But currently it is only packaged in Fedora, even from the Archlinux User Repository is no package available. But maybe it would allow to stay at Mallard and create the needed HTML files at build time.

[1] http://docs.translatehouse.org/projects/translate-toolkit/en/latest/commands/html2po.html
[2] https://github.com/projectmallard/pintail

Best Regards,
Mario

We have a use case that would be easier if glabels supported sendint the pdf file to stdout.

This would eliminate specifying a temporary file and then sending that file to the next processing step.

What I need to do is:

echo "some,args,here" | qlabels-batch template | gs ..... | ps2raster | netcat printer 9100

I tried it using my Dymo Labelmanager PnP.

This printer prints on 12mm tape, 9mm effective print. Where I need to enter a negative number in order to print correctly (I have to manually edit the template file, setting Layout x0 to -1.5mm when printing on glabels v3.40). Since you can't open your own old custom templates yet, I tried print an old label created on v3.40. This label contains negative value on Layout x0, which this version of the program interpret as a positive value.

Why not create a new category of open-ended templates where you enter the desired length when creating a new label? Super awesome would be if I could alter the length during the editing phase.

Hi,

First thank everyone involved for creating and maintaining this great software.
I just installed from PPA and, opening a label previously designed in Glabels, it revealed I only have access to a shortened list of barcodes choices and, for what I'm after, haven't access to QRcode :'(

Do I miss any dependency or something ? Please ask for any info I can provide to enjoy the goodness of this Qt dev for a KDE lover :)

Bests

I am using the latest appimage file for testing the glabels-qt software. When i try to print, i choose the printer (instead of PDF file, PDF file is working fine) and then print.
The terminal window where i have started glabels-qt looks like this when i press print and there is no print job send to the printer:

QPainter::begin(): Returned false
QPainter::scale: Painter not active
QPainter::save: Painter not active
QPainter::translate: Painter not active
QPainter::save: Painter not active
QPainter::setClipPath: Painter not active
QPainter::save: Painter not active
QPainter::rotate: Painter not active
QPainter::translate: Painter not active
QPainter::save: Painter not active
QPainter::translate: Painter not active
QPainter::setWorldTransform: Painter not active
QPainter::save: Painter not active
QPainter::setClipRect: Painter not active
QPainter::setPen: Painter not active
QPainter::pen: Painter not active
QPainter::pen: Painter not active
QPainter::setPen: Painter not active
QPainter::restore: Unbalanced save/restore
QPainter::restore: Unbalanced save/restore
QPainter::restore: Unbalanced save/restore
QPainter::restore: Unbalanced save/restore
QPainter::restore: Unbalanced save/restore

How about to print to bmp file, rather than just pdf?
Just go through the code, if the project want to support bmp file, or other type files, it is hard.
the current architecture is not support this feature.

How about to print to bmp file, rather than just pdf?

Is there any way to integrate our code with gLabels, using some sort of API.
I intend to give a print command along with a variable to insert on template and print.

Even a CLI command, that I can trigger to execute a print command would do a great help.

When I print a label, the label frame isn't printed correctly on the printer, a Dymo Labelwriter 320.
I have experienced this in the following versions:
gLabels 3.0.1-4.1(From repository)
gLabels 4.3.1 (Downloaded from glabels.org)
gLabels Continuous appimage(downloaded from github).

Please see attached photo of labels(Dymo 11354) produced with both horizontal and vertical orientation. The labels are produced with the continuous app image, but the same behavior is present in all versions mentioned above. The label rotation is always 90 degrees off. The thick box is a box that I have drawn on the label, while the thin box is created with the "print outlines" setting in the print menu.

Its clear that the text is being rotated correctly, although it is also reversed. But the actual "frame" of the label seem to always be vertical, as indicated by the outline box.

I have experimented with printer settings(auto rotate, keep orientation, 180 degrees, 270 degrees), but that doesn't change anything.

In the beginning, I thought the issue was incorrect custom label creation(Label 11354 isn't included in 3.01 and 4.3.1, so I had to create it myself), but regardless of how I did it(e.g. switching around height and width), the prints are always rotated to a vertical position.

I can verify that the printer prints correctly by printing from a custom size paper(with the dimensions of the label in landscape mode) in Libre Office Writer, as seen in the following screenshot. This leads me to belive that it is something in the commands from gLabels to the printer, that causes an issue.

My computer setup is Linux LMDE(LMDE 2 Betsy, 3.16.0-7-amd64 #1 SMP Debian 3.16.59-1 (2018-10-03) x86_64 GNU/Linux) and the drivers for the printer are the Dymo CUPS Drivers for Linux(v. 1.4.0-5). The printer itself is shared on the network using an OpenWRT-based router. I am able to print correctly to the printer using the official Dymo software(tested on a macbook).

Please let me know if you need any more information from me. I will be happy to provide it, if at all possible.

Thank you for your time.

Glabels 3.x has man pages for both the binary itself and the glabels-batch script. Admittedly, I haven't installed Glabels 4.x from source yet, but I can't found a man page source anywhere in the Git repo. OK, if we use it only via the AppImage, probably it doesn't make sense to call "man glabels-qt".

But especially for inclusion in Debian, man pages will be needed again. And once we will have a user manual, the man pages could be integrated into the translation stack. Maybe the man pages should be built from an XML source (not from Groff, this would need extra tools like po4a). Just an idea...

• Version: AppImage (Continuous Integration Snapshots) v3.99.0
• System: Ubuntu 16.04.1

In this scenario:

The text fields are correctly rendered with the corresponding record's value but the datamatrix is always the same, with this value: ${2}

Hello
Currently, max copies in "Print" seems to be hardcoded at 96.
Could you increase this number, or make it the number of labels on the sheet ?

gLabels looks like exactly what I'll need to programmatically print some labels with barcodes, graphics etc for a product I'm working on.

I may be ahead of myself but if this works I'd like to be able to make a donation to the project as a thanks. Any thoughts on how that might be possible?

Hi,
Let me first thank you all for a wonderful label software. This question might have been asked in the past. Need your suggestion.

1. I have a CSV file with a image path. (Local file system. C:<my-images><image>)
   01, C:<my-images><image1>
   02, C:<my-images><image2>

2. I added an Image object in my label design. I selected the substitution filed ${2}.

3. When I print my labels, the images are not shown.

Could you please help if I am missing any steps?

glabels-batch-qt requires an X environment to run due to use of QGuiApplication in https://github.com/jimevins/glabels-qt/blob/master/glabels-batch/main.cpp#L58. Replacing QGuiApplication with QCoreApplication and running it without X yields a segmentation fault.

Invocation: DISPLAY= glabels-batch-qt --output x.pdf input.glabels

Backtrace:

(gdb) bt
#0  0x00007ffff712ea06 in QGuiApplication::font() () from /usr/lib/libQt5Gui.so.5
#1  0x00007ffff721d043 in QFontDatabase::load(QFontPrivate const*, int) () from /usr/lib/libQt5Gui.so.5
#2  0x00007ffff71ec764 in QFontPrivate::engineForScript(int) const () from /usr/lib/libQt5Gui.so.5
#3  0x00007ffff7210a02 in QFontMetricsF::lineSpacing() const () from /usr/lib/libQt5Gui.so.5
#4  0x00005555555c4dd4 in glabels::model::ModelTextObject::update (this=0x555555a9cd90) at /home/flo/code/glabels-qt/model/ModelTextObject.cpp:598
#5  0x00005555555c3919 in glabels::model::ModelTextObject::ModelTextObject (this=0x555555a9cd90, x0=..., y0=..., w=..., h=..., lockAspectRatio=false, text=..., fontFamily=..., fontSize=10, fontWeight=QFont::Bold, fontItalicFlag=false, 
    fontUnderlineFlag=false, textColorNode=..., textHAlign=..., textVAlign=..., textWrapMode=QTextOption::WordWrap, textLineSpacing=1, textAutoShrink=false, matrix=..., shadowState=false, shadowX=..., shadowY=..., shadowOpacity=0.5, 
    shadowColorNode=...) at /home/flo/code/glabels-qt/model/ModelTextObject.cpp:132
#6  0x000055555558b96e in glabels::model::XmlLabelParser::parseObjectTextNode (node=...) at /home/flo/code/glabels-qt/model/XmlLabelParser.cpp:699
#7  0x0000555555586926 in glabels::model::XmlLabelParser::parseObjectsNode (node=..., data=...) at /home/flo/code/glabels-qt/model/XmlLabelParser.cpp:327
#8  0x00005555555862d7 in glabels::model::XmlLabelParser::parseRootNode (node=...) at /home/flo/code/glabels-qt/model/XmlLabelParser.cpp:279
#9  0x0000555555585403 in glabels::model::XmlLabelParser::readFile (fileName=...) at /home/flo/code/glabels-qt/model/XmlLabelParser.cpp:108
#10 0x000055555556af04 in main (argc=4, argv=0x7fffffffddf8) at /home/flo/code/glabels-qt/glabels-batch/main.cpp:152

ldd:

ldd ~/glabels-qt/build/glabels-batch/glabels-batch-qt                                                                                                                                    
        linux-vdso.so.1 (0x00007ffdcd18f000)
        libqrencode.so.4 => /usr/lib/libqrencode.so.4 (0x00007f8f50ea3000)
        libQt5PrintSupport.so.5 => /usr/lib/libQt5PrintSupport.so.5 (0x00007f8f50e2e000)
        libQt5Xml.so.5 => /usr/lib/libQt5Xml.so.5 (0x00007f8f50dec000)
        libQt5Svg.so.5 => /usr/lib/libQt5Svg.so.5 (0x00007f8f50d93000)
        libQt5Widgets.so.5 => /usr/lib/libQt5Widgets.so.5 (0x00007f8f506fc000)
        libQt5Gui.so.5 => /usr/lib/libQt5Gui.so.5 (0x00007f8f5011a000)
        libQt5Core.so.5 => /usr/lib/libQt5Core.so.5 (0x00007f8f4fc0e000)
        libz.so.1 => /usr/lib/libz.so.1 (0x00007f8f4f9f7000)
        libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007f8f4f80f000)
        libm.so.6 => /usr/lib/libm.so.6 (0x00007f8f4f6c9000)
        libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00007f8f4f6af000)
        libc.so.6 => /usr/lib/libc.so.6 (0x00007f8f4f4ec000)
        libpthread.so.0 => /usr/lib/libpthread.so.0 (0x00007f8f4f4c9000)
        libGL.so.1 => /usr/lib/libGL.so.1 (0x00007f8f4f436000)
        libpng16.so.16 => /usr/lib/libpng16.so.16 (0x00007f8f4f3fe000)
        libharfbuzz.so.0 => /usr/lib/libharfbuzz.so.0 (0x00007f8f4f310000)
        libsystemd.so.0 => /usr/lib/libsystemd.so.0 (0x00007f8f4f269000)
        libicui18n.so.64 => /usr/lib/libicui18n.so.64 (0x00007f8f4ef72000)
        libicuuc.so.64 => /usr/lib/libicuuc.so.64 (0x00007f8f4ed9a000)
        libdl.so.2 => /usr/lib/libdl.so.2 (0x00007f8f4ed95000)
        libpcre2-16.so.0 => /usr/lib/libpcre2-16.so.0 (0x00007f8f4ed14000)
        libdouble-conversion.so.3 => /usr/lib/libdouble-conversion.so.3 (0x00007f8f4ecfd000)
        libzstd.so.1 => /usr/lib/libzstd.so.1 (0x00007f8f4ec5d000)
        libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x00007f8f4eb39000)
        /lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x00007f8f511a4000)
        libGLX.so.0 => /usr/lib/libGLX.so.0 (0x00007f8f4eb06000)
        libX11.so.6 => /usr/lib/libX11.so.6 (0x00007f8f4e9c7000)
        libXext.so.6 => /usr/lib/libXext.so.6 (0x00007f8f4e9b2000)
        libGLdispatch.so.0 => /usr/lib/libGLdispatch.so.0 (0x00007f8f4e8f6000)
        libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x00007f8f4e826000)
        libgraphite2.so.3 => /usr/lib/libgraphite2.so.3 (0x00007f8f4e801000)
        librt.so.1 => /usr/lib/librt.so.1 (0x00007f8f4e7f6000)
        liblzma.so.5 => /usr/lib/liblzma.so.5 (0x00007f8f4e5d0000)
        liblz4.so.1 => /usr/lib/liblz4.so.1 (0x00007f8f4e5af000)
        libgcrypt.so.20 => /usr/lib/libgcrypt.so.20 (0x00007f8f4e490000)
        libicudata.so.64 => /usr/lib/libicudata.so.64 (0x00007f8f4ca4a000)
        libpcre.so.1 => /usr/lib/libpcre.so.1 (0x00007f8f4c9d7000)
        libxcb.so.1 => /usr/lib/libxcb.so.1 (0x00007f8f4c9ad000)
        libbz2.so.1.0 => /usr/lib/libbz2.so.1.0 (0x00007f8f4c99a000)
        libgpg-error.so.0 => /usr/lib/libgpg-error.so.0 (0x00007f8f4c977000)
        libXau.so.6 => /usr/lib/libXau.so.6 (0x00007f8f4c970000)
        libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0x00007f8f4c968000)

A workaround is to use Xvfb: DISPLAY= xvfb-run glabels-batch-qt --output x.pdf input.glabels

You may be interested in my project QtnProperty that allows you easily manage object's properties and show it's UI.

Especially if you are going to have more kinds of objects available.

Is it possible to add also instructions to add to compiling qrencode and zint, please.

We have many of the Herma 5078 labels. Now we switch over from Windows to linux and would like to use glabels. Could you please add support for those labels? https://www.amazon.de/Herma-5078-Etiketten-bedruckbar-selbstklebend/dp/B000M20XR6

https://www.herma.de/produkt/cd-huellen-etiketten-a4-superprint-5078/

I tried the AppImage and it was not there. Because the AppImage version seems to be released frequently, i can test changes quickly.

Thanks!

Hi, I've downloaded the continuous integration version for Windows and it doesn't appear to support QR codes like the linux version? Is this just a case of it not being compiled with the QR code library? Or is it not possible to compile it at the moment? If it is possible would you consider updating the continuous integration version to support QR codes?

It will be nice if we can use a column from csv file for number of label to be print.

I've founded a new project at Zanata where we could manage our translations [1]. I'm not sure if Zanata is the best platform for us, I stumbled upon some things:

After uploading files, the language definition will be removed. I've seen that after downloading a previously uploaded file and opening in Qtlinguist. The programm asks again for the source language, but I've just clicked on "Cancel". Obviously the language definition is not mandatory, but the dialog window itself could be annoying for translators who prefer to use their local translation tools instead of the web interface.

The one and only language which Zanata doesn't support is ca@Valencia. I don't consider this as a really big problem.

After uploading the ts files, all of the strings get marked as "unfinished". This flag can be unset by approving translated strings in the web interface, but probably Zanata doesn't accept uploaded "raw" files edited with Qtlinguist or Virtaal.

There is a project maintainer guide for Zanata [2]. If you agree with using this platform for Glabels, you have to register an account there and I can add you as a maintainer. This would enable the command line access to the files.

[1] https://translate.zanata.org/project/view/Glabels
[2] http://docs.zanata.org/en/release/user-guide/project-maintainer-guide/

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 👍 👍 👍 ), but "${..}" fields remain in print.

Thanks in advance for your help

When I try use "Template Designer" (by click on it menu entry) nothing happen.

Version: latest AppImage (built on 2018/03/05)

OS: Debian 9 "Stretch, x86_64

Hello,

in the "View" menu we have the switch Toolbars → File/Editor, see [1]. This is some strange, because I've never heard about a "File" toolbar. The strip with File, Edit, View etc. a menubar (I'm sure I don't need to explain that further), which should always be named so to avoid confusing.

But do we need such a quick toggle switch in the menu? Wouldn't it be adequate to have the appropriate setting in the preferences?

[1] https://photos.app.goo.gl/DKZxT24w9u8ZdKYx8

Currently after creating "New Product" using "Product Template Designer" wizard there NO any ways how export and/or delete custom products throw gLabels UI.

• https://github.com/jimevins/glabels-qt/blob/master/docs/PRODUCT-TEMPLATES.md

TODO

• Add "Delete Product" option for "Product Template Designer"
• Add "Export/Save Product" option for "Product Template Designer"

Please, add *_uk.ts templates to translation folder

• https://github.com/jimevins/glabels-qt/tree/master/translations

Then I will try add Ukrainian locales to gLabels ;-)

I would be happy to try gLabels-qt via PPA build and provide some feedback.
Is it on the to-do list of the project?

For a barcode object (type EAN-13), the "Show text" and "Checksum" checkbox cannot be unchecked.

glabels-3.99-master552
Windows 10 Pro 10.0.18362

1: Is there a way to reduce QrCode object size below (1.438 X 1.438)inches in gLabels?
My each label size is 2x1 inches, and it won't be able to fit in the sticker width.

2: My page layout is two stickers each side, I couldn't find a way to feed in the 2 values for the same key via CLI. This will be required as both sides will have different unique values.

My template Specifics

Some years ago, I stumbled upon the constraint that stationery products with more then one shape cannot edited in a convenient way, moreover, multiple templates are needed to use all the shapes available.

That's why we had created a branch named global-template from Glabels master [1]. One template file contains all shapes the page has, but of course this is not sufficient to use in in Glabels for a parallel workflow. What we need:

• A tabbed view for the editor window which shows all available shapes
• The project chooser should map the different shapes in one page
• Most difficult could become the print dialog: Users must be able to choose whether they like to print only one shape (in the usual way by choosing the start point and end point) or different shapes. Maybe the simplest way is, when users call the print dialog, it shows only the shapes from the currently active editor tab.
• The template designer needs to be extended to let one define more than one shape.

[1] https://github.com/GNOME/glabels/tree/global-template

Link shows 404

Release page shows no Travis build for it

What needs done before glabels v4 can be considered stable enough to release (and "use in a production environment")? There are a couple of feature requests currently listed in the README -- are those all or does more testing, etc. need to be done?

Add an easy way to build and package for Windows and Mac using "craft" from KDE
https://community.kde.org/Craft

Craft manages dependencies and builds libraries and applications from source
Craft can create setup.exe and OSX bundle

Proof of concept:

• Source: https://github.com/samdolt/glabels-qt
• Craft Config File: https://github.com/samdolt/glabels-qt/blob/master/glabels-qt.py
• CI Config File: https://github.com/samdolt/glabels-qt/blob/master/azure-pipelines.yml
• CI Build: https://dev.azure.com/dolt-ch-lab/glabels-qt/_build

If this method would be accepted, I can make a pull request (My code need some cleaning), and add support for a macOS CI build.

Huge thanks for 2db137e

While i test it out, i think i found a bug. When i made a small but long text box (about the size of the thin label), the text was cut(position way too low in the textbox). I had to use the positioning functionality - centralize(instead of top or bottom - both are cutting the text). After using the centralize functionality the text inside the textbox was ok.
Is this "text is half missing inside thin text boxes"-issue known? If not hopefully i could help by reporting it.

Currently, GLabel doesn't feel like "native" on KDE.

By using some KDE Framework Libraries, GLabels could get some feature for free, and a native look and feel on KDE:

• Toolbar icon using KDE icon theme
• Toolbar button using KDE settings (eg. with label on the right by default)
• toolbar and shortcut configurator by using KXmlGui

If it's ok on your side, I could work on this and make a pull request

Hello,

I made a first try of an import of glables files.
It imports the Text-Node and image-Nodes. The gdk-pixmap is imported without a visible problem. The text is in the wrong size but i havn't figured out what the problem is.
Attached is a patch, with my try. hope this helps.

Thanks for your work.
Here is my patch: glabels-import.zip

Hi Jim,

after the commit ca6f0c7 (Don't include line numbers in translation files) all the existing translation files are empty! I'm not really happy with that. Especially testers of the AppImage file are no longer able to see translations.

We have a translation platform now, where translators can submit their work and which is the one and only place to change translations. There's a common rule for project maintainers who use an external platform: Never touch translation files outside of the translation management system! Really never!

Don't know if I've already told about how Zanata works for maintainers. There are some instructions in the docs [1]. In case of you are not willing to maintain this, I would do this, of course, using my Git fork. But keep in mind, it always needs a new merge request (with a possible delay). Would e much easier if the updates happen in the master branch. All you have to do is to register at Zanata and then I add you to the project maintainers. The sync of translations could be done via the command line client (and even automatized this way). The client is available from the Fedora repos (zanata-client) or the Archlinux user repository (zanata-python-client), otherwise the source code is available from [2].

[1] http://docs.zanata.org/en/release/user-guide/project-maintainer-guide/
[2] http://docs.zanata.org/en/release/client/#installation

Best Regards,
Mario

It would appear that glabels-3-batch incorrectly uses stdout for debugging and error messages, instead of stderr. Furthermore when issues occur, errors and status messages are output both on stderr and stdout, making it impossible to use stdout for collecting the output PDF.

Please move debugging output all to stderr, or at least add a command line parameter to silence the output messages.

The print view uses the plural always when telling about the count of items and pages. This reads some odd when only one item on one page ist to be printed.

Screenshot:
https://lh3.googleusercontent.com/Jl9RqnPdlgTxdtwsjwWs-h9mLrVbRF_mSLqnPhlFmvTF_qPKGfpbIxk8cfLRsotE1JY4IyClI9hmhRgDPpYmvhhuTuvG2ejzk3xIpWgDNNPv9avGR8ElHwHSCCf9xGAQU8eTmQagRER7euBVBdZ0Fntn-wv4qIuqVymVq0Ki0FprzjBVokPy29zIvYW-vku-5AIzmeviggEKnV3awnzPX4J0mIC1iIda6fDHQ8AeVd9tp60pPGksKNk-De0DMLrlRpX1_yMUjHWaC9UAKII_7U6UCmxUDQs8bcPrIPIDNij22CUnCHWk7pzoeVKBBeUFNn1ywi5_yr9pDRBGU1HjmoTO5yyFaU4gtksAi150Ab2bEOTYqhucrBAH0JBQSHNrPWoy5F8-Z6v8Vc3h7CrBZNcKwkbLg2oS_f0d1_A_e-QvbAD-KErDuLgucQ3wfrWPnCV-mV0eZmxENKFo3rGExTVX8I0zCia1xYIYRdX6lv2BK3wrn_t_Nksr2JmM33j4kWhwZwZ9uTOgdTP0rChXivj4hLaD9EktUAZXUvtGCHJtIFRF-Atr9XRfvTbXaymrAJVELFVjlIqy2Y3ECrKTarXwW49Sy-KjsqtgAx_60Kfztgx7pncUgrBor1pD8YdJa3Cv4_r6gGM2v_bgekszOct8kw=w330-h182-no

The corresponding source code is in glabels/PrintView.cpp:

	void PrintView::updateView()
	{
		copiesStartSpin->setRange( 1, mModel->frame()->nLabels() );

		copiesDescriptionLabel->setText( tr("(Will print a total of %1 items on %2 pages.)")
		                                 .arg(mRenderer.nItems()).arg(mRenderer.nPages()) );

		pageSpin->setRange( 1, mRenderer.nPages() );
		nPagesLabel->setText( QString::number( mRenderer.nPages() ) );
	}

Some plural forms definition is needed here.

Hello,
thanks for glabels-qt! I am super happy I found it! (and it works on Mac just fine ;-)

I saw that the travis configuration builds only on the old ubu trusty (14.04).

Would you be interested in a PR (or a series) with the following goals

• build on a more recent ubu, 18.04
• use docker
• build on windows (this will be best effort)
• build on mac
• add build badge to README
• extract the shell commands from travis into a script
  ?

Could not generate QR codes.
We need QR codes for printing label stickers. The glabes 3.4.1 has support for IEC18004, but the same is missing in glabels-qt.

Hi, please,
could you implement a function to highlight the text?
and also the possibility of inserting a background, image or color ... would be very useful.
tnx.

Trying to make an AppImage, the build fails with

Unknown CMake command "qt5_wrap_cpp"

Video of what I did:
https://youtu.be/IUD-iqH_2cs

Build log:
https://api.travis-ci.org/jobs/217725838/log.txt?deansi=true

As the subject already says, there are some problems with text parts in the GUI.

The main window starts with dimensions of 1140 x 834 pixels. Running gLabels with the de_DE locale, I see some truncated GUI captions. Please have a look at [1].

In the side pane, I don't see the whole entries. That's annoying, but here in this case I have a scrollbar to see the whole text. Not the best solution, but still acceptable.

The second pane on the right of the sidebar: Some text is truncated, and I can't move the divider between the panes to adjust the width, as known from GTK. Maximizing the window to 1440 x 868 doesn't help, the divider is still static.

So we will need dynamic resizing of the panes, depending on the translated text. Or dynamic line wraps, whatever.

BTW, I had expected to find the "Print" option in the "File" menu, not in the sidebar...

[1] https://photos.app.goo.gl/UB07tzyin5ppml0j1

Now Glabels is translated into German, and the translation is OK so far. But all visible strings which come from Qt itself are still in English. The Travis file is based on Ubuntu, so the package "qttranslations5-l10n" is missing from the installation command. But I don't know if this is sufficient: Affects this only the build environment or the resulting AppImage file?

BTW, maybe "dist: trusty" should changed to the latest Ubuntu release...?

Hi

Thanks for a great tool! We're using it to create labels for scientific samples. These samples are labelled with a sequential number within some range. Currently, I just use seq $START $STOP >numbers.csv to generate a CSV to use as a Merge input to glabels. I feel it would be useful to support range merges, where I can supply a start and stop directly.

I can have a go at implementing this if you feel this would be useful.

Cheers,
Kevin

The Brother P-touch P700 can be fed over USB with pbm files like this one. Can it be supported in qlabels-qt?