Description: As I'm using libreoffice Versión: 6.0.2.1 (x64) compilation id: f7f06a8f319e4b62f9bc5095aa112a65d2f3ac89 in Spanish I'll write the words from menus in spanish. When I use | formato | caracter | bordes in a expresion with subindex there appear a unexpected line. Steps to Reproduce: 1. I have a text with subindex 2. I select format > character > border 3. I select rectangular border It happens too if I change the order. Actual Results: The frame is parted in two because of a unexpected line. Expected Results: A normal, rectangular frame. Reproducible: Always User Profile Reset: No Additional Info: User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:58.0) Gecko/20100101 Firefox/58.0
(In reply to Santi from comment #0) > 1. I have a text with subindex Please attach an example file at this point. Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the document.
Created attachment 140697 [details] odt file where you can find the bug This process is a little bit confused to me. Please, make it more simple.
Thanks, I could reproduce it. At least in my tests (on Linux & Windows), it does not help, if I do the subscript with keyboard shortcut. Steps: 1. Input something like an = 5n - 2 2. Set the n in an to subscript by for example Ctrl-Shift-B 3. Select everything 4. Format - Character - Borders: set all 4 borders Bisected to https://cgit.freedesktop.org/libreoffice/core/commit/?id=d5fab973d0af95c433c5f6a9492014f7db642489 tdf#87224 Merge character borders across different scripts. Character borders were broken when it contains multiple scripts. Merge borders on kern portions and draw its border as necessary. Refer to correct previous portion so it decide whether it join previous or next border correctly. (In reply to Santi from comment #2) > This process is a little bit confused to me. Please, make it more simple. How should we make it more simple?
Thank you. Beautiful work! >> This process is a little bit confused to me. Please, make it more simple. > How should we make it more simple With less fields, if possible.
Adding Cc: to Mark Hung
Dear Santi, 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
I think the description of the newer report is better, so marking this one as the duplicate. *** This bug has been marked as a duplicate of bug 126353 ***