Bug 80411 - select-all and change-font does not affect the numbering
Summary: select-all and change-font does not affect the numbering
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.5.7.2 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-23 15:49 UTC by Darko Veberic
Modified: 2016-03-12 15:06 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
numbered paragraph stay times new roman (30.99 KB, application/vnd.oasis.opendocument.text)
2014-06-23 15:49 UTC, Darko Veberic
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Darko Veberic 2014-06-23 15:49:53 UTC
Created attachment 101598 [details]
numbered paragraph stay times new roman

a simple document with numbered paragraphs has been produced by copying content from a web page and pasting it into the writer (see attachment). all the text is in default font, times new roman. upon hitting ctrl-a (select all) and choosing ubuntu from the font menu, all the text except the font of numbers is changed.

what should really happen: select-all should change the font of the numbering also...
Comment 1 ign_christian 2014-06-24 04:11:32 UTC
Reproducible on 4.2.5.2 and 3.5.7.2, Ubuntu 12.04 x86. Looks random, some number change & some not.

@Darko, please see Bug 61279. Did you create numbering with: Format -> Bullets and Numbering ?
Comment 2 ign_christian 2014-06-24 04:15:47 UTC
No change with number 1,7,10,14,19,22. The others changed
Comment 3 Timur 2015-01-19 17:54:15 UTC
I think this my be closed a duplicate of Bug 61279.
Comment 4 QA Administrators 2016-02-21 08:36:10 UTC
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

   Test to see if the bug is still present on a currently supported version of LibreOffice 
   (5.0.5 or 5.1.0)  https://www.libreoffice.org/download/

   If the bug is present, please leave a comment that includes the version of LibreOffice and 
   your operating system, and any changes you see in the bug behavior
 
   If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave 
   a short comment that includes your version of LibreOffice and Operating System

Please DO NOT

   Update the version field
   Reply via email (please reply directly on the bug tracker)
   Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
   appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3)

http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword


Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa

Thank you for your help!

-- The LibreOffice QA Team This NEW Message was generated on: 2016-02-21
Comment 5 Darko Veberic 2016-02-21 09:37:24 UTC
tested it with 5.0.5.2: the bug is gone!
Comment 6 Cor Nouws 2016-03-12 15:06:24 UTC
(In reply to Darko Veberic from comment #5)
> tested it with 5.0.5.2: the bug is gone!

Thanks for testing, and glad it works OK now.
Set to WorksForMe (Fixed is when there is a known patch involved.)