upgrading to 5.3 from 5.2.5 the Text alignement behaviour changes in the cells of calc.
previous version, the letter follow a line which is oblique,
new version, the letters keep horizontal but are shifted along the oblique line, which makes it unreadable !!
the feature may be nice, but please add it as an option and have the previous as defaut setting..
Please attach a screenshot, I don't understand the problem.
Set to NEEDINFO.
Change back to UNCONFIRMED after you have provided the screenshot.
Created attachment 131173 [details]
Screenshots from 5.2 and 5.3
The reporter sent this to me via direct email for some reason.
I tried to reproduce it: I wrote something to a cell and then in Sidebar - Properties - Text orientation: 65. It is shown like in your 5.2.
Please copy and paste the contents of your Help - About. It will show us, if you have OpenGL enabled.
Win 7 Pro 64-bit Version: 184.108.40.206.alpha0+
Build ID: 1d810b69a584fc33f4178c7012f68f551ba2e03b
CPU Threads: 4; OS Version: Windows 6.1; UI Render: default;
TinderBox: Win-x86@42, Branch:master, Time: 2017-02-12_23:34:02
Locale: fi-FI (fi_FI); Calc: CL
Reporter again emailed me directly. It is now clear he is using OpenGL.
Lukas: what happens, if you disable it: Tools - Options - LibO - View - Use OpenGL for all rendering?
Please also copy and paste TO A COMMENT the contents of your C:\Users\User\AppData\Roaming\LibreOffice\4\cache\opengl_device.log
I can't reproduce the issue. Created a file in 220.127.116.11, inserted text with orientation of 65° and saved it. Opened in 18.104.22.168 and it looks identical/correct. OpenGL and OpenCL activated (Windows 10).
Build ID: 7074905676c47b82bbcfbea1aeefc84afe1c50e1
CPU Threads: 8; OS Version: Windows 6.2; UI Render: default; Layout Engine: new;
Locale: de-DE (de_DE); Calc: CL
Created attachment 131176 [details]
unchecking openGL is good
Created attachment 131177 [details]
Created attachment 131178 [details]
wrong-view.. mistaken before..was anyway opencl.log
DeviceString: NVIDIA Quadro K600
*** This bug has been marked as a duplicate of bug 100986 ***