Created attachment 61098 [details] screenshot of some bad looking signs Problem description: Steps to reproduce: fresh installed Libreoffice Current behavior: The signs "plus"(+), "toward" and i.e. leftarrow will appear in a different font than, say minus(-). They look thicker. Platform (if different from the browser): Linux x86_64 and WinXP Browser: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:12.0) Gecko/20100101 Firefox/12.0
Please could you attach a file that demonstrates the problem. Thanks.
Created attachment 68023 [details] Example file to the Picture
Confirmed in master e4080dc (1 Oct, 16.50) Interestingly, but probably not usefully, not an issue in 3.3. Something to do with font substitution? Subscribing caolanm. Hope that is okay.
Hi, everybody. Just informing that Bug 51827 is probably related to this bug report. Please, check it out. Regards. Roberto.
The fix I found is to replace the Opensymbol font with the version supplied with LO 3.3.0. The reported versions of the old/new ttf are the same (102.2) but the size is different. Tested with L.O 3.6.4.3 under Win7/64 and L.O 3.6.2.2 under Ubuntu 12.10/64. For your convenience, here's the old version of the opensymbol font that fixed the issue: http://ge.tt/api/1/files/9lUZZdW/0/blob?download
Unfortunately it does not work for me. (LO 3.6.0.2 (Kubuntu 12.04)) (In reply to comment #5) > The fix I found is to replace the Opensymbol font with the version supplied > with LO 3.3.0. The reported versions of the old/new ttf are the same (102.2) > but the size is different. > Tested with L.O 3.6.4.3 under Win7/64 and L.O 3.6.2.2 under Ubuntu 12.10/64. > For your convenience, here's the old version of the opensymbol font that > fixed the issue: http://ge.tt/api/1/files/9lUZZdW/0/blob?download
(In reply to comment #6) > Unfortunately it does not work for me. (LO 3.6.0.2 (Kubuntu 12.04)) I installed Kubuntu 12.04.1/32 on a virtual machine. Opened LO 3.5.4.2 that comes default, wrote an equation (x + y - z) => thick ugly "+". Saved file. Replaced the current opensymbol font (it's in /usr/share/fonts/truetype/openoffice/) with the old one in the link above (with root privileges). Rebooted. Opened LO 3.5.4.2, opened previous file => nice thin "+". :) Updated kubuntu. The LO remained same version. Updated LO to 3.6.0.2. (p.i.t.a) Overwrite opens__.ttf with the downloaded one to make sure. Fired up LO 3.6.0.2 => nice looking "+". You may want to try replacing the font again. It should work for you as well.
(In reply to comment #7) > You may want to try replacing the font again. It should work for you as well. Ok, now it works. Thanks. My mistake was that I just renamed and not delete the broken font file.
*** Bug 51827 has been marked as a duplicate of this bug. ***
Dear friends, I'm sorry for bothering, but this bug still exist in 4.0.1. I would like to comment a bit the situation. Obviously, LO Writer is a promising tool for creation of scientific texts. But this bug prohibit almost totally Writer from using it as scientific text processor. Right now, the equations look terribly ugly! I can not use LO and I can not recommend it to my colleagues as a primary tool to be used within our team. Because we need high-quality equation editor. And LO Math was such editor before this bug. This bug is fairly old and I'm afraid that having 'low' importance status, it won't be fixed for a long time... To my mind, the bug is quite important. So is there any chance for this bug to be fixed?
(In reply to comment #10) > Dear friends, I'm sorry for bothering, but this bug still exist in 4.0.1. [...] > So is there any chance for this bug to be fixed? I have been using LO for generating lecture notes, homework assignments, etc. and have been struggling with this issue under Windows. Removing the currently installed opensymbol font and substituting the old version, as described above, fixed the problem. Control Panel => Fonts select OpenSymbolRegular, click delete. Download old font file, double click and click install. Back to nice looking equations.
Dear wsutcee, thank you for your advice. Actually, I did the procedure described above long ago. I did it under Ubuntu and under Win, and it works for me. So many thanks to Cip for finding the workaround. But I believe it's important that such things must be “from the box”. If LO claims to be “comprehensive, professional-quality productivity suite”, then the user should just install it and work, but not first-repair-then-work. So my desire is LO to be indeed the best office suite. But with annoying bugs like this, it's impossible :( And I am just amazed that nobody (I mean the developers) cares about this obvious and reproducible bug. And it's even more amazing if fixing is as simple as replacing the broken font by a correct one...
Alternate workaround is to use the notation: x {"+"} y ...instead of the usual: x + y More examples regarding treatment of the various "minus" sign characters: http://ask.libreoffice.org/en/question/15177/underbraces-and-overbraces/?answer=15806#post-id-15806 Also, minor point regarding the version of the OpenSymbol font. The statement "The reported versions of the old/new ttf are the same (102.2) but the size is different" in comment #5 does not appear to be correct. The old version of OpenSymbol shipped with LO v3.3.0.4 was v2.4.3 (c) 2010 Oracle. This is also the version provided in the link, whereas the current is v102.2 (c) 2009 Sun / (c) 2011 Julien Nabet / Olivier Hallot, and has been so since at least v3.5.x.
In the past I used the workaround to override the opens___.ttf with an older version. Every thing was perfect. But now I have to use "lline" and this looks terrible. With a new verion of opens___.ttf "lline" looks good, but "+" and "toward" look terrible. And the workaround to use "+" instead of + doesn't work on "toward".... So many workarounds ... Why can't it be fixed (in over two years)?
I confirm the problem with lline and rline when using the "old-font-workaround". So, LO Math is still not able to produce publication-quality equations. It is very sad situation, since this means that LO Math is actually unworkable. Indeed, who needs a tool making text which cannot be published?.. Very sad and no hope after about three years of waiting... I tried to raise this problem on the LO forum: http://en.libreofficeforum.org/node/7051 And I was told that we are on the edge of big changes... But another year passed and there's neither any apparent change in this direction, nor fix for this bug... Of course, I understand well that LO is developed by volunteers and I am very grateful for the great work they do. And this makes the situation even more sad since nothing actually can be done... Meanwhile, the whole component of LO is unusable for several years... ((( Sorry for this expression of my upset. I don't mean to insult anybody.
Created attachment 112556 [details] OpenSymbol font file that works on Win 8, too This font file is based on Version 1.7 of OpenSymbol but with updated glyphs (upright greek letters, +, arrows, <, > and =)
The attached font file (attachment 112556 [details]) causes problems i.e. with ldbracket, langle, lline and ldline. So I would prefer the older one that only causes problems with lline and ldline.
Olivier or Frederic might have some ideas as the last two people that hacked on that font. (see extras/source/truetype/symbol/ for the source of the font and a README on bumping the version etc)
** 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.5 or 5.2.1 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-20160920
The bug is still present. LibreOffice 5.2.1.2 Win7 and Ubuntu 16.04 My sincere apology, but I would like to stress once again that the bug is critical. LO Math is useless if it cannot fulfil its main goal -- generation of publication-quality equations. And this is the case with this bug.
** 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
(In reply to Caolán McNamara from comment #18) > Olivier or Frederic might have some ideas as the last two people that hacked > on that font. (see extras/source/truetype/symbol/ for the source of the font > and a README on bumping the version etc) There is a simple hack that might temporarily solve the problem. Go to Tools > Options > Fonts (LibreOffice) and substitute OpenSymbol with your font. I hope that the bug will be fixed.
A general discussion is needed: https://bugs.documentfoundation.org/show_bug.cgi?id=122730
The bug is in core/starmath/source/parse, on the nextToken() or the grammar. It has to be the different interpretations of '-'. 'll take a look, but do not make promises.
Dear raving, 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 https://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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
The problem still exists in the current version. Tested in: Version: 7.3.4.2 (x64) / LibreOffice Community Build ID: 728fec16bd5f605073805c3c9e7c4212a0120dc5 CPU threads: 1; OS: Windows 10.0 Build 18362; UI render: Skia/Raster; VCL: win Locale: de-DE (en_DE); UI: de-DE Calc: threaded