Created attachment 110612 [details] all widehats are too small or too large Hello, I read this bug (widehat crop : https://bugs.freedesktop.org/show_bug.cgi?id=62355), but my problem seems different. ---------------------------------------------- Libreoffice Version: 4.2.7.2 Build ID: 933c0aa564ec4f8883ed5732c866db48dca4dac5 OS : Win XP SP1 - Win 7 SP1 - Win 8.1 SP1 --------------------------------------------- The widehat preview is "sometime" different when I reopen my documents. This problem is not regular and occur on the same machine, or when I exchange my documents with other computer (IE: Win XP SP1 - Win 7 SP1 - Win 8.1 SP1). If I save the document in PDF, the preview is already wrong Some time the widehat is too small (see attach widehat.png) Some time the widehat is too large (see attach widehat.png) Regards Nicolas
Created attachment 110613 [details] odt document with widehat too small First example odt document with widehat too small
Created attachment 110614 [details] PDF with widehat too small (no change) The same document converted in PDF
Created attachment 110616 [details] Widehat too large (and too small 2nd page) Second example : PDF document (I have corrected my original odt doc) whit too large widehat (bottom of the first page) (sorry for my English, I'm French)
To sum up, If I edit (double-click) the widehat, formula is correct (ie: widehat {"BAC"}). And after come back in the doc, widehat is correct. I need to correct all my documents each day Nicolas
hi, would you please post a minimal test case, with just a single widehat where you can constantly reproduce the bug? the simpler the document is, the easier will be to spot the differences and focus on the issue. a comparative screenshot showing the desired width of the widehat would be useful too. moreover I did not understand if you are complaining about a visualization bug in the .odt file or just in the .pdf export. also consider upgrading to LibO 4.3.4.1 and retest with that version. set status to NEEDINFO revert it to UNCONFIRMED once you give required informations
Hello, >moreover I did not understand if you are complaining about a visualization bug >in the .odt file or just in the .pdf export. I'm complaining about a visualization bug in the .odt file Nicolas
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! This NEEDINFO Message was generated on: 2015-06-08 Warm Regards, QA Team
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of FDO Message generated on: 2015-07-18
Created attachment 134356 [details] Wrong widehat position before and correct position after editing formula
Created attachment 134357 [details] Wrong widehat position before editing formula
Created attachment 134358 [details] Correct position after editing formula
Hello, I already have this problem since 3 years :( Libreoffice version : Version: 5.3.4.2 (x64) Please find attach the screens shots: 1- "widehat position.png" -> Wrong widehat position before and correct position after editing formula 2- "before.odt" -> Wrong widehat position before editing formula 3- "after.odt" -> Correct position after editing formula This problem happens regularly randomly Many Thanks Nicolas
I think that I have a similar problem. Sometime, when I work with a hold document, my formula are to small when I reopen my documents. If I edit (double-click) formula is correct. I work with windows at work and Linux at home.
(In reply to paour from comment #4) > To sum up, If I edit (double-click) the widehat, formula is correct (ie: > widehat {"BAC"}). And after come back in the doc, widehat is correct. > I need to correct all my documents each day > Nicolas Yep, confirmed with attachment 110613 [details]. But it stays correct after save and reload.. I think there is another report for this, but I could not find it. Arch Linux 64-bit, KDE Plasma 5 Version: 6.0.0.0.alpha0+ Build ID: 98befbb26217b0bf3f35354e418a355280c52cfc CPU threads: 8; OS: Linux 4.11; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on June 29th 2017
** 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 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
Hello, This bug already exist with : Version: 6.0.5.2 (x64) Build ID: 54c8cbb85f300ac59db32fe8a675ff7683cd5a16 Threads CPU : 2; OS : Windows 6.3; UI Render : par défaut; Locale : fr-FR (fr_FR); Calc: group Regards Nicolas
Dear paour, 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
No problem between new versions of Libreoffice. I decided to close this ticket even if the probleme exist between the document gave as example and the last version of Libreoffice
(In reply to paour from comment #18) > No problem between new versions of Libreoffice. > I decided to close this ticket even if the probleme exist between the > document gave as example and the last version of Libreoffice Thanks for retesting with the latest version. Setting to RESOLVED WORKSFORME as the commit fixing this issue hasn't been identified.