Issue 117475 - Line indent not saved correctly
Summary: Line indent not saved correctly
Status: CLOSED DUPLICATE of issue 115705
Alias: None
Product: Writer
Classification: Application
Component: formatting (show other issues)
Version: OOo 3.3 RC1
Hardware: PC (x86_64) Linux, all
: P3 Normal (vote)
Target Milestone: ---
Assignee: writerneedsconfirm
QA Contact: issues@sw
URL:
Keywords: needmoreinfo, oooqa
Depends on:
Blocks:
 
Reported: 2011-03-19 21:02 UTC by roland
Modified: 2012-06-13 12:27 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
File for testing line indent (7.93 KB, application/vnd.oasis.opendocument.text)
2011-03-20 05:05 UTC, roland
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description roland 2011-03-19 21:02:14 UTC
The line indent is not saved correctly, text arrangement is disordered after reopening. Yet, the positions of the indent markers on the upper ruler are saved correctly. A similar bug was formerly reported when saving as doc, but now it seems to happen also when saving as odt. Correct behaviour in version 3.2.
Comment 1 roland 2011-03-19 21:05:52 UTC
P.S.: This is my first bug report ever, so please apologize if I did not follow the rule book in any kind of way.
Comment 2 eric.savary 2011-03-19 22:51:55 UTC
Please give a step by step example of you do get and expect and attach a sample document
Comment 3 roland 2011-03-20 05:05:07 UTC
Created attachment 76150 [details]
File for testing line indent

Try this:

- open document in OOo 3.3
- move lower indent marker on upper ruler to 8, move upper marker back to 0; textfragment "this is indented" should be moved to 8
- save document and close
- reopen document in OOo 3.3
- markers are still positioned where you placed them, but the text is like you never made any changes
Comment 4 roland 2011-03-20 05:08:26 UTC
P.S.: If you perform the same procedure in OOo 3.2, both marker position AND text position are saved correctly.
Comment 5 eric.savary 2011-03-20 09:47:25 UTC
Still cannot reproduce.


> textfragment "this is indented" should be moved to 8

First different: if a text fragment is placed on the first line (you didn't explain where the text is) it should go back to 0, not to 8.

Cannot reproduce any change in indent definition while reloading.

You are on Linux: are you using an OOo version from our site or the version from your Linux distribution?
Comment 6 roland 2011-03-20 12:41:44 UTC
(In reply to comment #5)
> Still cannot reproduce.
> 
> 
> > textfragment "this is indented" should be moved to 8
> 
> First different: if a text fragment is placed on the first line (you didn't
> explain where the text is) it should go back to 0, not to 8.
> 
> Cannot reproduce any change in indent definition while reloading.
> 
> You are on Linux: are you using an OOo version from our site or the version
> from your Linux distribution?

Sorry, I do not fully understand your first note. If you open my attachment, move the lower indent marker in the upper ruler to e.g. 8 cm (this is a randomly chosen, you could choose any other value), the upper indent marker will follow and the text will be indented 8 cm. Then, pull back the upper indent marker to 0 cm, now the first text fragment starts at 0 cm, and the second text fragment ("this is indented") will be positioned at 8 cm. After saving and reopening, the second fragment is not at 8 cm anymore. Yet, the lower indent marker is still at 8cm.

Maybe (probably) I do not understand how to use this feature. Anyway, the behaviour was different in OOo 3.2.

I am using OOo from Arch Linux repositories, did not try the official binary yet.
Comment 7 eric.savary 2011-03-20 19:29:54 UTC
Sorry! I didn't see you had an attachment so it was not easy to understand.
Anyway we already have a duplicate for this: bug 115705.

*** This issue has been marked as a duplicate of issue 115705 ***
Comment 8 Oliver-Rainer Wittmann 2012-06-13 12:27:59 UTC
getting rid of value "enhancement" for field "severity".
For enhancement the field "issue type" shall be used.