Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Allow for automatically removing spacing between same paragraph. | ||
---|---|---|---|
Product: | Writer | Reporter: | ftack <ftack> |
Component: | formatting | Assignee: | AOO issues mailing list <issues> |
Status: | CONFIRMED --- | QA Contact: | |
Severity: | Trivial | ||
Priority: | P3 | CC: | ardovm, dparker, issues |
Version: | OOo 1.1.3 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Latest Confirmation in: | --- |
Developer Difficulty: | --- |
Description
ftack
2004-09-15 10:46:34 UTC
Reassigned to BH. > A feature where spacing above and below the paragraph would depend
> on whether the previous/following paragraph style is the same...
Might this be better as a list property? As with paragraph styles, you could
assign space above and below the list (appearing on the Bullets & Numbering/List
Styles dialogs).
I think this would give a better user experience (clearer/easier to understand)
and better flexibility: If you have a pp style setting that says "ignore spacing
if the adjacent style is the same", how would you change the spacing between
list items?
List styles do only control the appearance of the individual list items. The line spacing is controlled by the paragraph properties (paragraph style or direct formatting). It would therefore be more consistent, in my opinion, to add this feature to the paragraph styles as a 'generic' feature to control line spacing (not necessarily restricted to lists). see also issue 43220 Making this a list property could work, but it would be better as a general paragraph feature--consider the analogous case of multiple subtitles (as in a course syllabus, where you may want a subtitle with the course number and another with the class time). The layout would look better (in my opinion, at least) with no space between the subtitles, but a space after. As it stands now, this requires two different styles rather than just one. This is an MS-Word feature parity bug, which I believe is very important. The workaround described is really no way to work writing documents. I also want to stress that the resolution of this issue should not be limited to lists. To grep the issues easier via "requirements" I put the issues currently lying on my owner to the owner "requirements". |