Bug 61791 - FORMATTING: Negative Numbers
Summary: FORMATTING: Negative Numbers
Status: RESOLVED DUPLICATE of bug 60215
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected) release
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
Whiteboard: BSA
Depends on:
Reported: 2013-03-04 14:19 UTC by David Humphrey
Modified: 2013-03-04 14:52 UTC (History)
0 users

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description David Humphrey 2013-03-04 14:19:23 UTC
I am using LibreOffice and have just noticed a problem with my existing spreadsheets. The cells are formatted to show negative numbers in RED, and on entering numerical data, either directly or via a formula, all negative numbers do appear in red – exactly as they should do. HOWEVER, if the file is saved, then upon re-opening the file, the negative numbers now revert to the normal BLACK colour.

But, if a NEW spreadsheet is created and numerical data entered after formatting the cells to show negative numbers in red, it does appear to work slightly better. Negative numbers entered directly stay red, even after saving, closing and re-opening, but negative numbers derived from a calculation
still revert to BLACK after saving, re-opening etc. etc. At least, this has been my experience to date.

I do not know if this problem has only just occurred with this latest version of LibreOffice, but I have only just noticed it, and I have to say it is most irritating – as it can be very misleading when both positive and negative numbers look alike, despite there being a small minus sign in front of the negative ones.

 I do hope this problem can be sorted out soon.

David Humphrey
Operating System: Windows 7
Version: release
Comment 1 Thomas van der Meulen [retired] 2013-03-04 14:52:01 UTC
hi David, thank you for repothing this bug.
This is well know bug and very anouching. 
I will mark it as a duplicate of fdo#60215

*** This bug has been marked as a duplicate of bug 60215 ***