Bug 86264 - FILEOPEN: Arrows point in wrong direction (.docx files)
Summary: FILEOPEN: Arrows point in wrong direction (.docx files)
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.2.6.3 release
Hardware: All Linux (All)
: medium trivial
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-13 20:53 UTC by John
Modified: 2015-07-18 17:27 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
A snapshot of the problematic diagram as seen from LibreOffice Writer (32.93 KB, image/png)
2014-11-13 20:53 UTC, John
Details

Note You need to log in before you can comment on or make changes to this bug.
Description John 2014-11-13 20:53:31 UTC
Created attachment 109439 [details]
A snapshot of the problematic diagram as seen from LibreOffice Writer

Arrows imported from DOCX files seem to be positioned using a different angle reference.  In the attached file, the arrows were intended to point from one item to the next in logical order, but they are apparently mirrored around various axes.  Also, the body of the arrow pointing from station #4 to #n was meant to be constructed from a dashed line, but this style doesn't seem to apply in LibreOffice.
Comment 1 Robinson Tryon (qubit) 2014-11-13 22:46:33 UTC
(In reply to John from comment #0)
> Created attachment 109439 [details]
> A snapshot of the problematic diagram as seen from LibreOffice Writer
> 
> Arrows imported from DOCX files seem to be positioned using a different
> angle reference.  In the attached file, the arrows were intended to point
> from one item to the next in logical order, but they are apparently mirrored
> around various axes.  Also, the body of the arrow pointing from station #4
> to #n was meant to be constructed from a dashed line, but this style doesn't
> seem to apply in LibreOffice.

Hi John,
Thanks for the bug report!

Please
- Attach the DOCX file that's rendering incorrectly
- Attach a screenshot of how the file renders in Word
- And let us know what version of Word you're using

When that's done, please set the status back to 'UNCONFIRMED'.


Status -> NEEDINFO
Comment 2 John 2014-11-14 01:20:26 UTC
(In reply to Robinson Tryon (qubit) from comment #1)
> (In reply to John from comment #0)
> > Created attachment 109439 [details]
> > A snapshot of the problematic diagram as seen from LibreOffice Writer
> > 
> > Arrows imported from DOCX files seem to be positioned using a different
> > angle reference.  In the attached file, the arrows were intended to point
> > from one item to the next in logical order, but they are apparently mirrored
> > around various axes.  Also, the body of the arrow pointing from station #4
> > to #n was meant to be constructed from a dashed line, but this style doesn't
> > seem to apply in LibreOffice.
> 
> Hi John,
> Thanks for the bug report!
> 
> Please
> - Attach the DOCX file that's rendering incorrectly
> - Attach a screenshot of how the file renders in Word
> - And let us know what version of Word you're using
> 
> When that's done, please set the status back to 'UNCONFIRMED'.
> 
> 
> Status -> NEEDINFO

See, that's the problem.  I do not have Word, and I recently lost access to the problematic file.  I know that the single image isn't much to work with, but I can tell you that in Word, the arrows are connected from image to image in clockwise formation, if that's any help.  I was hoping someone could do some troubleshooting.  But I can get the file and a screenshot to go with it, it might just be a week or so before I have it.
Comment 3 Robinson Tryon (qubit) 2014-11-14 05:05:08 UTC
(In reply to John from comment #2)
> See, that's the problem.  I do not have Word, and I recently lost access to
> the problematic file.  I know that the single image isn't much to work with,
> but I can tell you that in Word, the arrows are connected from image to
> image in clockwise formation, if that's any help.

That's a good start. Having the file helps us just so that someone doesn't have to recreate it as a test case.

> But I can get the file and a screenshot to
> go with it, it might just be a week or so before I have it.

Sure -- this isn't a crashing bug, so there's no problem with punting on this for a couple of weeks. Whenever you get the file, just attach it and we can go from there.

Thanks!
Comment 4 QA Administrators 2015-06-08 14:29:26 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!

This NEEDINFO Message was generated on: 2015-06-08

Warm Regards,
QA Team
Comment 5 QA Administrators 2015-07-18 17:27:57 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 FDO

Message generated on: 2015-07-18