Issue 16573 - Wrong line spacing of text in draw objects
Summary: Wrong line spacing of text in draw objects
Status: CLOSED FIXED
Alias: None
Product: Draw
Classification: Application
Component: code (show other issues)
Version: OOo 1.1 Beta2
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: OOo 1.1.1
Assignee: wolframgarten
QA Contact: issues@graphics
URL:
Keywords:
: 16572 19841 21709 (view as issue list)
Depends on:
Blocks:
 
Reported: 2003-07-08 14:29 UTC by andree
Modified: 2003-12-09 10:31 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Screenshots and sample file (31.11 KB, application/octet-stream)
2003-07-09 08:25 UTC, andree 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description andree 2003-07-08 14:29:18 UTC 
This is a regression from 1.0.3.1:

When opening a a draw file that contains objects with multi-line text, the line
spacing in much too big (although it is set 0.0mm in paragraph settings).

This is not a display problem as the printout is also wrong.

Interestingly, when copy & pasting the draw object into writer, things are fine.
Comment 1 andree 2003-07-08 14:33:12 UTC 
*** Issue 16572 has been marked as a duplicate of this issue. ***
Comment 2 wolframgarten 2003-07-08 15:08:42 UTC 
Would it be possible to attach a bugdoc where the described behaviour
occurs? Maybe with one or two screenshots in it, that would be nice.
Thanks in advance!
Comment 3 andree 2003-07-09 08:25:51 UTC 
Created attachment 7491 [details]
Screenshots and sample file
Comment 4 andree 2003-07-09 08:31:47 UTC 
Sure thing!

I've uploaded a sample file and two screenshots which show the sample
file opened in 1.0.3.1 and 1.1b2.

Cheers
Andree
Comment 5 wolframgarten 2003-07-09 09:54:59 UTC 
Set to new.
Comment 6 wolframgarten 2003-07-09 09:56:15 UTC 
Reassigned to Herbert. Please have a lok if there is something that
could be done about that. The issue is reproduceable in 1.1.beta2 and
in a current internal version.
Comment 7 hdu@apache.org 2003-07-09 17:19:58 UTC 
accepting.
Comment 8 hdu@apache.org 2003-07-10 16:46:38 UTC 
Can you also provide the document that showed the problem? Or even
better a small excerpt of the document?
Comment 9 andree 2003-07-14 04:51:19 UTC 
Hi Herbert

The Zip archive that I uploaded contains a sample file
(BugID16573.sxd) in addition to the screenshots. )It was used in
making the screenshots in fact.)

Let me know if you need anything else from me.

Cheers
Andree
Comment 10 andree 2003-07-22 13:37:57 UTC 
This is still present in 1.1rc1.

Cheers
Andree
Comment 11 andree 2003-07-27 08:58:56 UTC 
This is still present in 1.1rc2. (No nagging, just informing. ;-) )

One more thing, though: I've noticed in 1.1rc2, when changing the font
to say 'Bitstream Vera Sans', all is well. Going back to 'Helvetica'
shows the same way too big line spacing again.

Cheers
Andree
Comment 12 hdu@apache.org 2003-08-19 10:29:13 UTC 
HDU->WG: similar to internal reminder #110717#. The font matching still preferes a 
matching font name over other important attributes like scalability etc. The fix for 
#110717# improves the metrics of non-scalable X11 bitmap fonts by using correction 
factors to emulating the metrics of pseudo font using the nearest size bitmap font 
metric.
Comment 13 hdu@apache.org 2003-08-19 10:30:14 UTC 
Changing target to CWS vcl7pp1r2 target.
Comment 14 philipp.lohmann 2003-09-08 14:54:13 UTC 
pl->wg: hdu is on vacation now and mentions you as knowing about this
issue, could you please verify it in vcl7pp1r2 ?
Comment 15 wolframgarten 2003-09-09 13:46:13 UTC 
Set to fixed.
Comment 16 wolframgarten 2003-09-09 13:46:30 UTC 
Issue verified.
Comment 17 hdu@apache.org 2003-09-29 17:57:02 UTC 
*** Issue 19841 has been marked as a duplicate of this issue. ***
Comment 18 tamblyne 2003-10-26 21:01:21 UTC 
*** Issue 21709 has been marked as a duplicate of this issue. ***
Comment 19 wolframgarten 2003-12-09 10:31:23 UTC 
Tested in master. Issue closed.