(In reply to Rūdolfs from comment #22)
> The issue is NOT that the style named “Default” looks wrong. Problems arise
> from the fact that all other paragraph styles inherit from it, which leads
> to surprising behaviour. For example, if I add hyphenation to the “Default”
> paragraphs, I get hyphenation in headings as well. This is a gotcha
> (counter-intuitive, but documented, behaviour).
This is how inheritance works so there is nothing wrong with this behaviour.
> If the paragraph style for new documents would have been named “Default”,
> which would inherit from template called, lets call it “Baseline” and all
> other documents would inherit from said “Baseline”, then I there would be no
> bug. However, I do NOT think this is necessary, just don't use the “Default”
> style for the new documents.
New documents start with a paragraph that has not being assigned to a paragraph style, which is why it appears as if it is assigned to the 'Default' paragraph style. Similarly when no character style is applied to text, it appears as if it is assigned to the 'Default' character style.
> My suggestion to use “Text body” style (Reason2) was proposed only because
> it is used after headings. If people like the formatting of the “Default”,
> make a new style, let it inherit all the properties of the ”Default“ style,
> call it something generic, like “Paragraph”, and use it for the first
> paragraph in new documents.
It is the normal with all word processors to not assign a paragraph style to a new blank document.
> I don't think this would break any existing documents or affect
> interoperability.
No i dont think this change would break existing documents, as users could easily create a default template which had text body as the default, the interoperability issue i was mentioning was about other apps not using 'text body' as default and not assigning 'text body' after headings which results in different behaviours in LO when working with documents created outside of LO and those created inside LO.
(In reply to Rūdolfs from comment #22)
> The issue is NOT that the style named “Default” looks wrong. Problems arise
> from the fact that all other paragraph styles inherit from it, which leads
> to surprising behaviour. For example, if I add hyphenation to the “Default”
> paragraphs, I get hyphenation in headings as well. This is a gotcha
> (counter-intuitive, but documented, behaviour).
This is how inheritance works so there is nothing wrong with this behaviour.
> If the paragraph style for new documents would have been named “Default”,
> which would inherit from template called, lets call it “Baseline” and all
> other documents would inherit from said “Baseline”, then I there would be no
> bug. However, I do NOT think this is necessary, just don't use the “Default”
> style for the new documents.
New documents start with a paragraph that has not being assigned to a paragraph style, which is why it appears as if it is assigned to the 'Default' paragraph style. Similarly when no character style is applied to text, it appears as if it is assigned to the 'Default' character style.
> My suggestion to use “Text body” style (Reason2) was proposed only because
> it is used after headings. If people like the formatting of the “Default”,
> make a new style, let it inherit all the properties of the ”Default“ style,
> call it something generic, like “Paragraph”, and use it for the first
> paragraph in new documents.
It is the normal with all word processors to not assign a paragraph style to a new blank document.
> I don't think this would break any existing documents or affect
> interoperability.
No i dont think this change would break existing documents, as users could easily create a default template which had text body as the default, the interoperability issue i was mentioning was about other apps not using 'text body' as default and not assigning 'text body' after headings which results in different behaviours in LO when working with documents created outside of LO and those created inside LO.
Regina, Sophie, Cor: Do you guys have an opinion?