Bug 35954 - styles not imported thoroughly: with paragraph style associated bullet list is not imported when List styles are not selected with Import (see comment #12)
Summary: styles not imported thoroughly: with paragraph style associated bullet list i...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version: 3.3.3 release
Hardware: Other All
: medium minor
Assignee: Not Assigned
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-04 06:56 UTC by Paolo Benvenuto
Modified: 2014-11-04 09:03 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:

Attachments
document with a style with bullet list (8.79 KB, application/vnd.oasis.opendocument.text)
2011-08-11 00:07 UTC, Paolo Benvenuto 		Details
View All

Description Paolo Benvenuto 2011-04-04 06:56:56 UTC 
I have to import styles from a document to another.

I hit f11, and in the styles window I clic on the top right button, and then the menu item "load styles"

I select the file I want to import the styles from. The styles are imported.

However, a style that had a numeration style lost it: there wasn't any numeration style in the imported style that should have it.
Comment 1 Jan Holesovsky 2011-04-07 11:42:28 UTC 
Can you please attach the document that shows the problem?  Thank you!
Comment 2 Cor Nouws 2011-08-10 14:01:53 UTC 
no repsonse to the request > close
feel free to reopen if you have the additional info.
Comment 3 Paolo Benvenuto 2011-08-11 00:07:20 UTC 
Created attachment 50111 [details]
document with a style with bullet list

The attacched document has a "try" style with a bullet list defined.

Open a new document, F11, import styles from file, and select the attacched doc -> you'll have a "try" style without the bullet list defined.
Comment 4 Cor Nouws 2011-08-11 01:03:37 UTC 
thanks Paolo.
Can confirm the bug.
(Probably an omission during the rework of the numbering, in 2009/2009 ?)
Comment 5 Björn Michaelsen 2011-12-23 11:45:51 UTC 
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1

more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Comment 6 Florian Reisinger 2012-08-14 13:59:10 UTC 
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 7 Florian Reisinger 2012-08-14 14:00:23 UTC 
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 8 Florian Reisinger 2012-08-14 14:05:04 UTC 
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 9 Florian Reisinger 2012-08-14 14:07:08 UTC 
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 10 Paolo Benvenuto 2012-08-14 18:34:31 UTC 
stll present in 3.5.5.3
Comment 11 Florian Reisinger 2012-08-16 11:03:16 UTC 
Was confirmed...
Comment 12 Cor Nouws 2013-10-25 11:58:19 UTC 
Hi Paolo,
Works fine now for me in 4.1.3.1 
I imported styles for both paragraphs and lists - it does not work when I only import styles for paragraphs.

Can you pls check this for you?
I set to Resolved > WorksForMe (since we don't know when/how this got fixed.)

thanks,
Cor
Comment 13 Paolo Benvenuto 2013-10-25 12:55:53 UTC 
Ok, @ Cor Nouws, it's like you say: in order to get the try style correctly imported I need to check the numeration box.

However, it shouldn't be so: in my case a new blank document has the Elenco1 numeration style which the try style has too, and the import procedure should recognize that the numeration style is present and assign it to the imported try style.

In the case the numeration style of the imported style isn't present and the numeration styles aren't imported, the import procedure should warn the user.
Comment 14 Cor Nouws 2013-10-25 13:23:31 UTC 
OK. I think there is a reasonable work flow, but not perfect indeed.
Comment 15 Joel Madero 2014-11-04 03:14:06 UTC 
Some confusion about if this bug is reproducible. Moving to UNCONFIRMED to get QA to look at it again. Thanks for your understanding.
Comment 16 Cor Nouws 2014-11-04 09:03:16 UTC 
(In reply to Joel Madero from comment #15)
> Some confusion about if this bug is reproducible. 

I think I did with comment 4?
(Probably an error that the state remained NEEDINFO ?)

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.