Bug 48848 - FILEOPEN: after opening a doc all tables have Allignment:LEFT instead of Automatic
Summary: FILEOPEN: after opening a doc all tables have Allignment:LEFT instead of Auto...
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-17 16:15 UTC by Marius
Modified: 2013-07-08 21:23 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
example1 - please see the table alignment from the header (45.00 KB, application/msword)
2012-09-16 10:18 UTC, Marius
Details
please see the strange way the tables are imported (47.50 KB, application/msword)
2012-09-16 10:22 UTC, Marius
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marius 2012-04-17 16:15:57 UTC
The summary is self descriptive. If you open a Microsoft Office doc file you will see that by default all tables are LEFT alligned. After setting the Allignment to Automatic and saving everything will look fine.
Comment 1 Joel Madero 2012-09-11 20:51:34 UTC
Please provide a document so we can see the behavior. Also, in Microsoft Office are you saving this document as align left for the table text? Marking as NEEDINFO, once you provide attachment and info please change back to UNCONFIRMED and I'll take a look at it. Thanks
Comment 2 Marius 2012-09-16 10:18:28 UTC
Created attachment 67230 [details]
example1 - please see the table alignment from the header

It is possible that the person who made the table in word didn't specify any special alignment. Probable the best "default" alignment for imported tables would be "automatic"
Comment 3 Marius 2012-09-16 10:22:33 UTC
Created attachment 67231 [details]
please see the strange way the tables are imported

Another test is to save the document in "doc" format from LibreOffice then reopen it. They appear differences in the look ot the document. It's not ok.
Thanks.
Comment 4 QA Administrators 2013-05-29 14:00: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/FDO/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 5 ign_christian 2013-06-01 02:17:08 UTC
Hi Marius

Both files you supplied has different content. How we compare & see the problem?
I think you should supply 2 identical files (1 saved by MSO, 1 saved by LO)
Comment 6 QA Administrators 2013-07-08 21:23:02 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