Summary: | open-office-bin-2.0.3 - Fonts problem in PDF options dialog box | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Francois Chenier <belgix_oz> |
Component: | Current packages | Assignee: | Gentoo Office Team <office> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Snapshot of the faulty dialog box |
Description
Francois Chenier
2006-07-11 03:49:29 UTC
Created attachment 91447 [details]
Snapshot of the faulty dialog box
Here is the picture ...
Can't reproduce that, working fine here. Does this also happen if you use another gnome theme and / or font? (In reply to comment #3) > Can't reproduce that, working fine here. Does this also happen if you use > another gnome theme and / or font? Same results with Crux, Simple, Smokey & High Contrast Inverse themes. Not tested all but seems independent of gnome desktop theme. No improvement with Sans 8, Sans 10, Sans 16, Helvetica 10 & Serif 10. Font is changing in the box but missing text still remains ... invisible! No improvement with Gtk+2.8.20-r1. If you find nothing I will compile OO at the next software release. It's great now, we don't need to install half of KDE stuff with the new USE="-kde" flag. (In reply to comment #4) > > If you find nothing I will compile OO at the next software release. It's great > now, we don't need to install half of KDE stuff with the new USE="-kde" flag. > You really could try to rebuild it, maybe something went wrong there in the first place. You might also try to reduce your CFLAGS to something more generic (though I'm not quite sure how this could intervene here, but it can't hurt anyway) before rebuilding. btw: kde was never a hard requirement for OOo, Bug found. Set your interface language to English (UK). Works fine with Default Setting which is likely the same as English (US). (In reply to comment #6) > Bug found. Set your interface language to English (UK). Works fine with Default > Setting which is likely the same as English (US). > So that's a not fully supported language problem, something that got to be handled upstream, closing. Thanks for reporting back! |