After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 158030 - Bugs when printing
Bugs when printing
Status: RESOLVED DUPLICATE of bug 143874
Product: gedit
Classification: Applications
Component: general
2.8.x
Other Linux
: Normal normal
: ---
Assigned To: Gedit maintainers
gedit QA volunteers
Depends on:
Blocks:
 
 
Reported: 2004-11-12 10:45 UTC by Shahar
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8


Description Shahar 2004-11-12 10:45:31 UTC 
Well, just try to print something. I've coded a c++ application using gedit, and
printed it in 2 different printers with the same results.

When printing, first of all it seems that some pages are printed top to bottom
and some bottom to top. Apart from that, some text overrides other text on the page.

If you'd like I could attach 2 different files in which the bug occured, but I
believe it is not really needed.

Thanks in advance.
Comment 1 Paolo Borelli 2004-11-12 10:50:50 UTC 
Thanks for the report.

I suspect this is a bug in pango support added to gtksourceview: may you try to
downgrade to gtksourceview 1.0.X and see if it happens again?
Comment 2 Shahar 2004-11-12 11:15:59 UTC 
I downgraded it and indeed it doesn't overprint text. It has other issues
however, there are a few comments in hebrew which are printed backwards (since
hebrew is RTL language) but I guess that was a newly introduced feature.

Anyway, I guess it is a bug in gtksourceview. Hope it can be fixed in the next
maintainance release.
Comment 3 Paolo Borelli 2004-11-12 11:25:45 UTC 
Yup, pango introduces support for RTL languages etc, however the pango patch has
intruced regressions with regard to printing.

I'm marking this as a duplicate of 143874, which is the gtksourceview bug report
about pango printing issues.

*** This bug has been marked as a duplicate of 143874 ***