Bug 47295

Summary:	Default paragraph style should be "Text body" and not "Default"
Product:	LibreOffice	Reporter:	Rūdolfs <rudolfs.mazurs>
Component:	Writer	Assignee:	Not Assigned <libreoffice-bugs>
Status:	RESOLVED INVALID	QA Contact:	QA Administrators <qa-admin>
Severity:	enhancement
Priority:	medium	CC:	sasha.libreoffice
Version:	unspecified
Hardware:	All
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Rūdolfs 2012-03-13 16:46:28 UTC

The "Default" paragraph style is not a good idea for a default paragraph style. A "Text body" would be more suitable.

Reason 1:
If "Default" is used as base style for all other paragraph styles. If a user includes this style somewhere in the document and then changes it through "Edit paragraph style" context menu command, like adding first line indent, it indents all other styles. This happens quite often, almost silently, and usually breaks appearance. 

Reason 2:
When composing text, the normal paragraphs will have style "Default", however, after the first heading, the style will change to "Text body" and stay such. It could be argued that text before any heading is not typical "Text body", but not all writers set heading styles the moment they are written, especially, if text is copied and pasted.

The first problem can be solved by linking all other styled to something different than "Default" or making the default style of a new document something other than "Default" (this sounds a bit confusing).

Comment 1 sasha.libreoffice 2012-06-05 03:44:03 UTC

Thanks for new idea
1. Problem may be in default template, not in program itself
2. Paragraph Style dialog, tag "Organizer", field "Next style"
so again, it is in template

So, this all may reformulated as this: "Use different template as default"

Comment 2 Joel Madero 2012-07-02 21:18:42 UTC

Can you provide a document that shows this behavior and what you mean by "breaks appearance". I'm going to mark this as NEEDINFO, once you provide the document please mark it as UNCONFIRMED and we'll take a look at it again. Thanks for your input on LO, we appreciate it :)

Comment 3 QA Administrators 2013-05-26 22:32:28 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 4 QA Administrators 2013-07-08 21:23:04 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

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.