Apache OpenOffice (AOO) Bugzilla – Issue 23853
Font spacing becomes mis-calculated when auto linebreak is on
Last modified: 2004-01-27 10:49:50 UTC
This issue is probably related to Issue 15437. When a sentence within a cell is wrapped with the automatic line break on, the spacings between the characters seem to get mis-calculated. This becomes really noticeable when the font size is small (< 9). The same thing happens when the user is just typing in the content of a cell before hitting the enter. I will post a screenshot depicting this problem following this post. Kohei
Created attachment 12110 [details] Font in this screenshot is all set to Arial Bold at pt 6.
Created attachment 12111 [details] Spacings look messed up when typing something into cell in-line
Hi Kohei, I'm sometimes have problems with ugly spacing too. But there's no difference between auto linebreak on or off. Is there anything special about your system? E.g. asian locales. Peter
Actually I work in the US (has worked in the last 6+ years), so my locale is en_US. I use fully updated Fedora Core 1 (x86), and that's where I initially noticed this problem. Just FYI, my system uses the default freetype library as I assume that's relevant. Here is the output of the command 'locale' on my system: [kohei@hydro kohei]$ locale LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= I've reported it as a problem in 680m17, but I've also confirmed it in 1.1.1a on Linux. Windows version of 1.1.1a doesn't exhibit this problem running on Win2k SP4. Well, Peter, can we reopen this issue until at least someone using FC1 can test it? I'm actually reopening this issue anyway. If that's a problem, please change it to resolved (though I want it to remain open) again. Kohei
Actually I was wrong about the Win version not exhibiting this problem. I've confirmed it today that, on my system running a US English version of Windows 2000 with SP4, the font spacings become a bit off when the automatic line break is on, AND the content is wrapped. You may have to set the font size to 6 pt & the zoom to 200% to actually see it, though. It becomes really obvious with 5 pt font size zoomed to 300%. Not as bad as the problem on Linux, but it's there. It was confirmed using 1.1.1a for Windows (US English). I haven't tested it on 680m17, but since this seems like a platform-agnostic issue, I assume it's there also. So I will leave the version info unchanged.
reassigned to Peter
Hi Kohei, could you please check if the document: http://gsl.openoffice.org/files/documents/16/350/FontTroubleshooting-v2.pdf resolves you're issue. Peter
No. :( I've read through it. The document only covers general font problems that apply globally across the program. Mine is very specific, it only happens when the font size is small (< 6) and the automatic line break is ON within a cell. You need to set the zoom to 400% to be able to see it, but it's there, and looks ugly on paper when printed. Plus, the document mostly covers problems related to X server and freetype library on *nix platform. This problem occurs on Windows platform also. I don't know the internals of OOo, but this problem is very much similar to Issue 15437 where the developers discovered that the cause of the problem was the incorrect dpi resolution (600 dpi) which coarsened the font matrics. The problem was fixed by setting the resolution back to 2400 dpi (original setting) for the calculation of font placement. I'm just wondering if the old 600 dpi algorithm still kicks in somehow when the automatic line break of a cell is turned on. The problem is not yet resolved, so I'm reopening this issue. Kohei
Funny, 400% works best for me. But zooming in/out with CTRL+Mousewheel shows several percentages where font spacing is indeed very ugly. Seems to be the same in writer. @US: Any idea, maybe duplicate
Issue is a dupe of issue 22540. *** This issue has been marked as a duplicate of 22540 ***
Pls. see issue 22540 for details. Closing dupe.