Apache OpenOffice (AOO) Bugzilla – Issue 5960
Spellcheck will not catch errors with certain fonts
Last modified: 2013-08-07 14:41:36 UTC
Installed OpenOffice.org 1.0 from clean tarball. On both -net install and single-user installs, using the default font Thorndale, the spellchecker will miss word that are misspelled. If the font is changed to a normal font, then the spellchecker will work. However, if you use the drop down box, and the font has "!2CTev" and two other odd characters after it, anything in that font will be missed by the spellchecker. Further, in the -net installs, if you change the font then spellcheck twice, OpenOffice.org will crash. None of these problems appear in the spreadsheet spellcheck. It works fine for all fonts. I know this sounds crazy, but on my test machine, I can replicate this over and over and over. It's driving me batty. I'm having a user with a similar problem. Argh!
Hi, Yes, I have seen this exact same thing before I had a priner attached to my machine. The problem is that when specific fonts do NOT exist on a system, the OOo code tries to use whatever graphics device is available to create it (typically it talks to the printer so that the screen in Writer can do real WYSIWYG and the printer and the screen font metrics and things are in sync. Sometimes (and I haven't figured out why yet), this "created" replacement font is created as a SYMBOL font (like zapf dignbats, etc) that the spellchecker is set up to ignore. Thorndale is the default but it does NOT exist on most OOo systems (it only comes with StarOffice). So you might try using spadmin to remove any fonts that do not actually exist on your system to prevent them from being used. This is supposed to happen on startup by takling with the graphics device but for some reason this does not work (and never has as far as I can tell). IMHO, Thorndale should NOT be the default font under OpenOffice.org since it is practically guanranteed not to exist on any Linux / Windows box that does not have StarOffice already installed on it. Hope something here helps, Kevin
Kevin, That actually makes alot of sense. The only thing that throws me is why all the fonts work in the spreadsheet, but not in the word processor. Perhaps the spreadsheet doesn't recognize symbol fonts, so it doesn't treat them as symbol fonts? I don't know. Your answer makes the most sense of anything I could come up with. Thanks!
ES->US: Any statement on this?
us->tl: if I remember correct you fixed this for beta, didn't you?
TL->HDU: To you to comment.
HDU: The "!2CTev" fonts have the "symbol attribute" set. For some reason these fonts are considered to be symbol fonts. Maybe they have a funny encoding mentioned in the related fonts.dir file. Please provide the fonts.dir of the directory where one of these fonts live that shouldn't behave as symbol fonts. The other problem might be that Thorndale falls back to a "random font that is early in the font list" is probably related to #107485#, which gets fixed in CWS VCL06. The reason behind this is in vcl/source/gdi/outdev3.cxx's ImplDevFontList::ImplClear() method. This method needs to get a line "bMatchData = FALSE;"
Hi, Is this now fixed? Anyone know? Kevin
There are two ways how this could have happened: - #107485#, which is fixed since CWS VCL06. - an unidentified encoding in a "fonts.dir" file Since we haven't heard anything for four months on this second possibility, we have to assume that everyone only encountered the first problem.
HDU->US: Time to verify in a recent build and close...
@submitter: pls. verify in OOo 1.1 and comment. Thanks.
Changing resolutio to FIXED.
Fixed in OOo 1.1. Closing issue.