Hello! I've noticed that some fonts (e.g. "URW Palladio L", "Bitstream Charter", "Century Schoolbook L", "Utopia", "URW Bookman L" and maybe some others) look stretched vertically in Slide Show mode. In editing mode as well as in the exported PDF file everything is fine. This Launchpad bug seems to describe the similar issue: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/779366 Regards, Vladimir
This bug is still present for LibreOffice 3.5.0beta2
I've seen the same behavior in 3.4.4 for Ubuntu Oneiric.
Version 3.4.5 for Ubuntu Oneiric (PPA repository) still shows the same behavior.
Same bug on LibreOffice 3.5.0rc3 for Mac OS 10.6.8
Can you confirm that turning off use-hardware-acceleration fixes this ? :-) Sample document cf. bug#46901 shows this clearly: https://bugs.freedesktop.org/attachment.cgi?id=57920> It is caused by the cairo canvas: in a nutshell :-) should be Linux only in 3.5.2. Thanks for the nice clean report.
(In reply to comment #4) > Same bug on LibreOffice 3.5.0rc3 for Mac OS 10.6.8 @gka: Which fonts did you use for this test on MacOS? I want to test if this bug is still present with LibreOffice 3.5.2.x, but because the bug seems to depend on the fonts used, I'd like to test with the same fonts you used for your test. (BTW: I wanted to give it a try with Utopia (PostScript Type 1 from Adobe) or Bitstream Charter (PostScript Type 1), but both fonts don't even show up in the font menus of LibreOffice -- like all old-styled PostScript Type 1 / Mac fonts they are just ignored by LibreOffice -- but this is a different problem; the point is just that I can't use these fonts for testing and don't know which fonts I should test.)
@v_2e@ukr.net vladimir, (In reply to comment #5) > Can you confirm that turning off use-hardware-acceleration fixes this ? :-) > Sample document cf. bug#46901 shows this clearly: > https://bugs.freedesktop.org/attachment.cgi?id=57920> > > It is caused by the cairo canvas: in a nutshell :-) should be Linux only in > 3.5.2. Thanks for the nice clean report. Can you please look at it? Thanks,
Cor Nouws/Michael Meeks, unchecking Use hardware acceleration does prevent the problem. 1) lsb_release -rd Description: Ubuntu precise (development branch) Release: 12.04 2) apt-cache policy libreoffice-impress libreoffice-impress: Installed: 1:3.5.2-2ubuntu1 Candidate: 1:3.5.2-2ubuntu1 Version table: *** 1:3.5.2-2ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages 100 /var/lib/dpkg/status Status -> NEW
Hello! (In reply to comment #7) > @v_2e@ukr.net vladimir, > > (In reply to comment #5) > > Can you confirm that turning off use-hardware-acceleration fixes this ? :-) > > Sample document cf. bug#46901 shows this clearly: > > https://bugs.freedesktop.org/attachment.cgi?id=57920> > > > > It is caused by the cairo canvas: in a nutshell :-) should be Linux only in > > 3.5.2. Thanks for the nice clean report. > > Can you please look at it? Thanks, Yes, I have just tried it with LibreOffice 3.5.2.2 ID сборки: 350m1(Build:202) and it turned out that turning off the hardware acceleration does indeed "fixes" the problem. The fonts look normally without acceleration.
This one might be a DUP of "Bug 47673 SLIDESHOW: Particular fonts like "Century Schoolbook L" too narrow with hardware acceleration" (might still happen) or "Bug 46901 - SLIDESHOW shows characters too slim with Hardware Acceleration activated - cairo canvas used in error on windows" (should be fixed in between) We still do not really know what is happening here and what the roots might be, so NEEDINFO again due to <https://wiki.documentfoundation.org/BugTriage#Process> item 5 @v_2e@ukr.net: Can you decide whether this one is a DUP of one of the above ones or something different?
(In reply to comment #10) > > @v_2e@ukr.net: > Can you decide whether this one is a DUP of one of the above ones or > something different? This bug is definitely about the same problem as the Bug 47673 I also checked the "hardware acceleration" option, and yes, everything is fine with this option turned off. My current LO version is 3.6.2.2
*** This bug has been marked as a duplicate of bug 47673 ***