When I plot against a date/time formatted set of x values (e.g. DD/MM HH:MM), the "Break" option in on the "Label" tab of the "X Axis" dialog is ignored. If I set the "Major Interval" ("Scale" tab) to a small enough value that the labels would overlap, i.e. should break) they are instead drawn on 45 degrees, despite the orientation being set to 0 degrees (unless I specify "Overlap" as well, in which case they overlap). Surely the label should break at the space. The 2nd issue may be seperate, but surely setting an angle of 0 manually shouldn't ever be overridden by 45 degrees -- this is specific to 0 (setting 1 degree works though of course looks horrible). Version: 4.3.7.2 Build ID: 8a35821d8636a03b8bf4e15b48f59794652c68ba on Windows 7x86-64, replicated on Version 4.2.8.2 Build 420m0(Build 2) on Ubuntu 14.04 x86. A bit of background is at http://superuser.com/questions/946288/libreoffice-cell-axis-format-insert-a-newline but this doesn't add any real detail.
Could you attach an example document? Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the document.
Created attachment 117617 [details] Example showing how date/time X axis labels aren't broken but are rotated.
Attachment added with dummy data.
Confirmed that it is impossible to get the text flow to break. Win 7 Pro 64-bit Version: 5.1.0.0.alpha1+ Build ID: 902255645328efde34ddf62227c8278e8dd61ff0 TinderBox: Win-x86@39, Branch:master, Time: 2015-07-30_03:52:07 Locale: en-US (fi_FI)
** 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.1.5 or 5.2.1 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 helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
Unchanged in latest stable: Version: 5.1.5.2 Build ID: 7a864d8825610a8c07cfc3bc01dd4fce6a9447e5 CPU Threads: 4; OS Version: Windows 6.1 (I'm the OP under a new account)
** 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.4.1 or 5.3.6 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 helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170929
Confirmed on 5.3.6.1 under Windows 7 From Help|About: Build ID: 686f202eff87ef707079aeb7f485847613344eb7 CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; Layout Engine: new; Locale: en-GB (en_GB); Calc: group
*** Bug 123769 has been marked as a duplicate of this bug. ***
Created attachment 149877 [details] date axis labels are broken It looks good to me!
(In reply to Balázs Varga from comment #10) > Created attachment 149877 [details] > date axis labels are broken > > It looks good to me! Great! Do you know the commit that fixed it?
> Great! Do you know the commit that fixed it? Probably, this patch also helped here. Balazs Varga committed a patch related to this issue. It has been pushed to "libreoffice-6-2": https://git.libreoffice.org/core/+/997a1ae35041dc8eba5ba7c4e7e3552632ea08d4%5E%21 tdf#122091 OOXML Import: Automatically break of X Axis labels It will be available in 6.2.1. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Opening my original demonstration in 6.4.7.2 I still can't persuade the date/time labels to break. Starting in a blank file doesn't allow breaking either. Perhaps there's a sequence of steps that are necessary for the fix to be effective, but I can't see them and the diff doesn't offer any hints (to me at least). Hopefully it's just a matter of making things clearer. (BTW I don't know how I wasn't notified of the status change at the time - I'm supposed to be subscribed to this bug)
(In reply to Chris Hodges from comment #13) > Opening my original demonstration in 6.4.7.2 I still can't persuade the > date/time labels to break. Starting in a blank file doesn't allow breaking > either. > > Perhaps there's a sequence of steps that are necessary for the fix to be > effective, but I can't see them and the diff doesn't offer any hints (to me > at least). Hopefully it's just a matter of making things clearer. > > (BTW I don't know how I wasn't notified of the status change at the time - > I'm supposed to be subscribed to this bug) You reported this bug in 2015, but apparently created a new account afterwards and never added it to the Cc.
OK I've found the necessary steps. It looks like the fix requires the additional user step of inserting a line break in the number formatting of the axis. Alternatively ticking "source format" and inserting the line break into the format for the source cells breaks the axis labels correctly, but in the source cells the line break is suppressed so the effect is 01/02/0304:05; inserting a space as well breaks the centre-alignment of the 2 lines on top of each other in the axis labels The only way to get the line break in was given by a superuser answer https://superuser.com/a/1581574/245275 and consists of copy-pasting a line break from a cell where it was entered using ctrl+enter - there seems to be no way to enter it in a custom formatting box though it displays nicely as ↵ (but copies as a carriage return). So IMO this needs explaining somewhere
(In reply to Buovjaga from comment #14) > (In reply to Chris Hodges from comment #13) > > Opening my original demonstration in 6.4.7.2 I still can't persuade the > > date/time labels to break. Starting in a blank file doesn't allow breaking > > either. > > > > Perhaps there's a sequence of steps that are necessary for the fix to be > > effective, but I can't see them and the diff doesn't offer any hints (to me > > at least). Hopefully it's just a matter of making things clearer. > > > > (BTW I don't know how I wasn't notified of the status change at the time - > > I'm supposed to be subscribed to this bug) > > You reported this bug in 2015, but apparently created a new account > afterwards and never added it to the Cc. I still receive emails to the address associated with the original account but got nothing there. However one of the reasons I moved away from it was vanishing emails. I am on the CC list now - I just checked - and I thought commenting auto-added me, but maybe I'm thinking of a different bug system.
(In reply to Chris Hodges from comment #15) > OK I've found the necessary steps. > > It looks like the fix requires the additional user step of inserting a line > break in the number formatting of the axis. > > Alternatively ticking "source format" and inserting the line break into the > format for the source cells breaks the axis labels correctly, but in the > source cells the line break is suppressed so the effect is 01/02/0304:05; > inserting a space as well breaks the centre-alignment of the 2 lines on top > of each other in the axis labels > > The only way to get the line break in was given by a superuser answer > https://superuser.com/a/1581574/245275 and consists of copy-pasting a line > break from a cell where it was entered using ctrl+enter - there seems to be > no way to enter it in a custom formatting box though it displays nicely as ↵ > (but copies as a carriage return). > > So IMO this needs explaining somewhere Balázs: any comment on this?
Reproduced in OOo 3.3, so inherited.