Description of problem: Although most of the ui can displayed in (Traditional) Chinese correctly, partial area of gui still display squares and is not readable. Version-Release number of selected component (if applicable): 3.3.2.2-6mga1 How reproducible: Start localized libreoffice in zh_TW locale. Steps to Reproduce: 1.Install libreoffice-langpack-zh-Hant. 2.Set locale to traditional Chinese. 3.Start libreoffice writer. Screenshots of specific area that has this problem will be attached later. Reproducible: Steps to Reproduce:
Created attachment 234 [details] statusbar of libreoffice The status bar shows squares after langpack installed. (see attachment for reference.)
Created attachment 235 [details] fontsetting in libreoffice Partial area of font setting in libreoffice display squares. Note other area can display Traditional Chinese correctly. (see attachemtn pic for reference.)
Mandriva's libre office does not have this problem. Is there any patch that could fix this bug?
This problem only happens in KDE desktop, not in GNOME.
Workaround found: Remove libreoffice-kde.
Hardware: i586 => All
Source RPM: libreoffice => libreoffice-3.3.2.2-9.mga1.src.rpm
Source RPM: libreoffice-3.3.2.2-9.mga1.src.rpm => libreoffice-3.3.2.2-13.mga1.src.rpm
Sorry, this bug has totally fallen under my radar :/ Good catch finding the cause :)
Added to the Errata http://www.mageia.org/wiki/doku.php?id=mageia1:errata#libreoffice-kde_issues .
Assignee: bugsquad => dmorganecSource RPM: libreoffice-3.3.2.2-13.mga1.src.rpm => libreoffice-kde
In my KDE desktop, I have the same problem. My workaround is: * libreoffice-kde must be installed. * Choose KDE system fonts as "Droid Sans", or "UMing". Then the Chinese UI can be shown.
CC: (none) => franklin
Franklin's case is quite different: he reported (in our local google group) that all Chinese characters in libreoffice UI are squares if libreoffice-kde is not installed. (But I cannot reproduce it.) I recommend Franklin report a new bug instead. However, since these two problems seem to be conflict, it might be difficult to have both fixed.
(In reply to comment #9) > Franklin's case is quite different: he reported (in our local google group) > that all Chinese characters in libreoffice UI are squares if libreoffice-kde is > not installed. (But I cannot reproduce it.) > > I recommend Franklin report a new bug instead. However, since these two > problems seem to be conflict, it might be difficult to have both fixed. Yes, I found the differences. In my workaround, the status bar would still be unrecognized squares.
Not the same as, but maybe somehow related to bug 751 We're on a newer version of libreoffice now, did that improve anything?
CC: (none) => marja11
It is the same old story with KDE users failing to configure proper UI fonts (i.e. just specifying the alias "Sans") and no proper fallback configuration on the system. When the kde-integration package is installed, LibreOffice reads the configured font from the system, but the one that is then matched doesn't support all characters. Solution: Configure a proper chinese font in KDE's font settings (as pointed out by Franklin in comment#8) Alternate Solution: Tell LibreOffice *not* to use the font that is configured in KDE (same effect regarding the font as if the kde package was not installed) Tools|Options â LibreOffice â View: uncheck [ ] use system Font for UI display you probably should visit that dialogpage anyway, at least when you want to keep a bitmap font as UI font. (disable aliasing/increase the fontsize limit for aliasing fonts) You can also try to adjust the scaling factor to hit a fontsize that is covered by the bitmap font. (but then it is again hard to have proper display in both the menu as well as the dialog). otherwise: duplicate, Again: * it is essential that you configure proper font in KDE, and * it is important to have proper fallback definitions in the system (see bug 751) * bitmap fonts will only be rendered at specific display-sizes. At one size you'll see it, at another size you won't. *** This bug has been marked as a duplicate of bug 751 ***
Status: NEW => RESOLVEDCC: (none) => lohmaier+mageiaResolution: (none) => DUPLICATE
*** Bug 1897 has been marked as a duplicate of this bug. ***