Created attachment 161184 [details] This bullet symbols aren't set in "Standard" or "List" format template! A "not existing" template is used. I've set the "list style" in the "Styles and Formatting"-window to the wanted bullet symbol. I did it in "Standard" and the "lists" template. But, if I create a new list by clicking on the "Bulleted"-button, different bullet symbol are used, by default/standard. It seams the formatting templates are ignored. Please, make the "Bulleted"-button to allays set the bullet and style of the template as deflaut. Bay the way: I know, MS Office is doing exactly the same mistake. But why does LO copy this mistakes of MSO?
Created attachment 161185 [details] Setting of the bullet symbol for "Standard" in the template.
Thommy, thanks for the report. But I can't see the problem. Paragraph Style Standard has List Style "Aufzählungszeichen [Bullet]" which you can find in the list style tab. So an existing list style (better than "template") is used. It should work in this way: a) customise the list syle b) select that list style in Outlone and Numbering tab of paragraph style dialog
(In reply to Dieter from comment #2) > Thommy, thanks for the report. But I can't see the problem. Paragraph Style > Standard has List Style "Aufzählungszeichen [Bullet]" which you can find in > the list style tab. So an existing list style (better than "template") is > used. > > It should work in this way: > a) customise the list syle > b) select that list style in Outlone and Numbering tab of paragraph style > dialog Closing as RESOLVED NOTABUG
Why should the user need to customise the "List Style" again an again? (very annoying) Every time it uses them? Corporate identity is very hard to enforce like that. (Or designer like to set a different list symbols by default!) Why does LO 6.4.x.x use different list symbols it every level, even if in the temple is set a unique symbol? Why does LO ignore setting in the formatting templates? Nothing is solved so fare. Nothing. Please, have a look at the attachments and try your self! It used to work in older LO and OOo versions! I LO 6.4.x.x is doesn't any more. How should understand the closing to this bug? Many: "If MS is doing the same silly mistake, it isn't a bug in LO?" or even "it's not a bug, it's a feature" (WTF?)
Created attachment 162522 [details] List styles