Red Hat Bugzilla – Bug 73538
broken spadmin in ru_RU.UTF-8
Last modified: 2007-04-18 12:46:22 EDT
Description of Problem:
spadmin doesn't display cyrillic characters in ru_RU.UTF-8 locale
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install null and select Russian as default language
2. login and start OpenOffice.org printer setup from menu
you'll see "?" in place of every character
Cyrillic text must be there
In other OOo applications (writer, calc etc) everything is Ok
Created attachment 75134 [details]
spadmin window snapshot
Something's broken with ru_RU.utf8. I can't even start oowriter
LANG=ru_RU.utf8 oowriter spins in an infinite loop.
LANG=ru_RU works, LANG=ru_RU.utf8 doesn't.
Created attachment 75428 [details]
oowriter with cyrillic text
I am able to enter Cyrillic letters in both en_US.UTF-8 and ru_RU.UTF-8 locales.
There is a small problem. In en_US.UTF-8 if file name contains Cyrillic (UTF-8)
letters, they do not show up in OO file open (and status bar). However correct
Cyrillic document name shows up in window title! See attached.
This is just null + up2date (no other packages/ajustments).
This bug is still present in phoebe (8.0.93)
If msttcorefonts rpm is instaled (see corefonts.sf.net), spadmin window is ok.
Looks like the reason is somewhere in openoffice-default-font-nimbus-luxi.patch.
List of fonts for aImplSubsSansUnicode =
"andalesansui;luxisans;arialunicodems;lucidaunicode" doesn't have any font with
cyrillic glyph. If you install MS fonts, spadmin will appear in MS Arial
(arialunicodems). To fix this proble, it woluld be enough to add at leat one
sans serif font with cyrillic characters to this list, for example nimbussansl.
Does this problem still occur with 1.0.2-8 or later?
Created attachment 97568 [details]
openoffice.org-1.1.0 looks fine to me.
I think this has been fixed some time ago.
Unfortunately, I'm unable to find printer admin in currently installed
1.1.0 > 20 don't ship with an spadmin since all printers are automatically discovered
using CUPS, and since File->Export to PDF is the correct PDF export method... So I
guess this has been "fixed" more or less?
Yes, I marked as "closed"