Scaling the width of characters via (de) _F_ormat - Zei_c_hen -> [Schriftposition] works well unless the whole cell-content is to be scaled. If *all* characters in the cell are scaled (to the same value), the cell-content is displayed at (respectively set to) 100%-width-scaling after hitting [Enter]. Steps to reproduce: 1. open new spreadsheet 2. enter some text into a cell [Enter] 3. select the cell with entered text and open for editing [F2] 4. select *some* (e.g. all but the last) characters in the cell 5. modify character-width scaling ( [Alt] + F , C , (Tab.) "Schriftposition" ) to e.g. 90% 6. select [OK] -> the selected text is displayed scaled to (e.g.) 90%-width. 7. [Enter] -> the text in the cell is displayed with the previosly selected characters scaled to (e.g.) 90%-width. so far so good 8. edit the cell again [F2] 9. select the previously *not* selected/scaled characters 10. modify the width-scaling as before to the same value - (e.g.) 90% 11. select [OK] -> the whole text in the cell is now displayed scaled (to e.g. 90%-width) 12. [Enter] current behaviour: the whole text in the cell is reset to 100%-width expected behaviour: the whole text in the cell should be displayed at the previously set width (e.g. 90%) OS: Linux (Debian/SolydK) Version: 4.2.5.2, Build-ID: 420m0(Build:2)
just updated LibreOffice - same behaviour in Version: 4.3.0.4, Build-ID: 430m0(Build:4)
Created attachment 104846 [details] Mixed results demonstrating this issue Test System: Kubuntu (KDE 4.13.3) LibreOffic 4.2.4.2 I hope I have duplicated the format. In English, I used Format - Character - font position(tab) - text width (used 70% to let me see the difference easier0 I am having mixed results. - Some of my text is holding the formatting. More often, it does not. - Capital vs lower case does not seem to matter. - I am not satisfied that I have exactly confirmed the problem. Am I using the intended formatting steps?
Yes, you do. The "mixing" behaviour is even more strange ... Did you format (scale) the whole text-content at once? And, I guess, you did the same steps for each of the three filled cells in your testfile. Right? Or did you do something different with the "working" cell?
Ok I just recognised: in the seemingly(!) working cell, you scaled the BEGINNING ("sym") with 60% and the ENDING ("bol") with 70%. So it's NOT THE SAME what I described (scaling all text in the cell to the same value [!=100%] ). Further details to the BUG(!): (1) If text with different scaling values is selected (e.g. in the filed testfile "symb" from field A1 - with "sym" scaled to 60% and the "b" scaled to 70%) and the scaling-dialog is called, then the scaling value field is NOT EMPTY (as usual for an attribute of a selection formatted to varying values, e.g. text formatted with various fonts or font-sizes) but shows "100%". (2) width-scaling for the whole cell-content works, if at the same time the spacing is trimmed (to e.g. "0.1 pt condensed")
** 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.0.0.5 or later) 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-09-03
Test System: Kubuntu (Frameworks version: 5.9.0) LibreOffice 5.0.1.2 The bug appears to have been squashed. It was possible to set two parts of a word to 70% width in two stages and have 70% width "stick" for the whole cell after the second edit. NOTE: I was unable to set the status to WORKSFORME because that option was not available to me in the selection tool. I therefore left it unchanged (NEW).
Follow-up. I see that I was too timid. Selecting RESOLVED from the tool allowed me further selectable options. I've been away too long.
Sorry, but this bug is still present ("alive"): as long as in cell-edit mode (F2) the text remains (e.g.) condensed; after pressing "enter" it swaps back to 100%-width. I can keep it "stable" with a new generated profile, but ONLY until for the first time formatting all text in a cell *at*once* to a width [!=100%]. After that it always keeps swapping back as soon as all text is formatted to same width [!=100%]. Version: 5.0.1.2 Build-ID: 81898c9f5c0d43f3473ba111d7b351050be20261 Gebietsschema: de-DE (de_DE.UTF-8)
Bug does not meet the criteria for Status 'REOPENED' https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/REOPENED#Criteria Status -> UNCONFIRMED
Ubuntu 15.04 x64 LibreOffice 5.0.0.5 Confirmed: Note: Please don't change the version - as the label says "earliest affected" Version is NOT "latest version tested on). Setting to: New Normal - just a normal run of the mill bug that can potentially prevent high quality work Low - Not a feature that is going to impact a ton of users (given limited activity over the course of 14 months, no duplicate bugs, experience of this QA member). If this is tested against older releases and found to be a regression it should: 1) Be bumped to "medium" 2) "regression" should be added to keywords; 3) "bibisectRequest" should be added to whiteboard To test older versions: http://downloadarchive.documentfoundation.org/libreoffice/old/ Best thing to do is test 3.3 and see if it was around at that point - if it was, version should be updated to "inherited from OOo". Thanks
** 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.6 or 5.2.3 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-20161108
Dear VolkerTwer, 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 with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. 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) from 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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Looks like the bug has been cleared. Thanx a lot! Info from < Help - about LO > : Version: 6.3.3.2.0+ Build-ID: 1:6.3.3-2~bpo10+1 CPU-Threads: 4; BS: Linux 4.19; UI-Render: Standard; VCL: gtk2; Gebietsschema: de-DE (de_DE.UTF-8); UI-Sprache: de-DE Calc: threaded