Summary: | FORMATTING Request for wrapping long Date and Time formats | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | Regina Henschel <rb.henschel> |
Component: | Calc | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | NEW --- | ||
Severity: | enhancement | CC: | erack, glogow, hans-peter.dukek, jmadero.dev, LibreOffice, reisi007, vmena19 |
Priority: | lowest | ||
Version: | 3.3.0 release | ||
Hardware: | Other | ||
OS: | All | ||
See Also: |
https://bugs.documentfoundation.org/show_bug.cgi?id=151196 https://bugs.documentfoundation.org/show_bug.cgi?id=159061 |
||
Whiteboard: | |||
Crash report or crash signature: | Regression By: | ||
Bug Depends on: | |||
Bug Blocks: | 108252 |
Description
Regina Henschel
2011-09-07 05:09:46 UTC
A date is a date serial number, just formatted special to display the date. Numeric values, however formatted, are not wrapped in cells but displayed as ### instead if larger. Earlier OOo versions wrapped also numeric values, which was a bug (you don't expect a 14 digits number being wrapped after 11 digits) and got fixed. Introducing line breaking for formatted date/time numeric values IMHO is overkill. But of course, if someone provided a nice patch ... [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 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 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 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 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 This is a valid Enhancement request (but IMHO with very low importance) I see, OOo 1.1.5 indeed breaks long numbers. At least since LibO 3.3.3 that bug is fixed. *** Bug 66595 has been marked as a duplicate of this bug. *** Comment 7 confirms validity of request. Moving to NEW. A far better approach IMHO is to automatically widen the column after input (only!) if it is too narrow and was not yet set to a fixed width by the user. Which also Gnumeric and Excel do. Both also do not wrap numeric and date display strings if wrap is enabled, so we'd display significantly different content if we implemented wrapping here. *** Bug 109119 has been marked as a duplicate of this bug. *** *** Bug 59997 has been marked as a duplicate of this bug. *** |