Created attachment 66787 [details]
Screen capture showing truncated text at bottom of window
This only seems to be an issue during first use after clean install or an upgrade.
Attached image shows issue.
To reproduce this delete ~/Library/Application\ Support/LibreOffice before starting LibreOffice.
Thank you very much for your bug report!
REPRODUCIBLE on Mac OS X 10.6.8 (Intel) with
* LibreOffice 126.96.36.199
* LibreOffice 188.8.131.52
* LOdev 184.108.40.206.alpha0+ (Build ID: 5ca197c; pull time: 2012-09-06 07:07:33)
(In reply to comment #0)
> This only seems to be an issue during first use after clean install or an
Yes, but this is true just because only after a clean install all these messages are printed at the bottom of the splash screen (on an ordinary application startup, no messages are printed there).
> To reproduce this delete ~/Library/Application\ Support/LibreOffice before
> starting LibreOffice.
... or better, just rename it; to make LibreOffice display all these messages again.
@Astron, Thorsten Behrens:
Hello Astron, hello Thorsten,
here is yet another cosmetic issue with the new splash screen on Mac OS X. It is minor, but annoying, because it makes LibreOffice 3.6 look a bit "fragile" or "unfinished" on Mac OS X. Please take a look at it; it is a minor issue, of course, but should also be rather easy to fix; of course, this may involve changing the font size used for these messages.
Thank you very much!
Is this a dupe of bug 52268 or is it a valid new bug?
(I am asking because I am not completely sure if there is different code involved or not. I. e., the splash screens for Windows and Linux use different code.)
(In reply to comment #3)
> Is this a dupe of bug 52268 or is it a valid new bug?
> (I am asking because I am not completely sure if there is different code
> involved or not. I. e., the splash screens for Windows and Linux use different
Oh, thank you for the hint! (Why did I miss bug 52268?)
Yes, on the visual level, this IS a dupe of bug 52268 -- both on Win and on Mac OS X, the messages are displayed in the same (wrong) way. But I don’t know about the code, so someone else needs to judge this ...
Marking as duplicate of bug 52268 for now, because at least at the surface it *is* the same bug.
*** This bug has been marked as a duplicate of bug 52268 ***