Bug 48459 - FORMATTING - proposal for in-line headings, (run-in, inset headings)
Summary: FORMATTING - proposal for in-line headings, (run-in, inset headings)
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.5.2 release
Hardware: Other All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 99695 (view as bug list)
Depends on:
Blocks: Writer-Styles-Heading
  Show dependency treegraph
 
Reported: 2012-04-09 03:14 UTC by Bob Harvey
Modified: 2018-10-29 15:03 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments
ODT demonstrating workaround using index entries (12.14 KB, application/vnd.oasis.opendocument.text)
2014-01-27 12:34 UTC, Owen Genat (retired)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bob Harvey 2012-04-09 03:14:22 UTC
Please see https://issues.apache.org/ooo/show_bug.cgi?id=39582 for the proposal
in OOo.

I think that this would be a very useful addition to the methods of laying out.

The original issue contains good examples 

I think the mechanism would be similar to  but marginal headings require word flow within the margin, and in-line headings do not.

This is more or less a heading with no paragraph break at the end.

See https://bugs.freedesktop.org/show_bug.cgi?id=48457 for similar marginal headings proposal
Comment 1 Bob Harvey 2012-10-25 10:42:36 UTC
Bump - still unconfirmed after 6 months
Comment 2 Joel Madero 2013-11-18 22:14:37 UTC
Unfortunately part of the reason this has been in UNCONFIRMED for so long is because it requires us to dig through comments on someone else's bug tracker. We require clear and concise information on our bug tracker - saying "click this link and see" is not sufficient. Please provide the information here and if necessary say "see comment #n" on PROVIDE LINK) - vs. just "go browse this extensive bug report on AOO's framework.


Marking as NEEDINFO. Once clear info is provided here, including pointers to what comments we should look at on the link you provided, mark as UNCONFIRMED and we'll see if we can at least get it to NEW status.

Thanks for your understanding
Comment 3 Bob Harvey 2013-11-19 05:35:44 UTC
Right-oh

An 'Inline' or 'Inset' or 'Run-in' heading is one in which there is no newline at the end of the heading.  The succeeding paragraph text ('running text') runs on in smaller type on the same line.  The heading is still a separate 'paragraph' for logical purposes, e.g. creation of TOC or style selection or numbering, but the text does not start on the next line down.   This would frequently be used for low-order headings, heading level 3 or 4 downwards, in complex documents.

If the text height of the heading is sufficiently large then the succeeding paragraph may flow onto two or more lines on the right of the heading, in a layout similar to a 'Drop Caps' where the first letter of a paragraph is formed as a massive decorative 'drop capital' with the rest of the paragraph flowing around it.  This could be used to simulate a drop cap, although it would not be a true one because the first word of the paragraph would be incomplete by one letter, leading to errors in word count and perhaps indexing.  I hesitate to suggest a true 'Drop Cap' word style, though it would be fun.


It seems to me that this could be done by allowing any paragraph style (and hence any heading style) to include a boolean indicating whether the paragraph ends with a line break or not.   This is not unlike specifying the white space below a paragraph, but with the addition of it being null.  Or, rather, very short: I imagine some mechanism to specify alignment  minimum white space after the heading and before the running text would be needed.  This sounds suspiciously like another very specialist tab to me: the default or body text style could be preset with two or three 'inline starting point' tabs to allow the page to look nice, and the running text start points to line up down the page regardless of heading lengths.

Note, too, that the vertical alignment of the main 'running text' and of the inital 'run-in heading' is non-obvious.  they might want to be be bottom aligned (base aligned) in simple cases, but where the heading is made very large they will need to be top aligned.  I suspect this will want to be user selected too.

Don't forget too that design decisions here might interact with Bug 48457 for 'marginal' or 'outset' headings.



