Mailinglist Archive: opensuse-bugs (4065 mails)

< Previous Next >
[Bug 665937] New: Kate prints tabulations different than in window
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Thu, 20 Jan 2011 17:48:11 +0000
  • Message-id: <bug-665937-21960@http.bugzilla.novell.com/>

https://bugzilla.novell.com/show_bug.cgi?id=665937

https://bugzilla.novell.com/show_bug.cgi?id=665937#c0


Summary: Kate prints tabulations different than in window
Classification: openSUSE
Product: openSUSE 11.3
Version: Final
Platform: Other
OS/Version: openSUSE 11.3
Status: NEW
Severity: Normal
Priority: P5 - None
Component: KDE4 Applications
AssignedTo: kde-maintainers@xxxxxxx
ReportedBy: johnlb2002@xxxxxxx
QAContact: qa@xxxxxxx
Found By: ---
Blocker: ---


User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13)
Gecko/20101203 SUSE/3.6.13-3.1 Firefox/3.6.13

Columns formatted using tabs in the window will result in a printout that is
all over the page. It looks as if tabs are all 8 characters on the printout
instead of the stop at a specific tab point.

The problems with it have been occurring since KDE 4 came out, and the way it
is done in the window has changed with every update of kate.

To get a proper printout, I have to select all in kate, copy to OO Writer or OO
Calc, and then print.

Also, the selected font size in the window is not the font size as printed.
Printing appears to be a fixed font size that is larger than on the screen.

Reproducible: Always

Steps to Reproduce:
1.Press the tab key to move to the next tab point
2.Do multiple lines with different amounts of characters between tab points
3.Print the document on a HP LaserJet 4M Plus (type of printer should not
effect it)
Actual Results:
What was lined up columns in the window is printed as if every tab is multiple
spaces

Expected Results:
Printed columns all starting at specific character counts from the left.

--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >
This Thread
  • No further messages