In Calc to go to a new line when filling the cells need to use Ctrl+Enter in Writer when horizontally oriented text is used just Enter, and if vertical need to use Shift+Enter. It's confusing, most people cannot understand this intuitively, and they have to search the Internet how to go onto a new line in the vertically oriented text in a table in Writer. I think it would be appropriate everywhere to make the transition to a new line in a table cell in Writer and in Сalc using Ctrl+Enter and Enter the transition in the cell below, as in Calc.
For me, Enter in a Writer table inserts a new line in the cell, no need to use Shift-Enter. Win 7 Pro 64-bit, Version: 4.4.3.2 Build ID: 88805f81e9fe61362df02b9941de8e38a9b5fd16 Locale: fi_FI Version: 5.1.0.0.alpha1+ Build ID: 5fc0cbbc1254223fedf0f78c5e7539219b228697 TinderBox: Win-x86@39, Branch:master, Time: 2015-06-11_04:30:51 Locale: fi-FI (fi_FI)
Eh.. I meant when orientation is vertical.
Win7x64 6.1.7601 SP 1 Build 7601 Version: 5.0.0.1.0+ (x64) Build ID: 1a2c1393dcc950516bcc85470121e6d46e1c2b73 Ubuntu14x64 Version: 1:5.0.0~rc1-0ubuntu1~trusty1 I'm not sure if it's a bug
Beluga, Try Character - Position - Rotate.
Ok, rotation through character & paragraph styles/formatting only accepts line breaks (shift-enter), but not paragraph breaks (enter). Table properties - Text flow rotation does not have this problem. Win 7 Pro 64-bit Version: 5.1.0.0.alpha1+ (x64) Build ID: a51ac4d2bb8c4f1ea1d4ea7569863e2fb6535b02 TinderBox: Win-x86_64@62-TDF, Branch:MASTER, Time: 2015-06-22_21:37:53 Locale: fi-FI (fi_FI)
MS Word 2013 doesn't have text rotation separately. In a table cell, right-clicking gives you a menu item Text direction. A pop-up opens and you can select 90, 0 or 270 degrees. Paragraph breaks work ok in MS Word.
** 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-20170901
*** This bug has been marked as a duplicate of bug 75456 ***
(In reply to Xisco Faulí from comment #8) > > *** This bug has been marked as a duplicate of bug 75456 *** I don't see why. More a dupe of Bug 34436. Or it's all the same with a good new summary.
Oh, I didn't notice bug 34436. I marked it as duplicate of bug 75456 because it's assigned although I don't know if there's any progress there...