Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!
View Bug Activity | Format For Printing | XML | Clone This Bug
I tried using glabels-2.2.0 with some files previously created to print a batch of needed labels unsuccessfully. The file in question was using Avery 5163 template (4 x 2) in rotated mode 2" wide x 4" long. The print preview and print output is chopped halfway down for both columns of labels on the page. This seems to indicate that the problem is most likely that when the rotation was changed the print cutoff dimensions were not changed to match the new orientation. Upstream bug #1872568, http://sourceforge.net/tracker/index.php?func=detail&aid=1872568&group_id=46122&atid=445116 This new version also has a new file format that is not compatible with older versions of glabels. This is not a problem unless you are forced to re-install an older version (like I had to). Any files modified/created by 2.2.0 will have to be re-created. While format changes are not unreasonable, I had no warning of the format change and no backup of the old file format was made automatically. I think the ebuild should have an ewarn stating the format change and to make backups of your files before using this new version. In case you need to re-install and use the older version. upstream bug #1872584, http://sourceforge.net/tracker/index.php?func=detail&aid=1872584&group_id=46122&atid=445116 I also experienced some line spacing changes with a previously created file (minor) upstream bug # 1872576, http://sourceforge.net/tracker/index.php?func=detail&aid=1872576&group_id=46122&atid=445116 But, on the bright side, the new gtk print routines actually worked for me. Up till now the only way I could print properly was to select generic postscript ==>custom==>llpr to force printing thru llpr to set the correct paper type, etc.. Gtk/cups would never use settings for paper type, duplex mode. Unfortunately this new version does not offer quite as many print options, but if the gtk/cups print system will work correctly, then it should be OK. btw I had been using version 2.1.1 & 2.1.2 for some time with little problem. Overall, less problems than version 2.0.4. So, my vote = Not quite ready for prime time. Let's hope that a bugfixed 2.2.1 is out soon. Brian.
erm, besides the ewarn (I wasn't aware of the file format change or I just missed it), there is nothing much I can do for the rest without a patch.
Yeah, I did not know about the format change until I tried to open the modified label (I fixed the line spacing in 2.2.0) in the just re-installed 2.1.2 which complained about an unknown file format.
I have re-installed 2.2.0 and done some more testing... It gets even worse :( The rotated label shows correctly on the screen, but for printing it still uses a horizontal capture image (4" wide x 2" high) which is rotated 90 deg. I created a test label that purposely had text that went out of bounds to the right and it picked up the whole thing like it was a normal horizontal orientation. Of course it will overprint onto the adjacent label as well. I also found that several fonts will show on screen but will not produce any output in the print image or print preview image. Some fonts do not even show anything on the screen. Can anyone else confirm the font problem to make sure it is not something faulty in my system? The default "Agate" font is one that will not produce any print or print preview output for me. The times text loses the first and third or more lines, showing only the second line of text. It's position in relation to the frame is wrong as well, it changes drastically with different fonts, even showing above the frame it is suppose to be inside of. I am thinking this version should be hard masked until fixed. I Think version 2.1.2 (unstable) has been far more stable than this (stable) release. I never could get 2.1.3 to compile succesfully. The gentoo patches from 2.0.4 had already been incorporated into the source for >=2.1.3. I did not have time to try any more recent development releases leading up to 2.2.0. I will attach a sample test label showing the print problem to the upstream bugs I submitted. Brian
about the rotated labels, this was already noted in the links you put in your first post. Considering you seem to be using this in depth, I think it is indeed wise to mask this for the time being.
There is an upstream patch to fix the print problem for rotated labels. I have applied his patch manually and created one for the release tarball. It works for me. However, he states that he is not experiencing the font problems I am having. Can anyone else test that to find out if it is my system that is at fault? I was having no problems with those same fonts using -2.1.2 this past few days. My quick tests with this patch seem to show the same font problems I was having. Upstream is going to release -2.2.1 in a few days, so no point in updating the tree with this patch and ebuild. I am attaching it here for more testing though.
Created an attachment (id=141202) [edit] print bug patch
Created an attachment (id=141204) [edit] glabels-2.2.0-r1.ebuild
version bump to 2.2.1. * Font lists are now sorted alphabetically. * Evolution records are now sorted by the "file_under" field. * Fixed clipping bug when rotating labels. I used the 2.2.0 ebuild and all compiled fine. It works, but I still have the font issues and the pango screen layout does not match the print output in line spacing (using a pre-existing label). I'll do more testing later
I've bumped this ebuild in tree. Could you provide a sample file that shows your font problem ?
please get back to us.
Created an attachment (id=148812) [edit] sample label the image may not be sent with this label. I have not had any problems with images, so just substitute any image on your system. I was using it for reference and font spacing checks.
Ok, sorry, but things have been very hectic around here this past few months. The good news is that I am getting a life back :D. I've done some testing with both 2.2.1 and 2.2.2 and get the same results mostly. When printing with the Agate font there are: Error (1610): No font in show Error (1945): No font in show Error: Unknown font tag 'f-1-0' Error (1945): No font in show type of errors in the terminal. When these occur it causes other fonts to fail to print as well. Some fonts just do not produce any print output and no errors in the terminal. Times is one of those. Times also does not respond well to font size changes above 16 and seems to max at 23, despite the setting. I have made up a small label example and changed the fonts of several text fields with mixed results. In 2.2.2 the font line spacing that I get seems to carry over to the actual print now for some old production labels I have. In 2.2.1 the print output was often correct with the screen display out a little. I am wondering if I am having problems in pango and such and they are only showing up in glabels. I have also re-compiled glabels with the debug use flag set, but got no additional output in the terminal. If you are able to give me some --gtk-debug=flags settings, it may give more results.
