Bug 43213

Summary: Can not toggle bold in text containing 3 lines, 1 overlined, 1 not over/underlined, 1 underlined
Product: LibreOffice Reporter: KB_Pößneck <KA_PN>
Component: LibreOfficeAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED FIXED    
Severity: normal CC: LibreOffice, sasha.libreoffice
Priority: medium    
Version: 3.3.4 release   
Hardware: x86-64 (AMD64)   
OS: All   
Whiteboard:
Crash report or crash signature: Regression By:
Attachments: Sample.odt
Sample by reporter

Description KB_Pößneck 2011-11-23 22:32:30 UTC
Wenn ein Textbereich markiert ist, in dem sich Zeilen befinden, die jeweils nur Ueberstrichen, gar nicht oder Unterstrichen sind, klappt das Setzen bzw. Entfernen von Fett nicht.
Beispiel : ( Formatierung nur beschrieben, geht hier sicher nicht richtig )


ueberstrichener Text
normaler Text ( nicht ueberstrichen und nicht unterstrichen )
unterstrichener Text


Die 3 Zeilen in der Mitte waren zusammen markiert. Es konnte weder Fett gesetzt noch entfernt werden.
Comment 1 Rainer Bielefeld Retired 2011-11-23 23:55:36 UTC
Translation:
If a text is marked with lines what are only underlined, overlined or nothing, it's impossible to set "bold" or to remove "bold"

NOT reproducible with "LibreOffice 3.4.4  - WIN7 Home Premium (64bit) German UI [OOO340m1 (Build:402)]" 

Steps to reproduce:
1. Open attached "sample.odt", what contains text as described
2. <control+a> do select all
3. click "bold" button in 'Format' toolbar several times
   Expected: click will toggle bold <-> not bold
   Actual: as expected

@KB_Pößneck:
Please:
- Attach a sample document (not only screenshot)
- Attach screenshots with comments if you believe that that might explain the 
  problem better than a text comment. Best way is to insert your screenshots
  into a DRAW document and to add comments that explain what you want to show
- Contribute a step by step instruction containing every key press and every 
  mouse click how to reproduce your problem (and if possible how to created a 
  sample document from the scratch)
- add information 
  -- In what application (Writer, Calc, ...) you observe the problem. 
  -- what EXACTLY is unexpected
  -- and WHY do you believe it's unexpected (cite Help or Documentation!)
  -- concerning your PC (video card ...)
  -- concerning your OS (Version, Distribution, Language)
  -- concerning your LibO version and localization (UI language)
  –- Libo settings that might be related to your problems 
    (video hardware acceleration ...)
  -- how you launch LibO and how you opened the sample document
  –- If you can contribute an OOo Issue that might be useful
  -- everything else crossing your mind after you read linked texts
Comment 2 Rainer Bielefeld Retired 2011-11-24 00:12:31 UTC
Created attachment 53827 [details]
Sample.odt

Sample document, see Comment!
Comment 3 Rainer Bielefeld Retired 2011-12-06 01:32:19 UTC
Created attachment 54140 [details]
Sample by reporter

I see the effect selecting all text (bold icon always "active", but I can not find out the reason.
Comment 4 sasha.libreoffice 2012-02-10 06:45:06 UTC
When I opened last attachment by 3.6.0 master, on console appears this:
warn:sw.uno:22642:1:/home/s/libre-master/core/sw/source/ui/uno/SwXDocumentSettings.cxx:478: "CurrentDatabaseCommand" property possibly set before "CurrentDatabaseDataSource"
warn:sw.uno:22642:1:/home/s/libre-master/core/sw/source/ui/uno/SwXDocumentSettings.cxx:487: "CurrentDatabaseCommandType" property possibly set before "CurrentDatabaseDataSource"
warn:sw.uno:22642:1:/home/s/libre-master/core/sw/source/ui/uno/SwXDocumentSettings.cxx:489: "CurrentDatabaseCommandType" property possibly set before "CurrentDatabaseCommand"

When pressed Ctrl-A, Ctrl-C, appears this:
warn:legacy.osl:22642:1:/home/s/libre-master/core/sal/rtl/source/uri.cxx:610: bad pCharClass

when edited document, saved under another name and closed, appears this:
warn:vcl.gdi:22642:1:/home/s/libre-master/core/vcl/source/gdi/outdev.cxx:439: OutputDevice::~OutputDevice(): OutputDevice::Push() calls != OutputDevice::Pop() calls
Comment 5 sasha.libreoffice 2012-02-10 06:48:38 UTC
Validator http://odf-validator.rhcloud.com/
complains on this:

FETT_UeberNichtUnter.ODT/styles.xml[114,672]: Error: unexpected attribute "style:layout-grid-snap-to-characters"

PS: reproducible in 3.3.4 so change version
Comment 6 QA Administrators 2014-10-24 03:18:22 UTC
Please read this message in its entirety before responding.

Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed.

If you have time please do the following:
1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer).
2) If it is present please leave a comment telling us what version of LibreOffice and your operating system.
3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System

Please DO NOT
1) Update the version field
2) Reply via email (please reply directly on the bug tracker)
3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case)

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + 
LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link:
https://wiki.documentfoundation.org/QA/BugTriage

There are also other ways to get involved including with marketing, UX, documentation, and of course developing -  http://www.libreoffice.org/get-help/mailing-lists/. 

Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material
Comment 7 sasha.libreoffice 2014-10-24 11:38:06 UTC
reproduced in 4.3.1.2 on WinXP
Comment 8 KB_Pößneck 2014-10-27 08:17:04 UTC
In LibO 4.2.6.2 ist das Problem behoben.
Vielen Dank