Stealing from the OpenOffice bug request you mention (which still seems jolly accessible to me, don't really understand the problem) here is an example:
------------------------------------------
Example for run-in headings:

RUN-IN HEADING  Bla bla bla bla bla
bla bla bla bla bla bla bla bla bla
bla bla bla bla bla bla bla bla bla
bla bla bla bla bla.

Bla bla bla bla bla bla bla bla bla
bla bla bla bla bla bla bla bla bla
bla bla bla bla bla.

OTHER RUN-IN HEADING  Bla bla bla.

MORE RUN-IN HEADINGS  Bla bla bla 
bla bla bla bla bla bla bla bla bla
bla bla bla bla bla.
-------------------------------------------

Similarly, someone else said:
"Lack of r.i.h. is an absolute showstopper for creating IEEE- and
MIL-STD-961E-format documents. W*** accomplishes this by allowing you to set the
paragraph mark between heading and para text to "hidden". Recent W*** versions
use a "style separator" with same effect; the paragraph as printed is formatted
with Heading X up to the style separator, and with e.g. Body Text after the
separator."



===============================
The original OO bug included an opposite but related proposal, where chapter number and chapter name appear on successive lines in the text, but on a single row of the TOC.  This implies having a single heading with an embedded line break that is suppressed in the TOC and other cross-references. (this technique is often seen in book layouts where the chapter number and name are centre-justified at the top of the page)
Comment 4 Fabian Alexander Wilms 2014-01-24 14:38:00 UTC
This is neccessarify for creating academic papers adhering to the very common APA style: http://blog.apastyle.org/apastyle/2009/07/five-essential-tips-for-apa-style-headings.html
Comment 5 Bob Harvey 2014-01-26 20:35:26 UTC
OK, I've provided what was asked for, and we have some independent comment supporting it.  can we move on now?
Comment 6 Joel Madero 2014-01-26 22:52:59 UTC
Moving on just means waiting for someone to triage - it's an enhancement request so honestly the priority on it is much lower. Right now the focus is on triaging issues for the upcoming 4.2 release. 

If you have time to help QA team with some triage work - the more people we have on board, the faster we can deal with these kinds of enhancement requests (at least triaging them, getting a developer to volunteer to do it is a whole different challenge).
Comment 7 Joel Madero 2014-01-26 22:56:26 UTC
That being said - your description is very concise. Agreed it's a valid request.

Marking as:
New
Enhancement
Medium - I don't see this benefiting a huge proportion of our user base (most use our software for basic things) but as the comment points out, it could be required for "higher end" tasks such as academic papers.

Also:
Might be an easy hack so adding that, I agree with the idea that there should just be a check box that by default is unchecked but which can be unchecked and it says something like "In-Line Heading" and can be applied to any style
Comment 8 Owen Genat (retired) 2014-01-27 12:34:18 UTC
Created attachment 92849 [details]
ODT demonstrating workaround using index entries

This particular issue of run-in / in-line headings can be worked around using index entries:

1. Insert run-in / in-line heading (plain text) with ensuing text e.g., "Heading level 3 Text text ..."
2. Highlight "Heading level 3".
3. Insert > Indexes and Tables > Entry...
4. Select Index of "Table of Contents" > set Level to "3" > click Insert > click Close.
5. Place cursor where the ToC is to be inserted.
6. Insert > Indexes and Tables > Indexes and Tables...
7. Index/Table tab > ensure Create from "Index marks" option is checked (default setting) > click OK.

The attached document provides a four-level example, with levels 1 and 2 being standard paragraph styles Heading 1 and Heading 2, and levels 3 and 4 created using the index entry method provided. Tested using v4.1.4.2 Build ID: 0a0440ccc0227ad9829de5f46be37cfb6edcf72.
Comment 9 Bob Harvey 2015-01-25 15:02:13 UTC
I still think this is worth persuing, even though it's been a long time.

The work around is too confusing for casual users, even though it is clever
Comment 10 Bob Harvey 2016-01-18 07:37:14 UTC
Another bump.  I have used the work-around but it is not an obvious style, does not play well with the navigator, and I have to come back here to remember how to do it.

This remains a needed enhancement.
Comment 11 Joel Madero 2016-01-18 07:55:19 UTC
Please don't bump bugs - that's not how this project works. The enhancement will be done only if a volunteer takes interest.
Comment 12 Marc Grober 2016-05-06 18:00:07 UTC
*** Bug 99695 has been marked as a duplicate of this bug. ***
Comment 13 Marc Grober 2016-05-06 18:17:16 UTC
Just came across this as I discovered the ion-line/run-in key words when building 99695 (see dup link above).  My comments there have some additional info.

My proposal was simply to allow the use of Character Styles in the ToC in addition to Paragraph Styles.  In that way, one could create a set of specific inheriting Character Styles for various ToC (or index or bibs) levels, and it would be relatively easy to share those styles, making an effective and easy to use template much simpler.

Owen's workaround is much better than others I have seen, but it would in my view still be an all round functional improvement to be able to use Character Styles  in addition to Paragraph styles.

If you disagree that this is a dupe we can always split it up again....
Comment 14 Marc Grober 2016-05-06 18:25:49 UTC
(In reply to Joel Madero from comment #7)
> That being said - your description is very concise. Agreed it's a valid
> request.
> 
> Marking as:
> New
> Enhancement
> Medium - I don't see this benefiting a huge proportion of our user base
> (most use our software for basic things) but as the comment points out, it
> could be required for "higher end" tasks such as academic papers.
> 
> Also:
> Might be an easy hack so adding that, I agree with the idea that there
> should just be a check box that by default is unchecked but which can be
> unchecked and it says something like "In-Line Heading" and can be applied to
> any style

Re: "most use our software for basic things" -- I don't know what the source of your data is, but with shrinking education budgets everywhere one looks, more and more students employing LO, and students writing academic papers perhaps numbering over half the potential user base for the product, I'd say you were being a touch myopic.....

Re: "might be an easy hack" -- yes, and I think simply tweaking the ToC generator to accept Character Styles for indexing might even be easier.
Comment 15 V Stuart Foote 2016-05-06 21:07:41 UTC
Further to Owen's work around in comment 8, seems the desired effect can also be achieved with a pair of linked Text Frames. 

The first Text Frame contains the text to be used as the index or ToC is linked to a second that has the same anchor.  Simply duplicate the text and formatting of the run-in in the second, they'll overlay (or use white space). Borders will need to be cleared, and spacing above/below to other paragraphs might need to be adjusted.

Apply outline level to the paragraph in 1st frame--it will pick up in Index/ToC.

The linked frames also work for the Side headings of original AOO bz#39582

As Text Frames (unlike Draw Text Box), they take all available formatting for the contained text.

Might be a little fiddly to get the exact spacing for a given publication "style"--but ought to be functional until a dev decides to hack at things.
Comment 16 Zenaan Harkness 2016-09-04 22:37:23 UTC
Text frames does look like another workaround, but in that case, bug #101765 (cursor movement between "normal" text paragraphs and those paras inside text frames) would of course facilitate this process, along with but #101773 (link a frame style to a para style, to make applying easier).