Bug 314358 - Object placement is incorrect
Summary: Object placement is incorrect
Status: RESOLVED WORKSFORME
Alias: None
Product: calligrastage
Classification: Applications
Component: opendocument (show other bugs)
Version: 2.5.4
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: T Zachmann
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-03 14:49 UTC by Sergio
Modified: 2023-01-19 05:17 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Test case (54.54 KB, application/vnd.oasis.opendocument.presentation)
2013-02-03 14:50 UTC, Sergio
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sergio 2013-02-03 14:49:19 UTC
Opening an opendocument image that is a compound of multiple objects, the rendering is often unsatisfactory, because the relative positioning of the various image elements is skewed.

Reproducible: Always

Steps to Reproduce:
1. Open libreoffice4.0 with draw or impress
2. Insert a complex svg image
3. Ask libreoffice4 to split the image (this only works with libreoffice4 and converts the svg into the native opendocument object format)
4. Save the file. Now you have an odg or odp with a complex image compound
5. Open it with calligra stage
Actual Results:  
The image is not rendered correctly, because its parts are positioned incorrectly

Expected Results:  
Image should render in the same way as in libreoffice or as the original svg looked in inkscape
Comment 1 Sergio 2013-02-03 14:50:07 UTC
Created attachment 76881 [details]
Test case
Comment 2 Andrew Crouthamel 2018-11-09 01:02:33 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Andrew Crouthamel 2018-11-18 03:30:14 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Justin Zobel 2022-12-20 22:51:58 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 5 Bug Janitor Service 2023-01-04 05:26:56 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2023-01-19 05:17:12 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!