Download it now!
Bug 66285 - FORMATTING: Tab spacing becomes inconsistent.
Summary: FORMATTING: Tab spacing becomes inconsistent.
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.0.4.2 release
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-27 22:25 UTC by neinome
Modified: 2014-02-26 19:31 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description neinome 2013-06-27 22:25:47 UTC
Problem description: 
I'm writing a time line where the dates are on the left and a description of what happened then is on the right.  The problem is that half way down the page, the tabbing I've set stops lining up, even though the tab markers have not moved from where they were.

Steps to reproduce:
1. Set units to centimeters (I don't know if this truly has anything to do with it, but it's how mine is set).
2. Set tabs places at every 0.5cm up to 7.0cm
3. Type and try to keep consistent tabs down the page (I was spacing to 2.5cm)
4. Take small varied breaks during typing to gather data. (May not be necessary but it's something that I was doing).

Current behavior:
Tabs stopped being aligned during the time I spent typing. It looks like this:

<Date>:   This happened  on this day.  And then  this occurred
          because of it.
<Date2>:  A friend came over today with my children.  They did
            all sorts of things.

The second line will be half way between tabs, because the first will end up being only half the spacing it should.

Expected behavior:
Tabs should be precisely aligned to their columns.
              
Operating System: Windows 7
Version: 4.0.4.2 release
Comment 1 retired 2013-07-03 13:39:17 UTC
neinome: Could you please attach the document in question so we can test this and try to reproduce the problem.

Also screenshots pointing out the problem might help to verify this bug.

Thanks :)
Comment 2 retired 2013-07-03 13:39:41 UTC
After providing the requested info, please set the bug to UNCONFIRMED.
Comment 3 QA Administrators 2014-02-02 02:06:54 UTC
Dear Bug Submitter,

Please read the entire message before proceeding.

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 4 QA Administrators 2014-02-26 19:31: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 FDO