Bug 91176 - Shadowed Drop cap truncates character
Summary: Shadowed Drop cap truncates character
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.4.2.2 release
Hardware: All macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-08 18:40 UTC by Eliezer Segal
Modified: 2016-05-09 20:07 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Screen shots from Mac and Windows (1.34 MB, image/jpeg)
2015-05-10 18:17 UTC, Eliezer Segal
Details
Screenshot from LO4.4.3.2 running on OS X 10.10.3 (190.21 KB, image/jpeg)
2015-05-22 15:26 UTC, Eliezer Segal
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Eliezer Segal 2015-05-08 18:40:42 UTC
When a drop cap character style includes "shadow," the character is truncated so that only the left half appears. (Switching to a different  drop-cap character style in the paragraph style does not register unless I first format the paragraph in a different paragraph style and then switch back to the one using drop caps.)
This bug does not occur in OpenOffice.org (though the shadowed drop cap sometimes crashes the program). Nor does it occur in NeOffice.
Comment 1 A (Andy) 2015-05-09 07:01:23 UTC
For me not reproducible with LO 4.4.2.2, Win 8.1.

Or did I make something wrong?

What I made:
1. Open WRITER
2. Write a sample text paragraph
3. Select the paragraph and make a right mouse click
4. Go to PARAGRAPH in the context menu and there to the tab DROP CAPS and check "Display Drop Caps" and press OK
5. While still have selected the paragraph make once more a right mouse click
6. In the context menu select CHARACTER and go to the tab FONT EFFECTS and check "Shadow" and press OK

Result: In the Print Preview everything is fine.
Comment 2 Alex Thurgood 2015-05-09 13:46:00 UTC
Following Comment 1, no repro on 

Version: 5.0.0.0.alpha1+
Build ID: 3ffed8635acd55a5989bf9a0f4bc9c20b0acd945
Locale : fr-FR (fr.UTF-8)
Comment 3 Alex Thurgood 2015-05-09 13:46:37 UTC
Tested on OSX,10.10.3
Comment 4 Alex Thurgood 2015-05-09 13:52:37 UTC
@Eliezer: please provide us with more information.

Which version of OSX ?
Does this happen in a particular document (type/format), or any Writer document ?
Does it happen when you create a new Writer document ?

Please provide exact detailed steps for reproducing, unless the steps given in Comment 1 are correct.

Setting to NEEDINFO pending requested information. Please set back to UNCONFIRMED once you have provided that information.
Comment 5 Eliezer Segal 2015-05-10 18:17:02 UTC
Created attachment 115483 [details]
Screen shots from Mac and Windows
Comment 6 Eliezer Segal 2015-05-10 19:34:39 UTC
After playing around a bit, it appears that the problem does not exist in earlier versions of LO, but is new to 4.4 (I realize that these are not necessarily for release yet, so consider it beta testing).

Interestingly, the Drop Caps seem to show up correctly in the thumbnail previews on the Startcenter page. Go figure.
Comment 7 Gordo 2015-05-22 14:52:24 UTC
Could not reproduce.

These steps are different from comment 1 and require testing on OSX:
1. New Text Document.
2. Edit -> AutoText -> Standard -> Dummy Text, Insert, and Close.
3. Right click on paragraph, Paragraph -> Drop Caps tab and check Display drop caps.
4. Increase lines to 4 (to match screenshot).
5. In the same dialogue, change Character style to Drop caps and OK.
6. In Sidebar -> Styles and Formatting -> Character Styles, right click on Drop Caps and Modify.
7. On Font Effects tab, check Shadow and OK.
Result:
All of the first character is visible.

I also modified the character style first before applying the drop caps and get the same result.

Windows Vista 64
Version: 4.4.3.2
Build ID: 88805f81e9fe61362df02b9941de8e38a9b5fd16
Comment 8 Eliezer Segal 2015-05-22 15:26:17 UTC
Created attachment 115833 [details]
Screenshot from LO4.4.3.2 running on OS X 10.10.3
Comment 9 Alex Thurgood 2015-05-29 08:33:35 UTC
@Eliezer : please provide detailed steps of how you achieve the effect you consider to be buggy - screenshots don't help us here as they only show the final result you obtain.

Setting back to NEEDINFO
Comment 10 Eliezer Segal 2015-05-29 14:55:14 UTC
The steps described by Gordon are exactly correct, and produce the bug in LO 4.4.+ in OS X 10.10.3 (I've tried it on at least three different Mac hardware configurations).
Comment 11 QA Administrators 2015-12-27 20:30:51 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INVALID
due to lack of needed information.

For more information about our NEEDINFO policy please read the
wiki located here:
https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO

If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
 
Thank you for helping us make LibreOffice even better for everyone!


Warm Regards,
QA Team
Comment 12 QA Administrators 2016-05-09 20:07:24 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

This INVALID Message was generated on: 2016-05-09