Created attachment 55783 [details]
test case odp file
I just noticed in 3.5.0beta3 that the fonts are different in the editor versus the presentation mode (see attachments). I do not like how it looks in presentation mode.
Created attachment 55784 [details]
v3.5.0rc1 editor window screenshot
Created attachment 55786 [details]
v3.5.0rc1 presentation mode screenshot
Created attachment 55787 [details]
v3.4.5 editor window screenshot
Created attachment 55788 [details]
v3.4.5 presentation mode screenshot
This bug seems to be related to bug #43009 (Launchpad: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/779366 )
but I get the error with Liberation Sans in SLIDESHOW. I tried updating font from 1.06 to 1.07.1 and I still get the error.
I reproduce this bug
Version ID : b6c8ba5-8c0b455-0b5e650-d7f0dd3-b100c87
MacOS 10.5 leopard - Intel
This occur with all fonts i've tried : Arial, Times New Roman, Helvetica
I've seen the same behavior in 3.4.4 for Ubuntu Oneiric.
I just downloaded 3.5.1rc1 from the pre-release section and the fonts are working properly, I would like to wait until the full 3.5.1 comes out before closing bug.
What are others seeing?
It seems to be fixed in 3.5.1-rc1 => it does not need immediate attention => let's leave it out of the most annoying bugs.
Feel free to put it into most annoying bugs if you still see it with 3.5.1-rc1 or never.
The bug is not present in LibreOffice 18.104.22.168 on Mac OS X 10.7.3 (though it exists in 3.5.1rc3)
Just downloaded 3.5.1rc2 from the pre-release folder and I have no problems, just like 3.5.1rc1.
kghose: Since 3.5.1rc3 has not even been tagged yet, reading your message is very confusing.
(In reply to comment #11)
> Just downloaded 3.5.1rc2 from the pre-release folder and I have no problems,
> just like 3.5.1rc1.
> kghose: Since 3.5.1rc3 has not even been tagged yet, reading your message is
> very confusing.
@vossman: I cannot check on Mac, but according to your report I set this to fixed.
thanks for reporting & updating!
Still no problems in 3.5.2, so hopefully this one is gone for good.
(In reply to comment #13)
> Still no problems in 3.5.2, so hopefully this one is gone for good.
AH yes, that sounds logic, of course if the fix is correct. So I close this now.
& please jump in here or in a different issue if needed :-)